More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Lost Events Across Services

    1

    Trace and repair events that disappear between producers, outboxes, brokers, consumers, retries, checkpoints, and databases.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Lost Events Across Services

    Repair Lost Events Across Services

    Example session with this skill installed

    Some 'order_placed' events are missing in the shipping service even though the order service shows them as created. Check the Kafka path and the consumer logic.

    • Read your context and instructions
    • Compiled the repair lost events

    Found loss boundary: Consumer 'shipping-worker' acknowledges Kafka offsets before the database transaction commits. If the process crashes mid-handler, the event is lost. Fix: Moved manual ack to after successful DB commit. Added transactional inbox to prevent duplicates on redelivery.

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

    About this skill

    The problem

    Event-driven systems often suffer from "silent" data loss where a message disappears between the producer and the database. Developers struggle to distinguish between network delays, consumer lag, misconfigured retention, or early acknowledgments that kill redelivery.

    What it does

    • Traces logical event identities across producers, outboxes, brokers, and consumers to find the exact loss boundary.
    • Identifies failures in the delivery chain, such as commit-before-persist bugs or consumer checkpoint skipping.
    • Detects "poison events" trapped in dead-letter queues or suppressed by incorrect deduplication logic.
    • Implements architecture-compatible repairs like transactional outboxes, stable correlation IDs, and idempotent replays.
    • Validates event paths using deterministic failure injection and end-to-end verification tests.

    Frameworks & tools

    Works with message brokers and streaming platforms including Kafka, RabbitMQ, SQS, Pub/Sub, and NATS. Supports various persistence layers and outbox patterns.

    Why this beats prompting it yourself

    Generic prompts often suggest "just checking logs" or blind replays that cause duplicate side effects. This skill enforces a strict evidence chain, requiring proof of persistence at every durable boundary before suggesting a fix.

    Use cases

    • Finding why a successful checkout event never triggered a fulfillment record.
    • Diagnosing messages that vanish when a consumer service restarts during a rebalance.
    • Repairing gaps in event streams caused by broker retention expiry or TTL settings.
    • Auditing complex multi-hop event paths to ensure stable correlation and causation.

    Known limitations

    Requires a safe development or test environment for failure injection. Cannot recover historical events that were never durably recorded by the producer or broker.

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

    Requires test environment for failure injection. Cannot recover historical events if no durable record (outbox/broker) exists. Scope limited to established event path stages.

    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 3 months ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Permissions are limited to the active local workspace. They are used to inspect user-supplied or local project files; create or modify bounded local fixes, tests, documentation, or review artifacts; run repository-supported local tests, checks, builds, or parsing commands. The skill package does not require bundled credentials, unrestricted external network access, or automatic production changes.

    Listed3 months ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill traces logical event identities across your entire delivery chain—from producers and outboxes to brokers and consumers—to pinpoint exactly where messages disappear and implement architectural fixes like idempotent replays.

    It is compatible with all major message brokers including Kafka, RabbitMQ, AWS SQS, Google Pub/Sub, and NATS, as well as common persistence patterns like the Transactional Outbox.

    No, this skill cannot recover 'ghost' events that were never durably recorded; it requires at least one point of durable persistence (like a producer outbox or broker log) to initiate a repair or replay.

    The purchase includes the core logic for event path auditing, failure injection playbooks for testing, and pre-configured templates for implementing stable correlation IDs and deduplication logic.

    The skill performs a non-invasive audit of your current event flow first; however, implementing repairs or failure injections should be done in a staging environment to ensure idempotent handling before moving to production.

    New in Agents & Orchestration