Agent skill · operations · thebushidocollective
runbooks-incident-response
Use when creating incident response procedures and on-call playbooks. Covers incident management, communication protocols, and post-mortem documentation.
Why this skill is useful
Provides detailed incident response procedures and specific Bash commands for managing incidents that the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. About 8k tokens when loaded. Last updated 2026-07-19. 187 stars on the source repository.
What this skill does
Runbooks - Incident Response Creating effective incident response procedures for handling production incidents and on-call scenarios. Incident Response Framework Incident Severity Levels SEV-1 (Critical) Complete service outage Data loss or security breach Major customer impact (>50% of users) Response Time: Immediate Escalation: Page on-call + manager SEV-2 (High) Partial service degradation Affecting significant users (10-50%) Performance issues (>50% slower) Response Time: Within 15 minutes Escalation: Page on-call SEV-3 (Medium) Minor degradation Affecting few users (<10%) Non-critical features broken Response Time: Within 1 hour Escalation: On-call handles during business hours SEV-4 (Low) Cosmetic issues Internal tools affected No customer impact Response Time: Next business day Escalation: Create ticket, no page Incident Response Template bash Check current status curl https://api.example.com/health kubectl get pods -n production Incident: API Outage Started: 2025-01-15 14:30 UTC Severity: SEV-1 Timeline: 14:30 - Alert fired 14:31 - On-call acknowledged 14:32 - Assessed as SEV-1 14:33 - Created incident channel bash Check recent deploys kubectl rollout history deployment/api-server Rollback if deployed < 30 min ago kubectl rollout undo deployment/api-server bash Increase replicas kubectl scale deployment/api-server --replicas=20 bash Restart pods kubectl rollout restart deployment/api-server bash Disable failing external service calls kubectl set env deployment/api-server FEATUREEXTERNALAPI=false markdown [14:45] UPDATE Status: Investigating Impact: API returning 503 errors. ~75% of requests failing. Actions Taken: Rolled back deploy from 14:25 Increased pod replicas to 15 Next Steps: Monitoring rollback impact Investigating database connection issues ETA: Unknown Customer Impact: Users cannot place orders. Workaround: None available. markdown Status Messages Investigating: We are aware of elevated error rates on the API. Investigating the root cause. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thebushidocollective/incident-response--5f32ff