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.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill incident-runbook-templates90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 follows best practices. It uses third person voice, lists specific capabilities, includes a clear 'Use when...' clause with natural trigger terms, and occupies a distinct niche in incident response documentation. The description provides sufficient detail for Claude to confidently select this skill when appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'step-by-step procedures', 'escalation paths', and 'recovery actions'. These are concrete, actionable capabilities rather than vague language. | 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 natural keywords users would say: 'runbooks', 'incidents', 'incident response', 'escalation', 'recovery'. These are terms practitioners naturally use when discussing incident management. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on incident response runbooks with distinct triggers like 'runbooks', 'incident response', 'escalation paths'. Unlikely to conflict with general documentation or other operational skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent executable examples and clear workflow sequences including verification steps. The main weaknesses are moderate verbosity in framing sections and a monolithic structure that could benefit from splitting templates into separate referenced files. The core runbook templates are production-ready and well-organized.
Suggestions
Remove or significantly trim the 'When to Use This Skill' and 'Best Practices' sections - Claude knows when to use runbooks and basic incident response principles
Split the two runbook templates into separate files (e.g., SERVICE_OUTAGE.md, DATABASE_INCIDENT.md) and reference them from the main skill file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary framing (e.g., 'When to Use This Skill' section, 'Best Practices' Do's/Don'ts that Claude already knows). The templates themselves are efficient, but the wrapper content adds bulk. | 2 / 3 |
Actionability | Excellent executable examples throughout - real bash commands, SQL queries, kubectl operations, and curl requests that are copy-paste ready. The templates include specific commands for each scenario with concrete syntax. | 3 / 3 |
Workflow Clarity | Clear numbered sequences with explicit verification steps after mitigation procedures. Includes checklists, decision tables for symptom-to-action mapping, and dedicated verification/rollback sections. The 'Initial Triage (First 5 Minutes)' structure is particularly well-sequenced. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is inline in one large document. The templates could be split into separate files (service-outage.md, database-incident.md) with SKILL.md serving as an overview. External resource links are present but internal structure could be improved. | 2 / 3 |
Total | 10 / 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.
- 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.