Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    AI Automation Incident Evidence Pack

    1

    Turn redacted n8n, Zapier, Make, webhook, API, or script incident observations into a first-hour evidence register and safe client/engineer handoff before repair or retry decisions.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    AI Automation Incident Evidence Pack

    AI Automation Incident Evidence Pack

    Example session with this skill installed

    {"incident_id":"INC-DEMO-001","summary":"Order sync timed out after sending a request.","retry_status":"unknown","observations":[{"evidence_id":"E-001","source":"redacted run history","timestamp":"2026-07-31T10:00:00+08:00","type":"api","observation":"HTTP request timed out; downstream receipt is unknown."}]}

    • Read your context and instructions
    • Compiled the ai automation incident

    Provisional failure stage: external_dependency (evidence E-001)
    Root cause: unknown
    Side-effect risk: high
    Next step: obtain the request ID, timeout boundary, and downstream receipt.
    Safety: do not retry production while outcome or side effects are unknown.

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

    About this skill

    When a client automation times out, silently misses work, duplicates an action, loses authentication, or skips a schedule, this local read-only pack stabilizes the supplied facts before anyone changes production. One sanitized JSON input produces a deterministic evidence register and incident brief containing an evidence-ID-bound timeline, knowns and unknowns, provisional failure stage, side-effect/data-loss risk, missing-evidence requests, bounded reproduction plan, ownership handoff, and client-safe update.

    The pack does not access platforms, execute workflows, collect credentials, retry operations, repair production, monitor systems, audit general reliability, write a postmortem, or guarantee root cause.

    Output is bounded by supplied redacted evidence and cannot prove completeness. Screenshots/OCR, vendor dashboard inspection, and deleted-log recovery are out of scope. Keyword/type classification is provisional triage, not causation. Common token/contact patterns are redacted, but buyers must sanitize inputs. No production access, repair, retry authorization, monitoring, security forensics, legal advice, or platform assurance is provided.

    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 any payment.

    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

    File Scopes

    *.json
    incident-evidence-output/**

    Runs locally, reads only the supplied redacted JSON, and writes deterministic evidence outputs to a new local folder. No browser, network, environment-variable, credential, or production access.

    Listed3 months ago

    What's inside

    Frequently Asked Questions

    This skill provides a structured, read-only framework to stabilize incident facts immediately after an automation failure, preventing "guess-and-check" repairs that can cause further data loss or side effects.

    It is compatible with any LLM-based agent capable of processing JSON, including ChatGPT, Claude, and custom agentic frameworks, provided they can interpret structured text inputs.

    No, the pack is designed for local, read-only analysis; it does not require access to your production workflows, API keys, or platform credentials to generate the evidence register.

    You receive the core logic framework for the evidence register, a standardized template for sanitized JSON inputs, and specific instructions for generating client-safe incident briefs.

    Yes, the pack is platform-agnostic and works with any system that can produce log output or incident observations, including custom scripts, webhooks, and REST APIs.

    The Evidence Pack is intended for the "Golden Hour" of an incident—stabilizing information and preparing for handoff—rather than long-term monitoring or post-incident reliability auditing.

    New in Workflow Automation