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.
Creator: Engineering
License: MIT
Source Repo:neekware/dojo-skillsSource Bucket:engineeringOriginal Path:engineering/runbook-generator
1---2name: runbook-generator-23description: Runbook Generator4---5# Runbook Generator67**Tier:** POWERFUL 8**Category:** Engineering 9**Domain:** DevOps / Site Reliability Engineering1011---1213## Overview1415Generate operational runbooks quickly from a service name, then customize for deployment, incident response, maintenance, and rollback workflows.1617## Core Capabilities1819- Runbook skeleton generation from a CLI20- Standard sections for start/stop/health/rollback21- Structured escalation and incident handling placeholders22- Reference templates for deployment and incident playbooks2324---2526## When to Use2728- A service has no runbook and needs a baseline immediately29- Existing runbooks are inconsistent across teams30- On-call onboarding requires standardized operations docs31- You need repeatable runbook scaffolding for new services3233---3435## Quick Start3637```bash38# Print runbook to stdout39python3 scripts/runbook_generator.py payments-api4041# Write runbook file42python3 scripts/runbook_generator.py payments-api --owner platform --output docs/runbooks/payments-api.md43```4445---4647## Recommended Workflow48491. Generate the initial skeleton with `scripts/runbook_generator.py.md`.502. Fill in service-specific commands and URLs.513. Add verification checks and rollback triggers.524. Dry-run in staging.535. Store runbook in version control near service code.5455> **Note:** Bundled scripts ship as Markdown reference (`.md`) — copy the code out of the `.md` file to run it.5657---5859## Reference Docs6061- `references/runbook-templates.md`6263---6465## Common Pitfalls6667- Missing rollback triggers or rollback commands68- Steps without expected output checks69- Stale ownership/escalation contacts70- Runbooks never tested outside of incidents7172## Best Practices73741. Keep every command copy-pasteable.752. Include health checks after every critical step.763. Validate runbooks on a fixed review cadence.774. Update runbook content after incidents and postmortems.7879> **Creator:** Engineering80> **License:** MIT81> **Source Repo:** `neekware/dojo-skills`82> **Source Bucket:** `engineering`83> **Original Path:** `engineering/runbook-generator`
Run npx skillmds@latest add neekware/runbook-generator-2 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. 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