More screenshots

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    AI Production Failure Reconstructor

    1

    Reconstruct production failures from logs, deploy changes, errors, and timelines to identify what happened, why, and how to reproduce it

    Free

    2 installsSecurity scanned
    AI Production Failure Reconstructor

    AI Production Failure Reconstructor

    Example session with this skill installed

    Our checkout API started returning intermittent 500 errors after yesterday's deployment.

    Here is what I have

    Error logs from the affected requests
    Deployment timestamp
    Git diff from the last release
    One successful request
    One failed request
    API response traces

    Reconstruct what happened, identify the most likely trigger, and tell me how to reproduce the failure.

    • Read your context and instructions
    • Compiled the ai production failure

    PRODUCTION FAILURE RECONSTRUCTION

    INCIDENT
    Intermittent checkout API 500 errors after deployment.

    FAILURE TIMELINE

    14:02 — New deployment completed
    14:07 — First failed checkout request
    14:09 — Successful checkout from another session
    14:13 — Repeated failures begin under the same request condition

    STRONGEST EVIDENCE
    The failing requests contain a missing payment-session field that was not present in successful requests.

    LIKELY TRIGGER
    A new checkout path introduced in the latest deployment appears to access the payment-session value before it is initialized.

    CONFIDENCE
    Medium — strong correlation exists, but the causal path requires reproduction.

    REPRODUCTION CONDITIONS
    • New checkout session
    • Payment method selected
    • Specific session state
    • New application version
    • Payment-session initialization delayed

    NEXT TEST
    Replay the failing request sequence against the new build while logging payment-session initialization.

    EXPECTED RESULT
    If the hypothesis is correct, the 500 error should occur when the payment-session value is accessed before initialization.

    REGRESSION TEST
    Add a checkout test covering the delayed-session initialization state.`

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

    About this skill

    AI Production Failure Reconstructor is an evidence-first incident analysis skill for developers and engineering teams dealing with confusing production failures.

    Instead of immediately guessing a fix, it reconstructs the failure as a timeline and connects symptoms to deployments, code changes, requests, errors, environment conditions, and user actions.

    Core workflow

    Failure Timeline

    • Build a chronological sequence of events
    • Align logs, errors, deployments, requests, and user actions
    • Identify the first meaningful deviation

    Trigger Detection

    • Find conditions that may have triggered the failure
    • Compare successful vs failed scenarios
    • Separate correlation from stronger evidence

    Change Correlation

    • Compare recent deploys and code changes
    • Identify suspicious configuration or dependency changes
    • Map changes to affected behavior

    Reproduction Model

    • Convert production evidence into reproducible conditions
    • Define required inputs, environment, timing, state, and sequence
    • Handle intermittent and race-condition scenarios

    Evidence Map

    • Separate confirmed facts from hypotheses
    • Rank evidence by confidence
    • Identify missing evidence needed to confirm the theory

    Verification Plan

    • Define the smallest useful test
    • Create regression scenarios
    • Specify what evidence should appear if the hypothesis is correct

    Output

    • Failure timeline
    • Trigger hypothesis
    • Evidence map
    • Suspected change correlation
    • Reproduction conditions
    • Confidence level
    • Missing-evidence checklist
    • Verification test plan
    • Developer-ready incident handoff

    Perfect for

    • Production incidents
    • Intermittent failures
    • “Works locally” bugs
    • Post-deployment failures
    • Authentication failures
    • API errors
    • Database inconsistencies
    • Race conditions
    • Configuration-related failures
    • Performance regressions

    Important

    This skill does not pretend that a root cause is proven when evidence is incomplete. It clearly separates confirmed evidence, strong hypotheses, weak hypotheses, and unknowns.`

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    2 installs

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 1 month ago

    • Free to download with an account

    Listed1 month ago
    Updated29 days ago

    What's inside

    Frequently Asked Questions