runbook-gen

To generate an SRE runbook for incident response, you can use this skill to produce operational templates that structure severity classification, time-boxed diagnosis, resolution steps, and escalation paths for on-call procedures.

A blameless post-mortem focuses on system and process causes rather than individual blame. This skill generates a structured post-mortem template with an incident timeline, verification checklists, and tracked action items.

To set up a war room during an outage, this skill provides templates for war-room setup, customer communications, and incident timeline documentation, ensuring coordinated response across Slack, Zoom, and status page updates.

Yes, you can create an escalation matrix for different severity levels. The skill applies an SRE severity matrix to set response SLAs and defines escalation paths across primary, secondary, engineering manager, and VP contacts.

An operational runbook for a degraded-performance incident should include a detection and diagnosis decision tree, resolution steps, copy-paste-friendly command placeholders, and a verification checklist to confirm system recovery.

Automated runbook generation for customer communications follows defined negative-use boundaries to prevent inappropriate outputs. It produces SRE-aligned guidance and templates but requires human review before sending external status page updates.