Skills incident-runbook-templates
๐Ÿ“ฆ

incident-runbook-templates

Content revision r1 Safe โš™๏ธ External commands๐ŸŒ Network access๐Ÿ“ Filesystem access

Create Incident Runbook Templates

Incident teams need clear steps before outages happen. This skill provides structured runbook templates for triage, mitigation, recovery, escalation, and updates.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "incident-runbook-templates" from https://skillstore.io/skills/wshobson-incident-runbook-templates.md and its manifest at https://skillstore.io/api/skills/wshobson-incident-runbook-templates/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "incident-runbook-templates". Create an outage runbook for a payment service.

Expected outcome:

  • A structured runbook with service ownership, impact assessment, alerts, triage, mitigation paths, rollback steps, verification checks, and communication templates.
  • A severity-based escalation matrix for engineering, security, finance, legal, and support stakeholders.

Using "incident-runbook-templates". Prepare a database incident runbook for replication lag.

Expected outcome:

  • A database-focused procedure covering lag assessment, replica health checks, failover considerations, recovery validation, and escalation timing.
  • A checklist that separates diagnostic checks from production-changing actions.

Using "incident-runbook-templates". Standardize incident updates for on-call teams.

Expected outcome:

  • Internal notification, status update, and resolution message templates with fields for severity, impact, owner, actions, and next update time.
  • Guidance for keeping stakeholders informed during investigation, mitigation, and recovery.

Security Audit

Safe
v8 โ€ข 7/7/2026 Open versioned report

Static command, network, and filesystem hits are documentation examples inside SKILL.md, not executable skill code. No evidence found of prompt injection, credential exfiltration, hidden network activity, or malicious intent. Operators should still adapt example incident commands before production use.

1
Files scanned
384
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/wshobson-incident-runbook-templates/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/wshobson-incident-runbook-templates/security.svg)](https://skillstore.io/skills/wshobson-incident-runbook-templates?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/wshobson-incident-runbook-templates?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wshobson-incident-runbook-templates/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/wshobson-incident-runbook-templates.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

wshobson. (2026). incident-runbook-templates security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wshobson-incident-runbook-templates/audits/8

BibTeX citation

@techreport{wshobson-wshobson-incident-runbook-templates-2026, author = {wshobson}, title = {incident-runbook-templates security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/wshobson-incident-runbook-templates/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "incident-runbook-templates security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "wshobson" date-released: "2026-07-07" url: "https://skillstore.io/skills/wshobson-incident-runbook-templates/audits/8" identifiers: - type: other value: "skillstore:wshobson-incident-runbook-templates:audit:8" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
wshobson Recommended Current

wshobson-incident-runbook-templates

Skillstore Score 78
Evidence Confidence High
Skillstore usage 15
Updated

2026-08-21

sickn33-incident-runbook-templates

Skillstore Score 69
Evidence Confidence High
Skillstore usage 11
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
72
Community
83
Spec Compliance

What You Can Build

Service Outage Preparation

Create a repeatable outage runbook for a production service before the next on-call rotation.

Database Incident Response

Draft a database runbook covering connection pressure, replication lag, disk space, rollback, and verification.

Incident Communication Standardization

Prepare consistent internal updates, escalation paths, and resolution messages for high-severity incidents.

Try These Prompts

Create a Basic Runbook
Use the incident-runbook-templates skill to create a SEV2 runbook for [service]. Include impact, alerts, first triage, mitigation, rollback, verification, escalation, and communication sections.
Adapt a Database Runbook
Create a database incident runbook for [database]. Cover connection pool exhaustion, replication lag, disk pressure, safe rollback, validation checks, and escalation contacts.
Build Active Incident Steps
Draft an active incident runbook for [current symptoms]. Separate diagnostic steps from mitigation steps. Mark any production-changing action for human approval before execution.
Standardize a Runbook Portfolio
Design a runbook template library for [organization]. Include severity definitions, required sections, owner metadata, review cadence, escalation matrices, and communication templates.

Best Practices

  • Replace sample service names, endpoints, dashboards, and contacts with approved internal references.
  • Mark any rollback, scaling, database, or network action for review before execution.
  • Review each runbook after incidents and test it during scheduled readiness exercises.

Avoid

  • Do not paste example commands into production without environment-specific review.
  • Do not omit verification, rollback, or escalation sections from high-severity runbooks.
  • Do not rely on one person for incident decisions when escalation criteria are met.

Frequently Asked Questions

Does this skill execute incident response commands?
No. It provides runbook templates and example procedures that operators must review before use.
Which incidents does it cover?
It covers service outages, degraded latency, partial failures, traffic surges, database pressure, replication lag, and disk pressure.
Can I use it with Claude, Codex, and Claude Code?
Yes. The report lists support for Claude, Codex, and Claude Code.
Does it include communication templates?
Yes. It includes initial incident notices, status updates, resolution messages, and escalation matrix examples.
Is it ready for regulated environments?
Not by itself. Legal, compliance, and security teams should review runbooks before regulated production use.
How should teams maintain generated runbooks?
Teams should update runbooks after incidents, ownership changes, alert changes, and scheduled readiness tests.

Developer Details

Author

wshobson

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

36e07d5e13068e5be64447e8f20b427cf2cbd21a

Maintenance freshness

7/18/2026

Usage

10 downloads ยท 335 views

File structure

๐Ÿ“„ SKILL.md

More from wshobson

View all
View all