skills.rest
HermeticOrmus
HermeticOrmusCOMMUNITY
Explore all skills by this author →
Website𝕏@dbodartmGitHub

Runbook Patterns

Generate standardized runbook templates with symptom, cause, and remedy patterns.

Updated Feb 25, 2026
Search Tags:#documentation#troubleshooting#incident response#runbook#on-call#sre
One-click install
npx skills add https://github.com/HermeticOrmus/LibreCopy-Claude-Code --skill runbook-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Runbook Patterns
Source: https://github.com/HermeticOrmus/LibreCopy-Claude-Code/tree/main/plugins/runbook-writing/skills/runbook-patterns
Command: npx skills add https://github.com/HermeticOrmus/LibreCopy-Claude-Code --skill runbook-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common issue of inconsistent, hard-to-follow runbooks that hinder effective incident response, ensuring on-call engineers can quickly diagnose and resolve issues.

Core Features & Use Cases

  • Standardized Structure: Enforces a clear Symptom → Cause → Remedy pattern.
  • Actionable Commands: Provides self-contained, copy-paste-ready command blocks with expected outputs.
  • Escalation Clarity: Defines deterministic conditions for escalating incidents.
  • Use Case: An on-call engineer receives an alert for a service outage. They immediately access the linked runbook, which guides them through diagnosing common causes with specific commands, applying a fix, and verifying the resolution, all within minutes.

Quick Start

Use the runbook patterns skill to generate a diagnostic command block for checking API server logs.

Frequently Asked Questions about Runbook Patterns

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

FAQPage Schema
How do I structure technical runbooks for faster incident response?▼

To structure technical runbooks for faster incident response, enforce a standardized Symptom, Cause, and Remedy pattern. This provides clear, actionable steps for on-call engineers to quickly diagnose and resolve issues.

What is the best way to document troubleshooting commands for on-call engineers?▼

The best way to document troubleshooting commands is by providing self-contained, copy-paste-ready command blocks complete with expected outputs. This makes runbooks highly actionable and minimizes Mean Time To Resolution.

How do I define deterministic escalation gates in SRE documentation?▼

Deterministic escalation gates in SRE documentation are defined by setting clear, specific conditions within the runbook that explicitly state when an on-call engineer must escalate an incident to another team.

Can I use runbook templates for service outage alerts?▼

Yes, you can use runbook templates for service outage alerts. They guide on-call engineers through diagnosing common causes with specific commands, applying fixes, and verifying the resolution within minutes.

When should I include verification steps in incident response documentation?▼

You should always include verification steps in incident response documentation to confirm a remedy is successful. Enforcing these best practices ensures the actual resolution of the issue and minimizes Mean Time To Resolution.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
devCharuzudevCharuzu

runbook-generator

Generate runbook skeletons for services with start, stop, health, and rollback sections.

Community
Intermediate
act70255act70255

incident-responder

Guide SRE teams through incident response with observability and management frameworks.

Community
Advanced
InnerScopeHearingInnerScopeHearing

incident-runbook-templates

Create structured incident response runbooks with step-by-step procedures and escalation paths.

Official
Advanced