More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Kafka Producer Epoch Fencing Recovery

    1

    Resolve producer epoch fencing after transactional failover.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Kafka Producer Epoch Fencing Recovery

    Repair Kafka Producer Epoch Fencing Recovery

    Example session with this skill installed

    A transactional producer restarts with reused identity after broker leadership changes.

    Available evidence: producer transaction logs (partial). Additional evidence requested: reference policy or configuration, event and change timeline, owner review or test record. Review this case; identify evidence gaps; do not invent a live test or production action.

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

    Repair Kafka Producer Epoch Fencing Recovery — EVIDENCE-LIMITED REVIEW

    Scenario received

    A transactional producer restarts with reused identity after broker leadership changes.

    Source register

    • S1: producer transaction logs — PARTIAL SOURCE PROVIDED.
    • S2: reference policy or configuration — NOT PROVIDED; REQUIRED TO VERIFY.
    • S3: event and change timeline — NOT PROVIDED; REQUIRED TO VERIFY.
    • S4: owner review or test record — NOT PROVIDED; REQUIRED TO VERIFY.

    Concrete checks

    1. Correlate producer transaction logs with the authorized baseline — AWAITING CORROBORATING EVIDENCE.
    2. Isolate epoch conflict and repeat fencing using matching identifiers — AWAITING CORROBORATING EVIDENCE.
    3. Cross-check timestamps, versions and source ownership — AWAITING CORROBORATING EVIDENCE.
    4. Prepare reversible checks for bounded producer recovery plan — AWAITING CORROBORATING EVIDENCE.

    Deliverables / acceptance gates

    • producer transaction logs traceability map: DRAFT / INCOMPLETE until evidence is validated.
    • epoch conflict and repeat fencing exception register: DRAFT / INCOMPLETE until evidence is validated.
    • bounded producer recovery plan 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

    Repair Kafka Producer Epoch Fencing Recovery is a ToolForge Labs ChatGPT Skill workflow. Resolve producer epoch fencing after transactional failover.

    What this skill checks

    1. Correlate producer transaction logs with the authorized baseline.
    2. Isolate epoch conflict and repeat fencing using matching identifiers.
    3. Cross-check timestamps, versions and source ownership.
    4. Prepare reversible checks for bounded producer recovery plan.

    What to provide

    • producer transaction logs.
    • reference policy or configuration.
    • event and change timeline.
    • owner review or test record.

    Deliverables

    • producer transaction logs traceability map.
    • epoch conflict and repeat fencing exception register.
    • bounded producer recovery plan validation plan.

    Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions and missing inputs; no unperformed live tests, external changes, or approvals are claimed.

    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 19 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.

    Listed19 days ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill is designed for Kafka clusters using transactional producers, including Confluent Cloud, AWS MSK, and self-managed deployments. It works with standard Kafka client logs and configuration files from any compliant AI agent platform.

    Unlike generic troubleshooting, this skill uses a formal diagnostic framework that maps every recovery step to specific log timestamps. It prevents common mistakes like 'zombie' fencing or accidental data loss caused by prematurely resetting transactional IDs.

    No direct connection is required. You provide the relevant transaction logs, configuration policies, and event timelines as context, and the skill performs the diagnostic analysis and planning based on that data.

    You receive the full diagnostic workflow, the evidence-led recovery plan generator, and a structured reporting template. It also includes the 'Assertion Classification' system to help you audit the AI's conclusions for technical accuracy.

    The skill identifies the root cause and provides a step-by-step, reversible recovery plan. However, for security and safety, the actual execution of those steps—such as restarting producers or updating ACLs—must be performed by an authorized human operator.

    New in APIs & Backend