runbook-writing
Write high-utility runbooks structured for speed, readability, and effective incident mitigation.
Install
mkdir -p .claude/skills/runbook-writing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13450" && unzip -o skill.zip -d .claude/skills/runbook-writing && rm skill.zipInstalls to .claude/skills/runbook-writing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when authoring or editing a runbook that an oncall engineer will read at 3am with a page in hand and incomplete context. Triggers when the user mentions "write a runbook", "this alert needs a runbook", "what should the responder do", "playbook for this alert", "oncall doc", or "I keep getting paged for this and there's no doc". The skill covers the runbook structure that survives sleep deprivation, trigger conditions linked to alert rules, immediate actions ordered by reversibility, escalation tree, related-runbook crosslinks, and post-incident updates. For the alert that fires the page, see monitoring-and-alerting. For the incident response itself once mitigation has happened, see incident-response. For the post-mortem after, see post-mortem-writing.Key capabilities
- →Structure runbooks with six standard sections
- →Align runbook triggers with alert rules
- →Prioritize reversible actions in immediate steps
- →Define clear escalation paths with named individuals
- →Cross-link related runbooks for complete guidance
- →Include maintenance notes for runbook ownership and review
How it works
The skill structures runbooks into specific sections like trigger, immediate actions, diagnosis, mitigation, escalation, and related runbooks, ensuring clarity and usability under stress.
Inputs & outputs
When to use runbook-writing
- →Documenting alert responses
- →Creating incident mitigation steps
- →Establishing escalation trees
- →Updating outdated oncall documentation
About runbook-writing
Focuses on creating runbooks that work under 3am sleep-deprived conditions. Uses structured triggers, reversible actions, and clear escalation paths to minimize incident impact.
Use when authoring or editing a runbook that an oncall engineer will read at 3am with a page in hand and incomplete context. Triggers when the user mentions "write a runbook", "this alert needs a runbook", "what should the responder do", "playbook for this alert", "oncall doc", or "I keep getting pa
When not to use it
- →When designing the alert that fires the page
- →When managing the incident response itself after mitigation
- →When writing a post-mortem after an incident
Limitations
- →Does not cover the design of monitoring and alerting systems
- →Does not cover the incident response process itself
- →Does not cover post-mortem writing
How it compares
This skill enforces a rigid, responder-centric structure for runbooks, prioritizing immediate, reversible actions and clear escalation, which differs from general documentation that might lack this operational focus.
Compared to similar skills
runbook-writing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| runbook-writing (this skill) | 0 | 2mo | No flags | Intermediate |
| postmortem-writing | 17 | 2mo | No flags | Beginner |
| passport | 0 | 2mo | Review | Beginner |
| sre-templates | 0 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
postmortem-writing
wshobson
Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.
passport
puukis
Show or refresh Repo Passport and context — wraps lstack brain passport/context/overview CLI
sre-templates
jeremyary
Operational document templates for SRE artifacts — SLO definitions, alerting rules, runbooks, capacity plans, and post-incident reviews. Referenced by the SRE Engineer agent.
architecture-decision-records
wshobson
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
meeting-minutes
github
Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.
docs-write
metabase
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).