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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/incident-runbook-templates/SKILL.md

Quality

Content

67%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 multi-step workflows including verification. Its main weakness is structure: at ~330 lines with two full templates inlined and no bundle files or external references, it functions as a monolithic document rather than an overview pointing to detailed materials. Some repetition also leaves room for tightening.

Suggestions

Move the two full runbook templates (Service Outage, Database Incident) into separate files under references/ (e.g., templates/service-outage.md, templates/database.md) and have SKILL.md summarize the structure with links, improving progressive_disclosure and conciseness.

Add explicit validate->fix->retry feedback loops around destructive operations such as pg_terminate_backend, VACUUM FULL, and kubectl rollout undo (e.g., verify impact before and after each destructive step) to push workflow_clarity to 5.

De-duplicate repeated commands (kubectl rollout history, rollback procedures appear in multiple sections) and reference a single canonical block to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The body avoids conceptual padding and is mostly executable code/tables, but at ~330 lines it repeats content (rollback and kubectl rollout history appear in multiple sections) and inlines a second full template that could be trimmed or split out. Matches 'mostly efficient but could be tightened'; not 4 because more than minor trimming is needed, not 2 because there is no explanatory padding of concepts Claude already knows.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands (kubectl, psql, curl with real flags) covering the common cases — service down, high latency, partial failures, traffic surge, and DB incidents. Matches the top anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	Multi-step processes are clearly sequenced with numbered steps (e.g., Initial Triage 'First 5 Minutes', Steps 1-6 in mitigation) plus a dedicated Verification Steps section and rollback procedures. Not 5 because destructive ops like pg_terminate_backend and VACUUM FULL lack an explicit validate->fix->retry feedback loop; not 3 because verification and checklists are present.	4 / 5
Progressive Disclosure	No bundle files exist and all content — two full runbook templates, complete SQL quick-reference, and communication templates — is inlined in SKILL.md, which clearly belongs in separate reference files. Matches 'content that clearly belongs in separate files is inlined'; not 3 because despite section headers there is no external file structure or signaled references to offset the monolithic bulk, not 1 because there is some internal section organization.	2 / 5
	Total	14 / 20 Passed

Description

87%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.

The description is strong: it clearly states a specific capability and pairs it with an explicit 'Use when...' trigger clause, satisfying both the what and when requirements. Trigger terms are natural and the niche is distinct from other skills. Minor improvement is possible by adding synonyms (on-call, SEV, alerting, postmortem) for fuller keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (incident response runbooks) and several concrete actions — 'step-by-step procedures, escalation paths, and recovery actions' — matching the 'several specific actions; minor gaps' anchor. Not 5 because the actions are generic verbs rather than a comprehensive enumerated capability list; not 3 because it clearly lists more than 1-2 actions.	4 / 5
Completeness	Explicitly 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') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say — 'building runbooks, responding to incidents, or establishing incident response procedures' — giving good keyword coverage. Not 5 because it omits common synonyms like on-call, SEV, alerting, or postmortem; not 3 because coverage is solidly beyond minimal.	4 / 5
Distinctiveness Conflict Risk	'Incident response runbooks' is a clear niche with distinct triggers (runbooks, incidents, incident response procedures) and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	18 / 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: rmyndharis/antigravity-skills
Path: skills/incident-runbook-templates/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.