Incident Runbook Templates

When your payment service goes down at 2 AM and you're fumbling through Slack history for that kubectl command, you need structured runbooks that work under pressure. This generates comprehensive incident response procedures with specific bash commands, escalation matrices, and communication templates. It covers service outages, database issues, traffic spikes, and partial failures with actual troubleshooting steps like checking pod status, rolling back deployments, and killing slow queries. The templates include verification commands, rollback procedures, and severity-based escalation paths. Essential for teams moving from "figure it out as we go" to standardized incident response that works when your brain is running on caffeine and adrenaline.

skills.sh installs: 11.4K
GitHub stars: 42.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add wshobson/agents --skill incident-runbook-templates --agent claude-code

Installs into .claude/skills of the current project.

Files

Incident Runbook Templates

Production-ready templates for incident response runbooks covering detection, triage, mitigation, resolution, and communication.

When to Use This Skill

Creating incident response procedures
Building service-specific runbooks
Establishing escalation paths
Documenting recovery procedures
Responding to active incidents
Onboarding on-call engineers

Core Concepts

1. Incident Severity Levels

Severity	Impact	Response Time	Example
SEV1	Complete outage, data loss	15 min	Production down
SEV2	Major degradation	30 min	Critical feature broken
SEV3	Minor impact	2 hours	Non-critical bug
SEV4	Minimal impact	Next business day	Cosmetic issue