incident-runbook-templates
Build incident runbooks quickly
Teams struggle to document consistent incident response steps during pressure. This skill delivers structured runbook templates with triage, mitigation, and communication sections.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "incident-runbook-templates". Create a service outage runbook for our billing service
Expected outcome:
- Overview and impact checklist for the billing service
- Triage steps with health checks and rollback options
- Mitigation paths for downtime, latency, and partial failures
- Escalation matrix and communication templates for updates
Using "incident-runbook-templates". Draft a database incident runbook for PostgreSQL
Expected outcome:
- Quick reference table with common PostgreSQL diagnostic queries
- Connection pool exhaustion procedures with SQL termination commands
- Replication lag checks and failover decision tree
- Disk space emergency procedures with table size queries
Using "incident-runbook-templates". Create escalation matrix for a SEV1 incident
Expected outcome:
- 15-minute escalation to engineering manager if unresolved
- Security team notification if data breach suspected
- Finance and legal escalation for financial impact over 10k
- Support lead coordination for customer communication
Security Audit
SafePure documentation skill containing only static markdown templates. No executable code, no file system access, no network calls. All 70 static findings are false positives: markdown code blocks were misidentified as Ruby/shell backticks, example URLs were flagged as hardcoded network addresses, and SQL/YAML content was misidentified as weak cryptographic algorithms. The skill generates text templates only.
Risk Factors
⚙️ External commands (40)
🌐 Network access (19)
📁 Filesystem access (1)
Quality Score
What You Can Build
Handle a live outage
Follow structured triage and mitigation steps while keeping stakeholders informed.
Standardize runbooks
Create consistent runbook structure and severity levels across teams.
Learn incident flow
Study templates to understand escalation paths and recovery procedures.
Try These Prompts
Create a concise incident runbook outline for a SaaS API service with detection, triage, mitigation, verification, and communication sections.
Draft a service outage runbook for a payments API. Include triage steps, rollback actions, and escalation contacts.
Create a database incident runbook for PostgreSQL with connection exhaustion, replication lag, and disk space issues.
Extend a runbook with specific alerts, dashboards, and verification metrics for a microservice on Kubernetes.
Best Practices
- Customize commands, dashboards, and contacts before use
- Order steps by urgency and verify each action
- Review and update templates after incidents
Avoid
- Leaving placeholders without owners or contacts
- Including steps that require undocumented tribal knowledge
- Skipping verification and rollback guidance