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

88%

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

Quality

Content

77%

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

The body is highly actionable with clear, verified workflows backed by real commands and rollback paths. Its main weaknesses are mild padding in generic instruction sections and a monolithic structure with references to non-existent bundle files.

Suggestions

Remove or tighten the generic 'Instructions' and 'Do not use this skill when' sections, which restate obvious guidance without adding runbook-specific value.

Split the full runbook templates into one-level-deep reference files (e.g. references/service-outage-runbook.md, references/database-incident-runbook.md) and link them from a concise overview, improving progressive disclosure.

Either provide the referenced ./scripts/smoke-test-payments.sh and ./scripts/db-rollback.sh as bundle scripts or replace the references with inline commands so they are not dangling paths.

Dimension	Reasoning	Score
Conciseness	Mostly efficient executable templates and commands, but the generic 'Instructions' section ('Clarify goals, constraints... Apply relevant best practices') and 'Do not use this skill when' boilerplate add padding that could be trimmed.	2 / 3
Actionability	Provides fully executable kubectl/psql/curl commands, checkboxes, escalation matrices, and copy-paste-ready communication templates rather than pseudocode or abstract descriptions.	3 / 3
Workflow Clarity	Clear numbered sequencing with explicit verification checkpoints ('Verify service is healthy', error-rate/latency checks), rollback escape hatches, and checklists for risky operations like deployment rollback and query termination.	3 / 3
Progressive Disclosure	Well-organized sections but monolithic at ~390 lines with two full runbook templates and communication templates all inline; referenced scripts (./scripts/smoke-test-payments.sh, ./scripts/db-rollback.sh) are not provided as bundle files.	2 / 3
	Total	10 / 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.

The description is strong across all dimensions: it states concrete capabilities, includes explicit third-person triggers, and carves out a distinctive niche. No first/second-person voice issues are present.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities — 'step-by-step procedures, escalation paths, and recovery actions' — matching the anchor that lists several specific actions rather than naming only a domain.	3 / 3
Completeness	Explicitly answers both what (create structured runbooks) and when via a 'Use when building runbooks, responding to incidents...' trigger clause.	3 / 3
Trigger Term Quality	Covers natural phrasings a user would say — 'building runbooks, responding to incidents, or establishing incident response procedures' — giving good coverage rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (incident response runbooks) with distinct triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	12 / 12 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: e63f7dd

Reviewed: about 23 hours 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.