Use runbook-generator

Generate an operational runbook for a service

Generate an operational runbook for a service — covering deploy/rollback, common incidents, on-call escalation, SLOs, dashboards, and dependencies.

Reach for it when the user is launching a new service, onboarding to on-call, or being asked for "the runbook" by SRE or production-readiness review.

Install it

npx skilldrop-cli install runbook-generator                 # Claude Code, your user folder
npx skilldrop-cli install runbook-generator --project       # Claude Code, this repo
npx skilldrop-cli install runbook-generator --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the SRE / on-call pack: --pack sre-oncall installs it with its neighbours.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Write an operational runbook for this service"
• "We're launching a service — what does on-call need documented?"
• "Document deploy, rollback, and incident response for this system"
• "Generate the runbook covering escalation and common failures"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Design our SLIs, SLOs, and burn-rate alerts"
• "We're in an incident right now — draft the status page update"
• "Write the postmortem for the outage"

If another skill answers instead, ask for this one by name: "use runbook-generator".

Check what you get

A good result:

• Owner info is current. Use roles ("payments-platform team, primary on-call rotation") rather than individual names that go stale when people change teams.
• Every alert listed has a response. A "what to do when this alert fires" section that doesn't cover all the alerts is worse than no section.
• Rollback is one command, or three steps max. If rollback is complicated, write a script and link to it.
• No "TBD" left in the doc when it's published. Move TBDs to a "known gaps" section so they're explicit, not hidden.

Where a loop runs it

• Stage document of the operate loop

Next

• SKILL.md, the instructions the agent reads
• Its page on the site

Edit this page on GitHub · View source