Runbook Generator
Generate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows.
Before & after
Same prompt, same agent — the only difference is the skill.
Here's an on-call runbook structure for a payments service: **Service Overview**: What the service does and its dependencies **Deployment**: How to deploy and roll back **Common Issues**: Known problems and their fixes **Monitoring**: Dashboards and alerts to watch **Escalation**: Who to contact and when **Incident Response**: Steps to take during an outage For a payments service specifically, you'd want to pay attention to: - Transaction failures and reconciliation - Third-party payment provider outages - Idempotency and duplicate charges Would you like me to fill in any of these sections?
RUNBOOK — Payments Service · env: production
Templated structure, payments-specific where it counts.
SERVICE
Owns: charge creation, refunds, provider webhooks
Critical deps: Stripe (provider), Postgres (ledger), Redis (idempotency)
Blast radius if down: no new charges. Existing subscriptions unaffected
until renewal. This framing tells on-call how hard to page.
DEPLOY
Command, health-check URL, expected green signal.
ROLLBACK — the section on-call actually opens at 3am, so it's first:
1. Payments is ledger-critical. NEVER roll back if a migration
changed the ledger schema — roll FORWARD with a fix. Rolling
back a schema on a payments DB is how you double-charge.
2. For code-only changes: <exact rollback command>
3. After rollback: verify idempotency keys still resolve (Redis)
INCIDENT RESPONSE — by symptom, not generic steps
Charges failing broadly
→ Check Stripe status page FIRST. Provider outage is the most
common cause and nothing you do fixes it — comms, don't debug.
Duplicate charges reported
→ Idempotency layer. Check Redis health and key TTLs. This is the
one that generates refunds and angry customers — highest urgency.
Webhook backlog
→ Provider events queuing. Check consumer lag; replay is safe
BECAUSE the ledger is idempotent — confirm that before replaying.
MAINTENANCE
Reconciliation job schedule, what a healthy run looks like, what a
mismatch means (investigate, never auto-correct a ledger).
MONITORING
Dashboards: charge success rate, provider latency, idempotency hit
rate, ledger reconciliation delta. Alert thresholds per metric.
ESCALATION
L1 on-call → L2 payments owner (15 min no-resolve) → finance lead if
money is miscounted, not just if the service is down.
THE PAYMENTS-SPECIFIC RULE ON EVERY PAGE
When unsure, favor NOT charging over maybe-double-charging. A failed
charge retries clean; a double charge is a refund, a support ticket, and
a trust hit.
Want the deploy/rollback commands filled in for your actual pipeline?About this skill
name: runbook-generator description: Use when Generate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows.
Runbook Generator
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.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the runbook-generator skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Runbook Generator; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: runbook-generator
description: Use this skill when documenting on-call procedures for a service, standardizing incident response across teams, or producing runbooks before a production launch.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Runbook Generator
Generates operational runbooks from a service name, covering deployment, incident response, maintenance, and rollback procedures.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.