incident-runbook-templates

Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use this skill when building a service outage runbook for a payment processing system; creating database incident procedures covering connection pool exhaustion, replication lag, and disk space alerts; onboarding new on-call engineers who need step-by-step recovery guides written for a 3 AM brain; or standardizing escalation matrices across multiple engineering teams.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and well-structured with executable commands, validation checkpoints, and a clean one-level reference to details.md. Its only weakness is mild verbosity in the Best Practices / Do's-and-Don'ts sections, which restate guidance already implied elsewhere.

Suggestions

Trim the Best Practices Do's/Don'ts list to non-obvious items only, since most of that advice is already demonstrated in the troubleshooting examples and core concepts.

Consider moving the generic severity-level table into references/details.md if it is rarely needed at a glance, keeping the SKILL.md body focused on actionable patterns.

The communication-template and escalation-matrix material duplicated in details.md could be summarized in the body with a pointer rather than partially restated.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable examples that earn their tokens, but the Do's/Don'ts and Best Practices lists restate generic advice that overlaps with the troubleshooting and core-concept sections, so it could be tightened further.	2 / 3
Actionability	Concrete, copy-paste-ready commands appear throughout — kubectl, curl, psql, feature-flag calls — with specific flags and example payloads, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Multi-step procedures are numbered and sequenced with explicit validation checkpoints (dry-run output checks, "Verify recovery", rollback steps) and feedback loops for destructive SQL, fitting the clear-sequence anchor.	3 / 3
Progressive Disclosure	The SKILL.md is an overview that points to one-level-deep references/details.md with a clear signal ("Read that file when the navigation tier above is insufficient"), and that referenced file exists, giving well-organized navigation.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it names concrete actions, includes natural trigger terms users would actually say, and explicitly covers both what it does and when to use it. It occupies a clear niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	"Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions" lists multiple concrete actions, matching the score-3 anchor.	3 / 3
Completeness	It states what the skill does (create runbooks with procedures, escalation, recovery) and provides an explicit "Use this skill when..." clause with concrete triggering scenarios, satisfying both what and when.	3 / 3
Trigger Term Quality	Natural terms a user would say appear throughout — "service outage runbook", "payment processing system", "connection pool exhaustion, replication lag, and disk space alerts", "escalation matrices" — giving broad coverage.	3 / 3
Distinctiveness Conflict Risk	The incident-runbook niche with domain-specific triggers (payment outages, DB pool exhaustion, on-call onboarding) is clearly distinguishable from other skills and unlikely to fire for the wrong one.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Commit: 2b48f16

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.