More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair S3 Event Notification Duplicate Commit Race

    1

    Remove duplicate downstream writes caused by retried object-created event delivery

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair S3 Event Notification Duplicate Commit Race

    Repair S3 Event Notification Duplicate Commit Race

    Example session with this skill installed

    A single S3 object produces two ledger postings after Lambda retry overlaps a queue replay.

    Available sources: object version IDs and event payloads (partial excerpts only). Additional evidence requested: consumer idempotency keys, ledger write logs. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.

    • Read your context and instructions
    • Compiled the repair s3 event

    Repair S3 Event Notification Duplicate Commit Race — EVIDENCE-LIMITED REVIEW

    Scenario received

    A single S3 object produces two ledger postings after Lambda retry overlaps a queue replay.

    Source register

    • S1: object version IDs — partial extract described, independent verification not provided.
    • S2: event payloads — partial extract described, independent verification not provided.
    • S3: consumer idempotency keys — NOT PROVIDED; validation pending.
    • S4: ledger write logs — NOT PROVIDED; validation pending.

    Case-specific checks

    1. group events by object version and sequencer — NEEDS VERIFICATION against S1/S2 and missing sources.
    2. trace retry windows and commit boundaries — NEEDS VERIFICATION against S1/S2 and missing sources.
    3. identify unsafe deduplication key scope — NEEDS VERIFICATION against S1/S2 and missing sources.
    4. design conditional write and replay test — NEEDS VERIFICATION against S1/S2 and missing sources.

    Deliverables and review gates

    • duplicate event genealogy: DRAFT ONLY; do not infer unsupported outcomes.
    • commit-race root cause: DRAFT ONLY; do not infer unsupported outcomes.
    • idempotent repair and regression cases: DRAFT ONLY; do not infer unsupported outcomes.

    Preliminary conclusion

    INCOMPLETE / REVIEW REQUIRED. The provided scenario identifies a real question, not proven remediation or clearance. Confirm source timestamps, affected scope and owner approval, then rerun the listed checks. No external system was accessed or changed.

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

    About this skill

    Repair S3 Event Notification Duplicate Commit Race is a ToolForge Labs ChatGPT Skill workflow. Remove duplicate downstream writes caused by retried object-created event delivery.

    What this skill checks

    1. group events by object version and sequencer.
    2. trace retry windows and commit boundaries.
    3. identify unsafe deduplication key scope.
    4. design conditional write and replay test.

    What to provide

    • object version IDs.
    • event payloads.
    • consumer idempotency keys.
    • ledger write logs.

    Deliverables

    • duplicate event genealogy.
    • commit-race root cause.
    • idempotent repair and regression cases.

    Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions, reports missing inputs, and never claims an unperformed live test, compliance approval, or production change.

    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.

    Cannot verify inaccessible systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.

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

    Permissions

    Read Files

    Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.

    Listed25 days ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill addresses race conditions and duplicate writes in serverless architectures, specifically when S3 event notifications trigger multiple Lambda executions or queue replays that bypass standard idempotency checks.

    You receive a structured diagnostic framework, an evidence-based auditing process, and a customized repair plan including conditional write logic and regression test cases.

    While the skill focuses on AWS services like Lambda, SQS, and DynamoDB, its methodology for S3 sequencer analysis and event genealogy applies to any serverless stack using S3 event notifications.

    The skill requires specific log evidence to function, including S3 version IDs, event payloads, and ledger logs, which it uses to perform a 'Four-Check Audit' of your system.

    Standard idempotency often fails during high-concurrency retries; this skill uses S3 sequencer strings and event genealogy to ensure deduplication logic is safe even during 'retry storms.'

    New in APIs & Backend