runbook-writing

Generate operational incident runbooks with exact alert matching and structured sections.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill runbook-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runbook-writing
Source: https://github.com/ohsonerdy/openclaw-frontier-stack/tree/main/skills/runbook-writing
Command: npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill runbook-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents oncall responders from getting stuck during incidents by ensuring runbooks are structured for fast, correct action even when they have little context and high urgency.

Core Features & Use Cases

  • Stress-proof structure: Enforces a consistent six-section format (Title/Trigger, Immediate actions, Diagnosis, Mitigation, Escalation, Related runbooks) in the responder’s read order.
  • Precise alert matching: Guides runbook titles and trigger conditions to match alert names and alert rules character-for-character for reliable discovery.
  • Actionable execution under pressure: Prioritizes reversible, bounded blast-radius immediate actions, then moves deeper investigation to Diagnosis.
  • Safety and durability: Requires irreversibility/high-risk steps to be explicitly annotated with escalation/IC sign-off expectations, and adds post-incident maintenance guidance.
  • Crosslinking for correctness: Uses related-runbook crosslinks (upstream/downstream/adjacent) so responders can quickly route to the right playbook.

Quick Start

Use the runbook-writing skill to draft a new runbook for an alert by matching the runbook title exactly to the alert name and filling the six required sections with reversible immediate actions, targeted diagnosis checks, clear mitigation steps, an escalation tree with explicit criteria, and related runbook crosslinks.

Frequently Asked Questions about runbook-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an incident runbook that oncall responders can follow during an active alert?

An effective incident runbook uses a six-section structure in the responder's read order: Title/Trigger, Immediate actions, Diagnosis, Mitigation, Escalation, and Related runbooks. This ensures fast, correct action under paging-time pressure.

What should immediate actions in an SRE runbook include to be safe during incidents?

Immediate actions in an SRE runbook should prioritize reversible, bounded blast-radius steps. Any irreversible or high-risk actions must be explicitly annotated with escalation and IC sign-off expectations before execution.

How do I structure runbook trigger conditions to match alerting rules correctly?

Runbook trigger conditions require exact character-for-character matching with alert names and alert rules. This precise alert matching ensures responders can reliably discover the correct playbook during an incident.

When should I update stale oncall runbooks in an operations documentation library?

Stale oncall runbooks should be updated during post-incident maintenance cycles. This is when you add safety annotations for irreversible steps and verify that runbook titles still match alert rules exactly.

Why do runbooks need related-runbook crosslinks for incident response?

Related-runbook crosslinks connect upstream, downstream, and adjacent playbooks so responders can quickly route to the correct operational documentation. This prevents getting stuck when an alert requires context from dependent systems.

Can I use this runbook-writing approach for new alerts without existing documentation?

Yes, this runbook-writing approach applies to authoring new runbooks for new alerts. It guides you to match the runbook title exactly to the alert name and fill the six required sections with targeted diagnosis checks and clear escalation criteria.