More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Webhook Failure Triage

    1

    Sort webhook failures fast and stop silent drops from losing orders.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Webhook Failure Triage

    Webhook Failure Triage

    Example session with this skill installed

    Apply the skill to this case: A store's payment webhooks occasionally failed to create orders. Support found the gap hours later, and replays sometimes created duplicate orders.

    • Read your context and instructions
    • Compiled the webhook failure triage

    Situation: A store's payment webhooks occasionally failed to create orders. Support found the gap hours later, and replays sometimes created duplicate orders. Evidence: Sender logs showed 5xx responses after 10 seconds; the receiver took 12 seconds during peak load because it ran a report synchronously. Retries then duplicated orders because no idempotency key was stored. Decision: Move the report out of the webhook path, respond in under 3 seconds, store the event id before processing, and alert on dead-letter depth. Outcome: Webhook failure rate fell from 4 percent to under 0.2 percent, duplicates stopped, and the next failure alerted within 10 minutes instead of being found by support hours later.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Webhook failures are hard because the sender thinks it delivered and the receiver thinks nothing arrived. The gap is usually a timeout, a signature or retry mismatch, an ordering problem, or a dead-letter queue no one watches. This skill reconstructs the delivery chain from both sides, classifies each failure, and puts a replay and monitoring fix in place so the next failure is visible within minutes. This skill gives you a counted diagnosis, a decision table, a fill-in template, a checklist, and a scoring rubric, plus a runnable script (webhook_triage.py) that Classifies webhook events from a CSV into timeout, error, duplicate, or missing, reports the duplicate rate against the 1 percent idempotency threshold, and writes a triage report. It is built for the bottleneck moment: when the usual quick fix has already failed, or when a silent failure is worse than a loud one. Follow the protocol in order, record numbers rather than impressions, and use the quality gate before you call the work done.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.

    Results depend on the quality of your evidence set: sender logs without receiver logs, missing event ids, or an unwatched dead-letter queue will limit the diagnosis, and the skill says so rather than filling gaps with guesses. The script is a helper for counting and reporting; it does not replace judgement about safety, permission, or whether a fix is correct. Thresholds are starting points to adapt to your context, not universal constants.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 23 days ago

    Permissions

    Terminal / Shell
    Write Files
    Network Access
    Listed23 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Because the first attempt may have succeeded slowly. Without storing the event id before processing, a retry looks like a new event.

    No. Acknowledge fast, store the event, then process from a queue. Slow synchronous work turns into sender timeouts and retries.

    Continuously, with an alert at one hour old. A daily manual check is how silent drops survive for days.

    New in APIs & Backend