incident-response

Guides production incident triage, mitigation, communication, and blameless postmortem workflows.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill incident-response-jin9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/incident-response
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill incident-response-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a production incident fires, teams often lose critical minutes deciding severity, assigning roles, and drafting communications. This Skill provides a structured playbook for classifying severity, scoping blast radius, driving short-term mitigation, and running a blameless postmortem with owned prevention items. ## Core Features & Use Cases - Severity Classification & Triage: Classify incidents as P0–P3, scope blast radius, and follow a first-5-minutes decision sequence including contacting SRE/Operations. - Role-Based Incident Command: Assign Incident Commander, Comms Lead, Ops Lead, and Scribe roles with a severity-bound public communication cadence. - Blameless Postmortems: Produce a postmortem artifact covering summary, impact, root cause, short- and long-term fixes, and prevention items with owners and due dates. - Use Case: Your payment provider's callbacks are timing out and all wallet top-ups are failing. Use this Skill to declare a P0, page SRE, draft a polling-fallback mitigation, send leadership updates every 30 minutes, and later write the postmortem with owned prevention actions. ## Quick Start Ask the agent to triage the current production outage and draft an incident record with severity, blast radius, mitigation plan, and comms cadence.

Frequently Asked Questions about incident-response

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a production incident in the first 5 minutes?▼

Assess the problem scope first, then analyze the initial cause and draft a short-term fix plan, contact SRE/Operations, begin solving, and monitor what was fixed. Classify severity as P0 through P3 to size the response before doing anything else.

How do I write a blameless postmortem after an outage?▼

A blameless postmortem captures a third-party-readable summary, system and user impact, root-cause summary, and short- and long-term fix processes. Every prevention action item must have an owner and due date, and the analysis focuses on cause and prevention rather than blaming individuals.

What severity levels should I use for incident classification?▼

Use four levels: P0 means customers cannot use the product at all, P1 means the core journey is roughly 30–40% degraded, P2 covers edge cases with the core journey intact, and P3 covers wording or pixel-level issues.

When should I not use an incident response playbook?▼

Do not use it for localizing the offending code, which belongs to a debugging skill, or for security breach disclosure specifics, which belong to a security review skill. It covers stabilization, communication, and postmortem, not root-cause code hunting.

How should on-call rotations work for different severity levels?▼

For high or critical-urgent issues, the tech lead acts as primary responder. For medium and low severity, rotate on-call every 4–5 days and work dashboard-first so responders start from monitored signals rather than ad hoc reports.