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.
65
77%
Does it follow best practices?
Impact
—
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 third-person voice convention and is concise without being vague. The description is comparable to the good examples in the rubric.
| 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). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'runbooks', 'incidents', 'incident response', 'escalation paths', 'recovery actions', 'procedures'. These cover the main terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around incident response runbooks specifically, with distinct trigger terms like 'runbooks', 'escalation paths', and 'incident response procedures' that are 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.
This skill provides highly actionable, well-structured incident response templates with executable commands and clear workflows, but it is far too verbose for a SKILL.md file. The content reads more like a complete runbook documentation site than a concise skill instruction, with extensive example content that inflates token usage. The lack of any progressive disclosure or bundle structure means all ~300+ lines must be loaded into context every time.
Suggestions
Reduce the SKILL.md to a concise overview (~50-80 lines) covering the runbook structure, severity levels, and one compact example template, then move the full service outage template, database template, and communication templates into separate bundle files (e.g., SERVICE_OUTAGE.md, DATABASE.md, COMMUNICATION.md).
Remove the 'Best Practices' do's/don'ts section and external resource links — Claude already knows incident management best practices and these add token cost without actionable value.
Remove the 'When to Use This Skill' section — this duplicates the skill description metadata and explains obvious use cases.
Trim communication templates to one example with a note about the pattern rather than three full examples that are largely repetitive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Includes extensive boilerplate (do's/don'ts lists, external resource links, communication template examples, severity level definitions) that Claude already knows or could generate on demand. The templates are largely example content rather than reusable instruction, and much of this could be condensed or split into separate reference files. | 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 steps with real commands rather than pseudocode. | 3 / 3 |
Workflow Clarity | Multi-step procedures are clearly numbered and sequenced (Steps 1-6 for service down, Steps 1-5 for high latency, etc.). Verification steps are explicit, rollback procedures are documented, and the triage section includes a symptom-to-section routing table. Feedback loops are present (verify recovery after rollback, re-validate after fixes). | 3 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no bundle files or references to separate documents. The database runbook template, communication templates, and best practices sections could all be separate files. The content is a wall of text that would benefit significantly from being split into focused reference files. | 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
bbc5ade
- 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.