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 strong skill description that clearly defines what the skill does with specific concrete actions and provides explicit trigger guidance via a 'Use when...' clause. The trigger terms are natural and comprehensive, covering the key vocabulary users would employ. The description is concise, uses third person voice correctly, and occupies a distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'structured incident response runbooks', 'step-by-step procedures', 'escalation paths', and 'recovery actions'. These are concrete, well-defined 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 | Clearly occupies a distinct niche around incident response runbooks specifically. The combination of 'runbooks', 'escalation paths', 'incident response', and 'recovery actions' creates a well-defined domain unlikely to conflict with other 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 provides highly actionable, well-structured incident response templates with executable commands and clear workflows, but suffers significantly from being a massive monolithic document. The content would be far more effective as a concise overview in SKILL.md pointing to separate template files, rather than inlining hundreds of lines of templates, communication examples, and best practices that consume excessive token budget.
Suggestions
Split the runbook templates into separate referenced files (e.g., SERVICE-OUTAGE.md, DATABASE-INCIDENT.md, COMMUNICATION-TEMPLATES.md) and keep SKILL.md as a concise overview with navigation links.
Remove the 'Core Concepts' section on severity levels and runbook structure - Claude already knows these concepts and they add ~20 lines of unnecessary context.
Remove the 'Best Practices' and 'Resources' sections which contain generic incident management advice that Claude already knows, or condense to 2-3 project-specific constraints.
Trim the 'When to Use This Skill' section which lists obvious use cases that can be inferred from the skill title.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, containing extensive template content that could be referenced externally. It explains basic concepts like severity levels and runbook structure that Claude already knows, and includes full communication templates and best practices lists that are largely common knowledge for incident response. | 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 procedures are clearly numbered and sequenced with explicit verification steps after mitigation (dedicated 'Verification Steps' section), rollback procedures, and a classification table that routes symptoms to specific resolution sections. Feedback loops are present (e.g., 'If errors: fix and re-validate' pattern in rollback/verification). | 3 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of content with no references to external files. The full runbook templates, communication templates, database runbook, and best practices are all inlined when they should be split into separate referenced files (e.g., TEMPLATES.md, DATABASE-RUNBOOK.md, COMMUNICATION.md). | 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
6e3d68c
- 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.