More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Production Incident Triage Pack

    1

    Triage production incidents in the first 15 minutes: severity, scope, owner, and comms, in that order.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Production Incident Triage Pack

    Production Incident Triage Pack

    Example session with this skill installed

    Apply the skill to a small test input and produce its core output. The script ranks a CSV queue only; it does not set severity, page anyone, or replace the runbook for the affected system.

    • Read your context and instructions
    • Compiled the production incident triage

    A payment service degraded at 14:03, and three alerts arrived within two minutes. The responder declared the incident at 14:05, with a lead and a separate communicator. Scope assessment showed 40 percent of checkouts failing in one region, not a total outage, so severity was set as high but not critical. The last change list showed a routing config change at 13:58, which became the prime suspect. Traffic was shifted away from the affected region at 14:12, restoring most checkouts before the root cause was confirmed at 14:40. The first customer update went out at 14:17, stating scope and a 30-minute cadence, and the live timeline made the post-incident review straightforward. Total customer impact lasted 9 minutes at full effect and 37 minutes at partial effect, against a previous similar incident that had run for two hours without a declared lead or a rollback decision.

    Script demo (verified): running python3 scripts/incident_triage.py on a test file printed INC1 at triage score 64.5 ranked above INC2 at 22.0.

    This is a worked example produced by applying the skill, not a claim about a live customer outcome.

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

    About this skill

    A triage pack for production incidents: a first-15-minutes protocol, a severity and scope assessment, a communication plan, and a handover note that lets the next responder start without re-asking everything. The skill provides a step-by-step protocol with decision points, a decision table, a fill-in template, a checklist, and a scoring rubric, plus a runnable script (incident_triage.py) that scores incidents from a csv by severity, duration, and customers affected, and ranks the triage order. It focuses on finding the bottleneck first and fixing in an order backed by evidence, rather than applying generic advice.

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

    Triage is not resolution; it organises the response so resolution can happen. It does not replace runbooks for specific systems.

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

    Permissions

    Terminal / Shell
    Listed23 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    No. It organises evidence and decisions so judgement is applied to the right question, with a record of why.

    Longer than a generic checklist, because measurement comes first. Later uses are faster once templates and scripts are in place.

    Yes, by narrowing scope explicitly and recording what was skipped. The quality gate still applies to the narrowed work.