AgentAlley
Submit

Runbook generator

Generate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/runbook-generator.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/engineering/skills/runbook-generator#main ~/.claude/skills/runbook-generator

For one project only, change the path to .claude/skills/runbook-generator.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Runbook generator

Show the full text77 lines
runbook-generator/SKILL.md77 lines · 2.1 KB
Outline
RawView on GitHub
namedescription
runbook-generatorGenerate 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

  • 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
  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.
1---
2name: "runbook-generator"
3description: "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 
16Generate 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
40python3 scripts/runbook_generator.py payments-api
41 
42# Write runbook file
43python3 scripts/runbook_generator.py payments-api --owner platform --output docs/runbooks/payments-api.md
44```
45 
46---
47 
48## Recommended Workflow
49 
501. Generate the initial skeleton with `scripts/runbook_generator.py`.
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.
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 
731. Keep every command copy-pasteable.
742. Include health checks after every critical step.
753. Validate runbooks on a fixed review cadence.
764. Update runbook content after incidents and postmortems.
77 

Discussion

Alternatives

Also in DebuggingSee all 533 in Development →
Systematic debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesCoding · MITVerification before completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysCoding · MITDebugging strategiesMaster systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.Coding · MITError handling patternsMaster error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.Coding · MIT

Browse more free Claude skills or everything in Development.