runbook-generator – DevOps & Infrastructure skill for AI agents
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 pro
Install the runbook-generator skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/runbook-generator-80338.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /runbook-generator – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/runbook-generator-80338.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $runbook-generator – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/runbook-generator-80338.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /runbook-generator – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/runbook-generator-80338.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /runbook-generator – then describe the task you want done.
SKILL.md content
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
1. Generate the initial skeleton with scripts/runbook_generator.py.
2. Fill in service-specific commands and URLs.
3. Add verification checks and rollback triggers.
4. Dry-run in staging.
5. 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
1. Keep every command copy-pasteable.
2. Include health checks after every critical step.
3. Validate runbooks on a fixed review cadence.
4. Update runbook content after incidents and postmortems.
Related skills
- fedora-hyprland-installer – Install, configure, verify, repair, update, and uninstall Hyprland on Fedora Linux with…
- fedramp-compliance – Implement FedRAMP requirements for federal cloud services. Configure NIST 800-53…
- firebase-app-platform – Build and operate apps on Firebase using Auth, Firestore, Cloud Functions, and Hosting…
- flutter-expert – Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment.
- secrets-vault-manager – Use when the user asks to set up secret management infrastructure, integrate HashiCorp…
- gcp-audit-logs – Configure GCP Cloud Audit Logs for compliance. Set up log routing and BigQuery analysis…
- gcp-cloud-functions – Deploy serverless functions on Google Cloud Functions. Configure triggers and manage…
- gcp-cloud-run – Specialized skill for building production-ready serverless applications on GCP. Covers…