Agent skill · operations · aiskillstore
incident-runbook-templates
Production-ready templates for incident response runbooks covering detection, triage, mitigation, resolution, and communication.
Why this skill is useful
Provides detailed, actionable incident response templates and procedures that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Incident Runbook Templates Production-ready templates for incident response runbooks covering detection, triage, mitigation, resolution, and communication. Do not use this skill when The task is unrelated to incident runbook templates You need a different domain or tool outside this scope Instructions Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification. If detailed examples are required, open resources/implementation-playbook.md. Use this skill when 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 2. Runbook Structure Runbook Templates Template 1: Service Outage Runbook bash Check service health kubectl get pods -n payments -l app=payment-service Check recent deployments kubectl rollout history deployment/payment-service -n payments Check error rates curl -s "http://prometheus:9090/api/v1/query?query=sum(rate(httprequeststotal{status=~'5..'}[5m]))" bash Step 1: Check pod status kubectl get pods -n payments Step 2: If pods are crash-looping, check logs kubectl logs -n payments -l app=payment-service --tail=100 Step 3: Check recent deployments kubectl rollout history deployment/payment-service -n payments Step 4: ROLLBACK if recent deploy is suspect kubectl rollout undo deployment/payment-service -n payments Step 5: Scale up if resource constrained kubectl scale deployment/payment-service -n payments --replicas=10 Step 6: Verify recovery kubectl rollout status deployment/payment-service -n payments bash Step 1 …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/incident-runbook-templates