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 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). | 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 focus on incident response runbooks specifically is a clear niche. Terms like 'runbooks', 'escalation paths', and 'incident response procedures' are distinct enough to avoid conflicts 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 excellent executable commands and clear workflows. However, it is extremely verbose for a skill file—it reads more like a complete runbook handbook than a concise skill teaching Claude how to create runbooks. The lack of progressive disclosure (no bundle files, no external references) means all content is crammed into one large document, wasting context window budget.
Suggestions
Split the detailed runbook templates (service outage, database incident) into separate bundle files (e.g., templates/service-outage.md, templates/database.md) and reference them from the main SKILL.md
Remove the 'Core Concepts' severity table and 'When to Use This Skill' section—Claude already understands incident severity and can infer when to use the skill from the description
Move communication templates to a separate file (e.g., templates/comms.md) since they are reference material, not core workflow instructions
Cut the 'Best Practices' and 'Resources' sections—these are generic SRE advice that Claude already knows and external links it cannot access
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Includes extensive best practices lists ('Don't assume knowledge', 'Don't skip verification'), explains basic concepts like severity levels that Claude already knows, and provides full communication template examples that bloat the content significantly. The 'When to Use This Skill' section and 'Core Concepts' sections add little value for Claude. | 1 / 3 |
Actionability | Highly actionable with fully executable bash commands, SQL queries, kubectl commands, and curl requests throughout. Every mitigation procedure has copy-paste ready commands with clear step numbering. The diagnostic commands, rollback procedures, and verification steps are all concrete and specific. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflows with clear sequencing (Step 1 through Step 6), explicit verification steps after mitigation, rollback procedures, and a symptom-to-section routing table for triage. The pattern of diagnose → mitigate → verify → rollback is consistently applied with validation checkpoints throughout. | 3 / 3 |
Progressive Disclosure | Monolithic wall of content with no references to external files despite the content being long enough to warrant splitting. The database runbook, communication templates, and best practices could all be separate files. No bundle files exist to support progressive disclosure, and everything is inlined into a single massive document. | 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
b09ec7f
- 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.