Generate the initial skeleton with scripts/runbook_generator.py.md.
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.
Note: Bundled scripts ship as Markdown reference (.md) — copy the code out of the .md file to run it.
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.
1---2name: runbook-generator3description: Runbook Generator4---56# Runbook Generator78**Tier:** POWERFUL 9**Category:** Engineering 10**Domain:** DevOps / Site Reliability Engineering1112---1314## Overview1516Generate operational runbooks quickly from a service name, then customize for deployment, incident response, maintenance, and rollback workflows.1718## Core Capabilities1920- Runbook skeleton generation from a CLI21- Standard sections for start/stop/health/rollback22- Structured escalation and incident handling placeholders23- Reference templates for deployment and incident playbooks2425---2627## When to Use2829- A service has no runbook and needs a baseline immediately30- Existing runbooks are inconsistent across teams31- On-call onboarding requires standardized operations docs32- You need repeatable runbook scaffolding for new services3334---3536## Quick Start3738```bash39# Print runbook to stdout40python3 scripts/runbook_generator.py payments-api4142# Write runbook file43python3 scripts/runbook_generator.py payments-api --owner platform --output docs/runbooks/payments-api.md44```4546---4748## Recommended Workflow49501. Generate the initial skeleton with `scripts/runbook_generator.py.md`.512. Fill in service-specific commands and URLs.523. Add verification checks and rollback triggers.534. Dry-run in staging.545. Store runbook in version control near service code.5556> **Note:** Bundled scripts ship as Markdown reference (`.md`) — copy the code out of the `.md` file to run it.5758---5960## Reference Docs6162- `references/runbook-templates.md`6364---6566## Common Pitfalls6768- Missing rollback triggers or rollback commands69- Steps without expected output checks70- Stale ownership/escalation contacts71- Runbooks never tested outside of incidents7273## Best Practices74751. Keep every command copy-pasteable.762. Include health checks after every critical step.773. Validate runbooks on a fixed review cadence.784. Update runbook content after incidents and postmortems.
Run npx skillmds@latest add neekware/runbook-generator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Runbook Generator It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
neekware (@neekware) published this skill. Their other Agent Skills are listed on their SkillMD profile.
neekware