stripe-webhook-replay-labReplay signed Stripe webhook payloads to a local or staging endpoint for idempotency and retry debugging.
Install via ClawdBot CLI:
clawdbot install daniellummis/stripe-webhook-replay-labGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
WEBHOOK → http://localhost:8000/webhooks/stripeCalls external URL not in known-safe list
http://localhost:8000/webhooks/stripeAI Analysis
The skill's external endpoint is user-provided via the STRIPE_WEBHOOK_URL input, making it a controlled test target rather than unauthorized exfiltration. The functionality is transparent and consistent with its stated purpose of replaying webhooks for debugging, with no evidence of credential harvesting, obfuscation, or hidden malicious instructions.
Audited Apr 16, 2026 · audit v1.0
Generated Mar 22, 2026
An online retailer uses this skill to test idempotency of order creation webhooks after payment success. Replaying webhooks ensures duplicate events don't create multiple orders or charge customers twice, crucial during high-traffic sales like Black Friday.
A SaaS company replays subscription lifecycle webhooks (e.g., checkout.session.completed) to verify that billing updates and user access provisioning are idempotent. This prevents overcharging or service interruptions during webhook retries from Stripe's side.
A fintech firm tests webhook replay for payment confirmation events to ensure accounting systems record transactions only once. This helps debug retry scenarios and maintain accurate financial records without manual intervention.
A marketing platform uses this skill to simulate duplicate webhook deliveries for customer engagement events. It validates that notification systems (e.g., email or SMS) don't spam users with repeated messages during webhook retries.
A development team integrates this skill into CI/CD pipelines to replay webhooks against staging endpoints. It automates idempotency testing for new features, ensuring code changes don't break webhook handling before deployment to production.
Businesses charge recurring fees for access to services, relying on Stripe for billing. This skill helps test webhook idempotency to prevent duplicate charges or subscription errors, ensuring reliable revenue streams and customer trust.
Platforms earn a percentage or fixed fee per transaction processed through Stripe. By replaying webhooks, they verify that payment events are handled idempotently, avoiding over-counting transactions and ensuring accurate fee calculations.
Companies sell custom software licenses with integrated payment processing. Using this skill, they test webhook replay for large-scale deployments to ensure idempotent handling of license activations and renewals, reducing support costs and errors.
💬 Integration Tip
Set up a local test endpoint first using tools like ngrok to simulate webhook reception, and use the REPLAY_DELAY_SECONDS parameter to mimic real-world retry intervals for more accurate debugging.
Scored Apr 19, 2026
Automate common Word/WPS document operations on Windows via COM (read text, replace, insert, headings, headers/footers, page breaks, merge, split, export to PDF/TXT, add/replace images). Use for single-document actions (no batch).
Set timers and alarms. When a background timer completes, you receive a System notification - respond with the reminder message (NOT HEARTBEAT_OK) to notify the user.
Control a Mac through natural language — open apps, click buttons, read the screen, type text, manage windows, and automate multi-step tasks via Airpoint's A...
Configure notification channels and conditional alerts. Track what's being watched, log what's been sent.
Native Windows mouse control (move, click, drag) via user32.dll. Use when the user asks you to move the mouse, click, drag, or automate pointer actions on Windows.
Unified notification hub collecting all skill alerts and delivering by priority