Agent skill · operations · thebushidocollective
runbooks-troubleshooting-guides
Use when creating troubleshooting guides and diagnostic procedures for operational issues. Covers problem diagnosis, root cause analysis, and systematic debugging.
Why this skill is useful
Provides a structured troubleshooting framework with specific commands and procedures that the AI wouldn't reliably generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-07-19. 187 stars on the source repository.
What this skill does
Runbooks - Troubleshooting Guides Creating effective troubleshooting guides for diagnosing and resolving operational issues. Troubleshooting Framework The 5-Step Method 1. Observe - Gather symptoms and data 2. Hypothesize - Form theories about root cause 3. Test - Validate hypotheses with experiments 4. Fix - Apply solution 5. Verify - Confirm resolution Basic Troubleshooting Guide bash kubectl get pods -n production grep api-server bash kubectl rollout history deployment/api-server bash Check database connections kubectl exec -it api-server-abc -- psql -h $DBHOST -c "SELECT count() FROM pgstatactivity" bash Check request rate curl -H "Authorization: Bearer $DDAPIKEY" \ "https://api.datadoghq.com/api/v1/query?query=sum:nginx.requests{}" bash Check third-party API curl -w "@curl-format.txt" https://api.stripe.com/v1/charges bash kubectl rollout restart deployment/api-server -n production bash kubectl scale deployment/api-server --replicas=10 -n production Decision Tree Format Check response time ┌──────────────┴──────────────┐ │ │ < 500ms > 500ms │ │ NOT THIS RUNBOOK Continue below bash Check which service is slow curl -w "@timing.txt" https://api.example.com/users bash Check active queries psql -c "SELECT query, state, querystart FROM pgstatactivity WHERE state != 'idle'" Layered Troubleshooting Layer 1: Application bash curl https://api.example.com/health bash kubectl logs deployment/api-server --tail=100 grep ERROR Layer 2: Infrastructure bash kubectl top nodes bash kubectl top pods -n production bash kubectl run -it --rm debug --image=nicolaka/netshoot --restart=Never -- ping database.internal Layer 3: External Dependencies bash curl -w "@timing.txt" https://api.stripe.com/health bash nslookup api.stripe.com dig api.stripe.com Systematic Debugging Use the Scientific Method bash aws rds describe-db-instances --db-instance-identifier prod-db jq '.DBInstances[0].DBInstanceStatus' bash aws ec2 describe-security-groups --group-ids sg-abc123 jq '.SecurityGroups[0].IpPe …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thebushidocollective/troubleshooting-guides