incident-response

Generates severity matrices, response playbooks, and blameless postmortem templates for production services.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill incident-response-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-response
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/incident-response
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill incident-response-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production services break in unanticipated ways, and teams without a documented incident response process improvise under pressure, leading to slow resolution, poor communication, and repeated failures. This Skill produces a complete incident response framework so teams know exactly how to declare, coordinate, resolve, and learn from incidents. ## Core Features & Use Cases - Severity Matrix & Declaration Process: Generates SEV-1/2/3 definitions with response SLAs, escalation rules, and Slack-based incident declaration commands including the Incident Commander role. - Blameless Postmortem Template: Produces a Google SRE-standard postmortem covering summary, timeline, root cause analysis, impact metrics, and corrective actions with owners and due dates. - MTTD/MTTR Tracking & Action-Item Closure: Creates an incident log, feeds DORA change failure rate and MTTR metrics via delivery-record scripts, and tracks open postmortem action items as a reliability metric. - Resilience Verification: Adds DiRT-style game day drills and Wheel of Misfortune role-plays to test runbooks and on-call readiness before real outages. - Use Case: After setting up SLOs and runbooks for a new production API, run this Skill to generate the incident response process, postmortem template, and tracking log, then validate everything with the incident-response-reviewer agent. ## Quick Start Set up a complete incident response process for my production service, including severity levels, a postmortem template, and MTTR tracking.

Frequently Asked Questions about incident-response

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

FAQPage Schema
How do I set up an incident response process for a production service?

Define severity levels (SEV-1/2/3) with response SLAs, document a declaration process with an Incident Commander role, and create a blameless postmortem template. This Skill generates all of these artifacts as wiki documents aligned with Google SRE and PagerDuty standards.

What should a blameless postmortem template include?

A blameless postmortem includes a summary, UTC timeline, root cause analysis, impact metrics, what went well and wrong, and corrective actions with owners and due dates. It follows the Google SRE format and explicitly focuses on systemic issues rather than individual mistakes.

How do I track MTTD and MTTR for incidents?

Track MTTD as alert time to incident declaration and MTTR as declaration to resolution, recorded per incident in a log table. The Skill also feeds these events to delivery-metrics scripts so DORA change failure rate and MTTR are computed from actual incident data.

When should I skip creating an incident response process?

Skip it for local development tools, scripts with no users, and staging-only services. It is required for any production service with users or downstream consumers, especially once observability and SLOs are in place.

How do I make sure postmortem action items actually get done?

File every corrective action as a tracked ticket with an owner and due date, review open items in a weekly ops sync, and block deploys on open P1 items. Track closure rate and age as a reliability metric, since accumulating open actions predicts the next incident.