More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Kafka Streams Changelog Tombstone Restore

    1

    Investigate state-store restoration gaps caused by compacted changelog tombstones

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Kafka Streams Changelog Tombstone Restore

    Repair Kafka Streams Changelog Tombstone Restore

    Example session with this skill installed

    A task restores stale values after a changelog compaction and rebalance.

    Available evidence: changelog offsets (partial). Additional evidence requested: state and configuration snapshot, error and recovery logs, deployment and alert timeline. Review the case, identify open evidence gaps, and do not invent a live test or production change.

    • Read your context and instructions
    • Compiled the repair kafka streams

    Repair Kafka Streams Changelog Tombstone Restore — EVIDENCE-LIMITED REVIEW

    Scenario received

    A task restores stale values after a changelog compaction and rebalance.

    Source register

    • S1: changelog offsets — PARTIAL SOURCE PROVIDED.
    • S2: state and configuration snapshot — NOT PROVIDED; REQUIRED TO VERIFY.
    • S3: error and recovery logs — NOT PROVIDED; REQUIRED TO VERIFY.
    • S4: deployment and alert timeline — NOT PROVIDED; REQUIRED TO VERIFY.

    Concrete checks

    1. trace tombstone order and compaction offsets — PRELIMINARY, NOT VERIFIED.
    2. compare local store snapshots to replay results — AWAITING CORROBORATING EVIDENCE.
    3. crosscheck source timestamps identifiers and changed versions — AWAITING CORROBORATING EVIDENCE.
    4. record exceptions and reversible verification gates — AWAITING CORROBORATING EVIDENCE.

    Deliverables / acceptance gates

    • changelog offsets evidence map: DRAFT / INCOMPLETE until evidence is validated.
    • stale restore exception register: DRAFT / INCOMPLETE until evidence is validated.
    • valid state validation plan: DRAFT / INCOMPLETE until evidence is validated.

    Decision

    INCOMPLETE — HUMAN REVIEW REQUIRED. Confirm dates, IDs, affected scope, owners and acceptance evidence. Do not claim authorization or execution that did not occur.

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

    About this skill

    Kafka Streams applications can suffer from silent data corruption when state-store restoration fails to handle compacted changelog tombstones correctly. This skill provides a systematic framework for investigating restoration gaps and verifying state integrity after rebalances.

    What it does

    • Changelog Tracing maps tombstone order against compaction offsets to identify missed deletions.
    • Snapshot Comparison detects discrepancies between local state-store files and changelog replay results.
    • Timestamp Cross-referencing validates record versions against deployment timelines to isolate stale data.
    • Exception Registration documents every restoration failure or verification gate bypass found in logs.
    • Validation Planning generates a structured plan to restore state consistency without blindly wiping stores.

    How it works

    1. Supply the agent with changelog offsets, state snapshots, and recovery logs.
    2. The agent traces the sequence of tombstones and compares them against local store snapshots.
    3. Observations are classified as VERIFIED or CONTRADICTED based on provided timestamps and IDs.
    4. A state validation plan is generated with specific rollback steps and verification gates.

    Frameworks & tools

    This tool is designed for Kafka Streams applications and requires access to local text-based logs, configuration snapshots, and offset data.

    Why this beats prompting it yourself

    Generic troubleshooting prompts often miss the nuance of Kafka compaction logic. This skill enforces a strict evidence-based discipline, requiring source citations for every inference and preventing hallucinated system measurements.

    Use cases

    • Investigating why a KTable retains deleted keys after a pod restart.
    • Auditing state-store consistency after a significant Kafka broker compaction event.
    • Preparing a safe recovery plan for a consumer group stuck in a crash loop during restoration.

    Known limitations

    Does not perform active cloud or broker side-effects. Requires local text logs and offset data as input. Requires explicit authorization for file modifications.

    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 environments or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.

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

    Permissions

    Read Files

    Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.

    Listed20 days ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the detection of state-store gaps that occur when Kafka compaction prematurely removes tombstones, preventing your KTables from returning stale or 'zombie' data after a rebalance.

    The skill requires text-based logs, state-store snapshots, and changelog offset data; it does not require direct production broker access, ensuring a secure and read-only analysis environment.

    While designed for Kafka Streams, it is compatible with any LLM-based agent that supports file-based context analysis and structured troubleshooting workflows.

    You receive the full investigative framework, a library of tracing logic for compaction offsets, and a structured template for generating verifiable state-store restoration plans.

    No, the skill is designed to analyze and plan; it generates a safe, step-by-step restoration script that you can review and execute manually to maintain full control over your production data.

    New in APIs & Backend