More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    WebhookReceipt — Retry & Idempotency Safety Audit

    1

    Audit payment and event webhooks for duplicates, replay handling and failure-safe processing.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    WebhookReceipt — Retry & Idempotency Safety Audit

    WebhookReceipt — Retry & Idempotency Safety Audit

    Example session with this skill installed

    Run WebhookReceipt — Retry & Idempotency Safety Audit as an evidence-first preflight. This is a representative, hypothetical test case: A webhook handler sends two fulfillment emails when the same paid-order event is retried. The materials I have available are: webhook handler code; event delivery fixture and retry policy; signature verification and storage configuration. Tell me what is evidenced, what is missing, which claims must be held, the exact corrections, and a clean verification plan. Do not claim you opened a file or performed a live run unless one is actually supplied.

    • Read your context and instructions
    • Compiled the webhookreceipt

    REPRESENTATIVE EXAMPLE — NOT A LIVE RUN

    PREFLIGHT: HOLD / VERIFY BEFORE ACTING. Task: Audit payment and event webhooks for duplicates, replay handling and failure-safe processing.
    Scenario supplied by buyer: A webhook handler sends two fulfillment emails when the same paid-order event is retried.

    1. MATERIAL FINDING (HIGH): The supplied pseudo-code acknowledges an event after side effects and has no persisted event-ID guard. The case describes a potential issue; no underlying account, file or production service has been accessed by this illustrative demo.

    2. TRACEABILITY MATRIX

    • Claimed behavior: A webhook handler sends two fulfillment emails when the same paid-order event is retried.
    • Critical evidence sources: webhook handler code, event delivery fixture and retry policy, signature verification and storage configuration.
    • Status: NOT VERIFIED from primary artifacts in this example. A real invocation must attach the files or authorize a read-only source inspection and record exact references.
    1. CHECKS THE SKILL WILL RUN
    • Trace authentication/signature checks before parsing or processing untrusted events.
    • Inspect event-ID deduplication, transactional state changes, and concurrency race conditions.
    • Check non-2xx retry handling, exponential backoff and poison-event dead-letter behavior.
    • Build harmless duplicate/reordered-event test fixtures in a sandbox rather than sending live charges.
    • Produce severity-ranked fixes with evidence, safe tests and deployment rollback conditions.
    1. CORRECTION TO PROPOSE
      Add durable event-ID idempotency around the transaction and perform side effects only after committed state. Do not present this as implemented until the seller/developer actually applies the change and reviews the result.

    2. REPRODUCTION / ACCEPTANCE TEST
      Replay identical and out-of-order sandbox fixtures; assert one fulfillment effect and safe retries. Capture the before/after witness (paths, commands, timestamp, observed outcome), distinguish a script signal from a working end-to-end product, and do not invent a PASS.

    3. SCOPE LIMIT
      No live payment capture, provider credentials, or production event replay without authorization.

    Final handoff: a clear evidence-linked issue list, copy-ready proposed changes where appropriate, a prioritized checklist, and a statement of exactly which tests were and were not run.

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

    About this skill

    WebhookReceipt — Retry & Idempotency Safety Audit

    Audit payment and event webhooks for duplicates, replay handling and failure-safe processing.

    What you receive

    • A ready-to-install skill with a repeatable, evidence-first procedure.
    • A source-to-claim discrepancy matrix, severity tags and specific corrective actions.
    • A clearly separated verification checklist and unknowns register.
    • A representative worked example; it is not passed off as a live customer run.

    Example issue

    A webhook handler sends two fulfillment emails when the same paid-order event is retried.

    Trust boundary

    No live payment capture, provider credentials, or production event replay without authorization.

    No paid API subscription is bundled. The agent can inspect materials supplied by the buyer in its supported environment. Access to private services is never presumed.

    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.

    No live payment capture, provider credentials, or production event replay without authorization.

    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 8 days ago

    Permissions

    File Scopes

    Buyer-provided
    local
    files
    (read-only)

    No production changes or account access without owner authorization.

    Listed8 days ago

    What's inside

    Frequently Asked Questions

    No. Supply files or authorize a suitable read-only connection. Missing evidence is marked unverified.

    No, they illustrate a representative workflow; the delivered skill uses your actual materials.

    New in APIs & Backend