CtrlK
BlogDocsLog inGet started
Tessl Logo

incident-runbook-templates

Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use this skill when building a service outage runbook for a payment processing system; creating database incident procedures covering connection pool exhaustion, replication lag, and disk space alerts; onboarding new on-call engineers who need step-by-step recovery guides written for a 3 AM brain; or standardizing escalation matrices across multiple engineering teams.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable body with strong workflow validation and clean one-level progressive disclosure. The only weakness is mild redundancy: the 'When to Use' list duplicates the description and the severity table re-states widely-known concepts.

Suggestions

Remove or trim the 'When to Use This Skill' bullet list since the same triggers already appear in the frontmatter description, keeping the body from repeating itself.

Consider condensing the SEV1–SEV4 severity table to only the org-specific response-time conventions, since severity definitions are general knowledge Claude already has.

Move the severity table and runbook-structure list into references/details.md so the SKILL.md overview stays purely navigational and actionable.

DimensionReasoningScore

Conciseness

Mostly efficient and code-forward, but the 'When to Use This Skill' bullet list largely restates the frontmatter description and the SEV1–SEV4 severity table is largely general knowledge Claude already has — these could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance — kubectl commands with prerequisite notes, markdown checklists, dry-run/execute SQL blocks, and standing communication templates.

3 / 3

Workflow Clarity

Clear 9-step runbook sequence plus explicit validation checkpoints for destructive operations (dry-run count check, 'EXECUTE only after verifying count < 50', 'If this fails' notes), with a quick checklist for stress conditions.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with a single, clearly signaled one-level-deep reference ('Detailed pattern documentation lives in references/details.md'); the referenced file exists and is well-organized into templates.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong, well-constructed description: third-person, concrete actions, explicit 'Use when' triggers covering multiple realistic scenarios, and a distinctive niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions' — naming specific deliverables rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Create structured incident response runbooks...') and when via a clear 'Use this skill when...' clause with concrete triggering scenarios.

3 / 3

Trigger Term Quality

Covers natural on-call phrasing a user would actually say — 'service outage runbook', 'connection pool exhaustion', 'replication lag', 'disk space alerts', 'onboarding new on-call engineers', 'escalation matrices'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (incident response runbooks) with domain-specific triggers unlikely to fire for unrelated skills; uses third-person voice throughout.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.