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.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/incident-response/skills/incident-runbook-templates/SKILL.md

The canonical home for this skill is incident-runbook-templates in wshobson/agents

Quality

Content

71%Weight 40%Scale 1-5

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

The content is highly actionable with concrete, executable commands and well-sequenced incident workflows including verification steps, but it is a monolithic 400-line file that inlines full templates which belong in separate reference files, and it has notable redundancy and broken code fencing inside the templates. Tightening and splitting the templates into bundle files would substantially improve token efficiency and navigability.

Suggestions

Move the full runbook templates into separate reference files (e.g., templates/service-outage.md, templates/database-incident.md) and keep SKILL.md as a concise overview with clearly signaled links.

Fix the mismatched code fences in Template 1 (early-closing fence at line 93) and Template 2 (```markdown closed with ```` plus a stray fence at line 383) so template boundaries are unambiguous.

Remove redundancy: drop the "When to Use This Skill" section that duplicates the description, and consolidate rollback commands that currently appear in both section 4.1 and "Rollback Procedures".

Dimension	Reasoning	Score
Conciseness	The body is command-dense rather than padded, but "When to Use This Skill" duplicates the frontmatter description, rollback commands appear in both section 4.1 and "Rollback Procedures", and the severity/structure tables add length that could be trimmed — mostly efficient with some unnecessary material (anchor 3).	3 / 5
Actionability	Templates contain fully executable, copy-paste-ready kubectl, psql, curl, and Prometheus query commands with concrete metric names and thresholds, plus filled-in communication templates covering the common incident cases, matching anchor 5.	5 / 5
Workflow Clarity	The runbook structure gives a clear detection → triage → mitigation → verification → rollback sequence with checklists and a dedicated verification section, but Template 1's outer code fence closes early (line 93) leaving later sections ambiguous, and Template 2's fencing is mismatched with a stray fence at line 383 — minor gaps versus anchor 5.	4 / 5
Progressive Disclosure	There are no bundle files (references/, scripts/, assets/ absent) and the two full runbook templates (300+ lines) are inlined in SKILL.md where separate template files would serve better; clear section headers keep it navigable, so it sits at anchor 3 rather than 2.	3 / 5
	Total	15 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 description that clearly and explicitly states both capability and trigger conditions in third person with concrete language. The only improvements are broader synonym coverage in the trigger clause and unpacking the single composite action into more distinct capabilities.

Suggestions

Add natural trigger synonyms such as on-call, outage, SEV, paging, or postmortem to the "Use when" clause.

Consider naming additional distinct capabilities (e.g., severity classification, communication templates, postmortem guides) to raise specificity.

Dimension	Reasoning	Score
Specificity	"Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions" lists several concrete capability components, but they are all facets of a single action (creating runbooks) rather than multiple distinct actions, matching anchor 4 rather than 5.	4 / 5
Completeness	It explicitly answers both "what" (create runbooks with procedures, escalation paths, and recovery actions) and "when" ("Use when building runbooks, responding to incidents, or establishing incident response procedures") with concrete trigger phrases, matching the anchor-5 example structure.	5 / 5
Trigger Term Quality	"building runbooks, responding to incidents, establishing incident response procedures" provides good natural trigger phrasing, though common synonyms such as on-call, outage, SEV, postmortem, or paging are missing, so it falls short of comprehensive anchor-5 coverage.	4 / 5
Distinctiveness Conflict Risk	"Incident response runbooks" is a clear niche with distinct triggers, but there is minor overlap risk with generic ops/SRE or incident-management skills, placing it at anchor 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/incident-response/skills/incident-runbook-templates/SKILL.md
Commit: a65ce00

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.