incident-runbook-templates

Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/incident-response/skills/incident-runbook-templates/SKILL.md

The canonical home for this skill is incident-runbook-templates in wshobson/agents

Quality

Content

71%Weight 40%Scale 1-5

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

Highly actionable content with executable commands and a clear sequenced workflow including verification and rollback. Its weaknesses are token efficiency and progressive disclosure: the body is long and inlines two complete templates that belong in separate reference files, with some redundant rollback guidance.

Suggestions

Move the two full runbook templates (Service Outage, Database Incident) into separate files under ./references/ and link to them from SKILL.md, keeping only the runbook structure outline and summaries inline.

Consolidate redundant rollback guidance — it appears in both Mitigation 4.1 (Step 4) and the Rollback Procedures section — to reduce length.

Either add the referenced helper scripts (./scripts/smoke-test-payments.sh, ./scripts/db-rollback.sh, curl-format.txt) as bundle files or remove those references, since they currently point at non-existent files.

Dimension	Reasoning	Score
Conciseness	The ~400-line body is mostly concrete commands and templates with little over-explanation of concepts Claude already knows, but it carries two complete inlined runbook templates and redundant rollback steps (Mitigation 4.1 Step 4 vs. the Rollback Procedures section) that could be tightened; not a 4 because the overall volume is high for a SKILL.md.	3 / 5
Actionability	Provides copy-paste-ready, fully executable kubectl, psql, and curl commands covering the common cases (service down, high latency, partial failures, traffic surge, DB pool exhaustion, replication lag, disk space), matching the 5 anchor.	5 / 5
Workflow Clarity	A clearly sequenced runbook structure with a dedicated Verification Steps section, Rollback Procedures, and checkbox triage checklists; validation is present for the destructive/database operations so the cap-at-3 rule does not apply, but it stays at 4 because some checkpoints are implicit inside bash blocks rather than explicit validate->fix->retry feedback loops.	4 / 5
Progressive Disclosure	Has useful section headers, but no bundle files exist and the two full runbook templates (Service Outage, Database Incident) are inlined in SKILL.md rather than split into one-level-deep reference files; additionally, referenced helper scripts (./scripts/smoke-test-payments.sh, ./scripts/db-rollback.sh, curl-format.txt) do not exist as bundle files.	3 / 5
	Total	15 / 20 Passed

Description

83%Weight 40%Scale 1-5

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

A strong, third-person description that clearly states both capability and trigger conditions with natural language. The main gaps are minor: trigger-term synonyms are incomplete and the named actions are category-level rather than maximally concrete.

Dimension	Reasoning	Score
Specificity	Names the domain ('incident response runbooks') and several actions ('step-by-step procedures, escalation paths, and recovery actions'), but these are category-level actions rather than the fully concrete operations seen in the 5 anchor; not below it because coverage is solid with only minor abstraction.	4 / 5
Completeness	Explicitly answers what ('Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions') and when ('Use when building runbooks, responding to incidents, or establishing incident response procedures') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	'building runbooks, responding to incidents, or establishing incident response procedures' are natural phrases a user would say; falls short of 5 because common synonyms like on-call, outage, SEV, and postmortem are missing.	4 / 5
Distinctiveness Conflict Risk	'incident response runbooks' is a clear niche with distinct triggers and low conflict risk; held at 4 rather than 5 because 'responding to incidents' has minor overlap with general SRE/monitoring or on-call skills.	4 / 5
	Total	17 / 20 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: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/incident-response/skills/incident-runbook-templates/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours 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.