2
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill 89jobrien/steve --skill devops-runbooks- SKILL.md1.4 KB
Overview
This skill produces actionable operational runbooks and procedure documentation for incident response, maintenance, and knowledge transfer. It focuses on clear step-by-step procedures, verifiable commands, and explicit rollback and escalation instructions. Use it to turn tribal operational knowledge into repeatable, testable runbooks that teams can follow under pressure.
How this skill works
The skill inspects the target system context and desired outcome, then generates a structured runbook following a proven template: Overview, Prerequisites, Quick Reference, Procedure, Rollback, Troubleshooting, and Escalation. It outputs copy-pasteable commands, expected outputs for verification, decision points, and contact information for escalation. The runbooks are concise, test-oriented, and designed for on-call and incident use.
When to use it
- Creating incident response procedures for production outages
- Documenting on-call playbooks and escalation paths
- Preparing system maintenance or deployment procedures
- Designing disaster recovery and rollback plans
- Transferring operational knowledge between teams
Best practices
- Provide copy-pasteable commands and exact file paths or URLs
- Include expected output or verification steps for each action
- Define rollback actions at every risky step and test them regularly
- Call out decision points and criteria for escalation explicitly
- Keep runbooks versioned and review them after incidents
Example use cases
- Write an incident runbook for a web service 503 error, with triage steps and quick fixes
- Create a scheduled maintenance runbook for database schema migration with rollback
- Draft an on-call escalation guide with contacts, paging rules, and SLA thresholds
- Generate a disaster recovery procedure for restoring from backups and validating integrity
- Produce a troubleshooting guide for degraded performance including metrics to check
FAQ
Yes. Specify environment labels (staging, production) and include environment-specific commands and verification steps.
How are escalation contacts handled?
List primary and secondary contacts with roles, contact methods, and when to escalate based on defined thresholds.
What verification should be included?
Include exact commands, expected outputs, log locations, and success criteria so responders can confirm the system state.