Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Incident Command

    1

    A command-line framework for managing incident timelines, blameless postmortems, and actionable follow-ups.

    $6.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Incident Command

    Incident Command

    Example session with this skill installed

    We have a SEV2: API 5xx errors spiked to 12% after the 14:10 deploy. I've rolled back and errors are subsiding. Start the incident record and give me the first notice for customers.

    • Read your context and instructions
    • Compiled the incident command

    Created incident folder docs/incidents/INC-20250522-api-5xx-spike/ and initialized the timeline.

    Incident Initialized: INC-20250522-api-5xx-spike

    FieldValue
    SeveritySEV2 (Major Degradation)
    StatusMitigated (Rollback complete)
    Log Entry2025-05-22T14:28Z [human] incident opened; rollback confirmed via CI
    Comms CadenceHourly updates required

    First Notice (Customer-Facing)

    Subject: Investigating API Performance Issues
    Copy: We are currently investigating an issue causing increased error rates (5xx) for API requests. Users may experience failed requests or service timeouts. A rollback has been initiated and we are seeing initial signs of recovery. We will provide the next update in 60 minutes or as soon as new information is available.

    Timeline Preview

    - 2025-05-22T14:10Z [deploy] deploy-prod-v2.4.1 completed
    - 2025-05-22T14:15Z [alert] PagerDuty: api-global-5xx > 10%
    - 2025-05-22T14:22Z [human] rollback started by @dev-on-call
    - 2025-05-22T14:26Z [deploy] rollback to v2.4.0 complete
    - 2025-05-22T14:28Z [human] incident folder created; status mitigated
    

    Next steps

    1. Run incident-kit.sh log "verbatim error from logs" --source log to capture the specific failure signature.
    2. Draft the resolution notice once error rates return to baseline for 15 minutes.
    3. Schedule the postmortem for no later than May 25th.

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

    About this skill

    Technical incidents usually result in two things: a frantic fix and a fragmented record. This skill ensures the record survives the chaos so that future teams can reconstruct exactly what happened, what customers were told, and what changed without asking anyone. It enforces a rigorous documentation standard that turns Slack threads and fuzzy memories into a structured repository of timelines, comms, and postmortems.

    What it does

    • Standardizes incident structure by initializing a dedicated folder for every event containing timelines, postmortems, and action items.
    • Captures live evidence using source-tagged logging (alert, human, deploy, chat) to prevent retrospective bias.
    • Generates status communications based on severity ladders, providing ready-to-send templates for first notice, updates, and resolution.
    • Drives blameless postmortems through a structured root-cause ladder and quantified impact analysis.
    • Tracks action items by enforcing single-owner accountability and hard due dates for every follow-up task.
    • Surfaces recurring failures by searching past incident signatures to identify if a fix from months ago has failed.

    How it works

    1. Initialize the incident folder using incident-kit.sh new <slug> the moment an alert fires or degradation is noticed.
    2. Log events in real-time with incident-kit.sh log "..." --source <type> to build a timestamped, source-tagged timeline.
    3. Draft comms using the severity-based templates in references/comms-templates.md to update stakeholders on a fixed cadence.
    4. Conduct postmortem within three days by filling out the template, focusing on system properties rather than human error.
    5. Manage follow-ups by auditing actions --open until every item is marked as done or explicitly dropped.

    Frameworks & tools

    The skill uses a Bash-based CLI (incident-kit.sh) to manage a flat-file Markdown architecture. It is designed for developers working in environments where Git-based documentation is the source of truth for engineering operations.

    Why this beats prompting it yourself

    Standard prompting often produces generic "lessons learned" summaries that lack technical teeth. This skill enforces specific constraints: it prevents you from guessing causes in comms, rejects ownerless action items, and forces source-tagging to identify gaps in your observability.

    Use cases

    • Managing production outages to keep a live, timestamped log of mitigations and decisions.
    • Writing technical postmortems that actually identify root causes instead of blaming the on-call engineer.
    • Audit-ready record keeping for security events or data loss incidents where a paper trail is mandatory.
    • Closing engineering loops by tracking long-term prevent-type action items that usually get forgotten in Jira.

    Known limitations

    This is a documentation and process framework, not an automated monitoring or observability tool. It requires manual input or CLI triggers to capture human decisions and chat context.

    Manual logging or CLI triggers required. Does not integrate directly with PagerDuty/Slack APIs. Focused on Markdown record-keeping, not automated infrastructure recovery.

    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 1 month ago

    Permissions

    Terminal / Shell
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill provides a structured CLI framework that forces real-time, source-tagged logging and standardized folder structures, preventing the data loss and 'retrospective bias' that occurs when relying on generic chat summaries or memory.

    The skill is designed for AI agents with terminal access or local file system permissions, and it integrates seamlessly into Git-based workflows where Markdown is the standard for engineering documentation.

    You receive the core `incident-kit.sh` CLI tool, a suite of severity-based communication templates, structured postmortem schemas, and a guide on integrating the framework into your existing SRE or DevOps workflow.

    No, this is a documentation and process enforcement tool; it captures the 'why' and 'when' of human decisions and system changes, complementing your existing monitoring tools like Datadog or Prometheus.

    Setup involves adding the script to your local path and initializing your central incident repository; once configured, your AI agent can manage the entire lifecycle from the command line.

    The tool generates flat Markdown files, making it easy to version control your incident history in Git, perform full-text searches across past outages, and ensure your records are audit-ready.

    New in DevOps & Cloud