Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Agent Failure Postmortem

    1

    Turn one bad agent run into a blameless postmortem with a root cause and a regression test.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Agent Failure Postmortem

    Agent Failure Postmortem

    Example session with this skill installed

    Our support agent cancelled the wrong subscription: the customer had a personal and a team plan, and it cancelled the team one, then said "Done". Here is the trace. Write the postmortem and the regression test.

    • Read your context and instructions
    • Compiled the agent failure postmortem

    Worked example — illustrative data.

    Postmortem: agent cancelled the team subscription instead of the personal one

    Severity: high (irreversible action, wrong account)
    Impact: 1 reported run; 37 runs in 30 days matched the ambiguity signature.
    Detected by: customer complaint, 6 hours later.

    What happened

    A customer asked to cancel "my subscription" while holding two active subscriptions. The agent picked the team plan without asking, cancelled it, and reported success.

    Timeline

    TimeEvent
    14:02:11user asks to cancel and refund
    14:02:12get_subscriptions returns two plans
    14:02:13cancel_subscription(id=team) — decisive step, no disambiguation
    14:02:14"Done, your subscription is cancelled"

    Cause

    Primary class: ambiguity
    Trigger: two active subscriptions
    Cause: the tool returns a list, the prompt has no rule for choosing, and the model resolved the ambiguity silently
    Contributing: cancel_subscription has no confirmation gate and no destructive hint

    Blast radius

    37 runs with the same signature in 30 days. 1 reported.

    Detection gap

    No eval case covers multiple subscriptions; no alert watches cancel_subscription arguments; success was reported in the reply.

    Action items

    #ActionOwnerVerify by
    1Ask which plan when more than one is activeagentrouting test
    2Require confirmation with plan nameagenttool schema test
    3Alert on cancellations without a prior clarify stepplatformalert fires

    Regression case

    Input: "cancel my subscription" with two active plans.
    Expected: asks which plan, makes no tool call.
    Assertion: must_call_tool false; no destructive call.

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

    About this skill

    Agent failure postmortem: a blameless timeline, the root cause behind the last error, and a regression case that keeps it fixed.

    Use this skill when:

    • an agent did something harmful
    • write an agent postmortem
    • a production agent run failed
    • stop a failure repeating

    Who it's for: Anyone who has shipped an agent.

    Example request

    The agent sent 400 duplicate emails yesterday. Why?

    What the example returns

    • Timeline: five steps, no retry cap
    • Cause: missing idempotency key
    • Regression case and guard added

    In the package: five files — SKILL.md with the trigger and workflow, README.md, references/METHOD.md (the full method), references/CHECKLIST.md (the pass/fail gate) and examples/EXAMPLE.md (a worked run you can copy).

    Works with Claude Code, Cursor, Codex CLI and any agent that reads SKILL.md. Plain markdown: no API key, no account, no network access.

    Agent Failure Postmortem

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Requires execution traces (tool calls, context, logs). Does not provide real-time alerting. Impact analysis depends on provided log data.

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

    Permissions

    Read Files
    Listed3 days ago
    Updated2 days ago

    What's inside

    Frequently Asked Questions

    The skill converts raw execution logs into a structured Markdown report that pinpoints the technical root cause (e.g., retrieval gaps or tool schema errors) and generates a ready-to-use regression test case.

    This skill is framework-agnostic and supports any agent built with LangChain, LlamaIndex, Haystack, or custom implementations, provided you can export the execution trace and model calls.

    While generic prompts often result in 'hallucination' as a catch-all, this skill uses a specialized blameless postmortem logic to identify specific mechanical failures like detection gaps and blast radius impact.

    No complex installation is required; the skill functions as an API-driven analysis tool where you input your trace data to receive the structured postmortem and test assertions.

    The skill works best with a full execution trace including model prompts, tool outputs, and timestamps, but it can still provide partial root-cause analysis with standard text-based logs.

    New in LLM Ops