Generate operational runbooks from a service name

Runbook generator

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

Generate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows. Templated structure customizable per environment.

---
name: "runbook-generator"
description: "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."
---

# 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

Overview

Tier: POWERFUL Category: Engineering Domain: DevOps / Site Reliability Engineering

Manual install (npx, ZIP)

Claude Codenpx skills add alirezarezvani/claude-skills --skill runbook-generator -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \
  | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/engineering/skills/runbook-generator

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/66059d223ae12a801299/runbook-generator.zip" -OutFile "$env:TEMP\runbook-generator.zip"; Expand-Archive "$env:TEMP\runbook-generator.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.1 KB
references/1 file · 1.1 KB
scripts/1 file · 2.8 KB

Read the files here

alirezarezvani/19392f73 files

SKILL.md2.1 KB

SKILL.md

Show the full text77 lines

runbook-generator/SKILL.md77 lines · 2.1 KB

PreviewCode

Outline

RawView on GitHub

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.

1	---
2	name: "runbook-generator"
3	description: "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."
4	---
5
6	# Runbook Generator
7
8	Tier: POWERFUL
9	Category: Engineering
10	Domain: DevOps / Site Reliability Engineering
11
12	---
13
14	## Overview
15
16	Generate operational runbooks quickly from a service name, then customize for deployment, incident response, maintenance, and rollback workflows.
17
18	## Core Capabilities
19
20	- Runbook skeleton generation from a CLI
21	- Standard sections for start/stop/health/rollback
22	- Structured escalation and incident handling placeholders
23	- Reference templates for deployment and incident playbooks
24
25	---
26
27	## When to Use
28
29	- A service has no runbook and needs a baseline immediately
30	- Existing runbooks are inconsistent across teams
31	- On-call onboarding requires standardized operations docs
32	- You need repeatable runbook scaffolding for new services
33
34	---
35
36	## Quick Start
37
38	```bash
39	# Print runbook to stdout
40	python3 scripts/runbook_generator.py payments-api
41
42	# Write runbook file
43	python3 scripts/runbook_generator.py payments-api --owner platform --output docs/runbooks/payments-api.md
44	```
45
46	---
47
48	## Recommended Workflow
49
50	1. Generate the initial skeleton with `scripts/runbook_generator.py`.
51	2. Fill in service-specific commands and URLs.
52	3. Add verification checks and rollback triggers.
53	4. Dry-run in staging.
54	5. Store runbook in version control near service code.
55
56	---
57
58	## Reference Docs
59
60	- `references/runbook-templates.md`
61
62	---
63
64	## Common Pitfalls
65
66	- Missing rollback triggers or rollback commands
67	- Steps without expected output checks
68	- Stale ownership/escalation contacts
69	- Runbooks never tested outside of incidents
70
71	## Best Practices
72
73	1. Keep every command copy-pasteable.
74	2. Include health checks after every critical step.
75	3. Validate runbooks on a fixed review cadence.
76	4. Update runbook content after incidents and postmortems.
77