Agent skill · operations · thebushidocollective
runbooks-structure
Use when creating structured operational runbooks for human operators. Covers runbook organization, documentation patterns, and best practices for clear operational procedures.
Why this skill is useful
Provides a comprehensive structured template for operational runbooks that includes specific commands and procedures not commonly found in generic documentation.
What it needs
About 7k tokens when loaded. Last updated 2026-07-19. 187 stars on the source repository.
What this skill does
Runbooks - Structure Creating clear, actionable runbooks for operational tasks, maintenance, and troubleshooting. What is a Runbook? A runbook is step-by-step documentation for operational tasks: Troubleshooting - Diagnosing and fixing issues Incident Response - Handling production incidents Maintenance - Routine operational tasks On-Call - Reference for on-call engineers Basic Runbook Structure Minimum Viable Runbook Comprehensive Runbook Template bash Check pod status kubectl get pods -n production Expected output: All pods Running bash View recent logs kubectl logs -n production deployment/api-server --tail=100 bash Connect to RDS metrics aws cloudwatch get-metric-statistics \ --namespace AWS/RDS \ --metric-name DatabaseConnections \ --dimensions Name=DBInstanceIdentifier,Value=prod-db bash kubectl drain pod/api-server-abc123 --ignore-daemonsets bash kubectl get pods -n production grep api-server bash Edit configmap kubectl edit configmap app-config -n production Change: DBPOOLSIZE: "10" To: DBPOOLSIZE: "20" bash kubectl rollout restart deployment/api-server -n production bash kubectl rollout status deployment/api-server -n production bash Rollback to previous version kubectl rollout undo deployment/api-server -n production Verify rollback kubectl rollout status deployment/api-server -n production markdown Database Connection Troubleshooting Pod Restart Procedures Incident Response Guide Runbook Organization Directory Structure Best Practices Write for Clarity bash kubectl get pods -n production -l app=api-server bash kubectl delete pod <pod-name> -n production bash kubectl get pods -n production -l app=api-server Include Decision Trees bash curl -f https://api.example.com/health bash kubectl get pods -n production Provide Expected Outputs bash psql -h prod-db.example.com -U app -c "SELECT 1" ?column? ---------- 1 (1 row) Use Checklists Common Patterns Emergency Response bash kubectl set env deployment/api-server MAINTENANCEMODE=true Routine Maintenance bash aws …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thebushidocollective/runbook-structure