Runbook generator
Skill dills122/ai-central/templates/skills/imported/claude-skills/engineering/skills/runbook-generator
Central library for AI coding context: steering files, AGENTS templates, reusable skills, scaffold scripts, and guided setup for new or existing projects.
npx -y skills add dills122/ai-central --skill runbook-generatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows. Templated structure customizable per environment. Use when documenting on-call procedures for a new service, standardizing incident response across teams, or producing runbooks before launching to production.
SKILL.md
2.1 KB, as published. Nobody here has run it
Runbook Generator
Tier: POWERFUL
Category: Engineering
Domain: DevOps / Site Reliability Engineering
Overview
Generate operational runbooks quickly from a service name, then customize for deployment, incident response, maintenance, and rollback workflows.
Core Capabilities
- Runbook skeleton generation from a CLI
- Standard sections for start/stop/health/rollback
- Structured escalation and incident handling placeholders
- Reference templates for deployment and incident playbooks
When to Use
- A service has no runbook and needs a baseline immediately
- Existing runbooks are inconsistent across teams
- On-call onboarding requires standardized operations docs
- You need repeatable runbook scaffolding for new services
Quick Start
# Print runbook to stdout
python3 scripts/runbook_generator.py payments-api
# Write runbook file
python3 scripts/runbook_generator.py payments-api --owner platform --output docs/runbooks/payments-api.md
Recommended Workflow
- Generate the initial skeleton with
scripts/runbook_generator.py. - Fill in service-specific commands and URLs.
- Add verification checks and rollback triggers.
- Dry-run in staging.
- Store runbook in version control near service code.
Reference Docs
references/runbook-templates.md
Common Pitfalls
- Missing rollback triggers or rollback commands
- Steps without expected output checks
- Stale ownership/escalation contacts
- Runbooks never tested outside of incidents
Best Practices
- Keep every command copy-pasteable.
- Include health checks after every critical step.
- Validate runbooks on a fixed review cadence.
- Update runbook content after incidents and postmortems.