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.
82
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/incident-response/skills/incident-runbook-templates/SKILL.mdQuality
Discovery
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.
This is a well-crafted skill description that clearly communicates specific capabilities, includes natural trigger terms, and explicitly addresses both what the skill does and when to use it. It follows the recommended pattern closely, uses third person voice, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'structured incident response runbooks', 'step-by-step procedures', 'escalation paths', and 'recovery actions'. These are distinct, concrete deliverables. | 3 / 3 |
Completeness | Clearly answers both 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'runbooks', 'incidents', 'incident response', 'escalation paths', 'recovery actions', 'procedures'. These cover the key vocabulary someone working in incident management would use. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around incident response runbooks specifically. Terms like 'runbooks', 'escalation paths', and 'incident response procedures' are distinctive and unlikely to conflict with general documentation or other operational skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with concrete, executable commands and clear workflow sequencing with verification steps. However, it is severely bloated—inlining multiple full runbook templates, communication templates, and best practices that should be split into referenced files. The content explains concepts Claude already knows (severity levels, runbook structure) and would benefit enormously from progressive disclosure.
Suggestions
Move Template 1 (Service Outage), Template 2 (Database Incident), and Communication Templates into separate referenced files (e.g., SERVICE_OUTAGE.md, DATABASE.md, COMMS_TEMPLATES.md) and link to them from a concise overview.
Remove the 'Core Concepts' section explaining severity levels and runbook structure—Claude already knows these; instead, just reference the severity table inline where needed.
Remove the 'Best Practices' and 'Resources' sections, which are generic SRE advice Claude already knows and external links that add token cost without actionable value.
Condense the SKILL.md to a brief overview (~50 lines) showing the runbook pattern with one compact example, then point to detailed templates in separate files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, containing extensive template content that could be referenced in separate files. It explains basic concepts like severity levels and runbook structure that Claude already knows, and includes full communication templates and best practices lists that add significant token overhead. | 1 / 3 |
Actionability | The skill provides fully executable bash commands, SQL queries, kubectl commands, and curl requests that are copy-paste ready. Each mitigation scenario includes specific, concrete step-by-step commands with real tool invocations. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps, verification checkpoints after mitigation (dedicated 'Verification Steps' section), rollback procedures, and an escalation matrix with clear conditions. The triage flow includes a symptom-to-section routing table and explicit feedback loops. | 3 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with all templates, SQL queries, communication templates, and best practices inlined. There are no references to separate files for the detailed templates, database runbook, or communication templates—all of which should be split out. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- Reviewed
Table of Contents
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.