Runbook writing

Skill shinzoxD/knackbox/skills/documents/runbook-writing

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

Install

npx -y skills add shinzoxD/knackbox --skill runbook-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write operational runbooks that on-call engineers can follow under stress. Use whenever the user asks for a runbook, playbook, ops procedure, alert response guide, or how to document incident response steps for a system.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, as published. Nobody here has run it

Runbook Writing

Runbooks are for 3 a.m. brains. Short steps, copy-pasteable commands, clear stop conditions, and escalation paths.

Workflow

Scope: service, symptoms/alerts that trigger this runbook, severity.
Preconditions: access, dashboards, feature flags, dependencies.
Diagnosis steps with expected outputs.
Mitigation steps (customer impact first) then durable fix pointers.
Rollback / communications / escalation.
Post-incident: what to capture for the postmortem.

Output format

# Runbook: <title>
**Service:** …
**Alert / symptom:** …
**Severity guidance:** …
**Last reviewed:** …

## Overview
One paragraph.

## Dashboards & signals
- …

## Diagnosis
1. …

## Mitigation
1. …

## Escalation
- …

## Rollback
…

## Do not
- …

## Related
links / owners / code paths

Rules

Imperative steps; one action per step.
Commands in copy-paste blocks with placeholders like <cluster>.
Never require tribal knowledge without a link or command to discover it.
Separate customer mitigation from root-cause engineering.
Include "when to stop and escalate".
Mark destructive steps with danger and confirmation.

Edge cases

Partial outage: branch the path by symptom.
Security incident: avoid spreading exploit detail; point to secure channel.
No prod access in doc context: still structure the runbook; mark missing commands clearly.