Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →onewave-ai/runbook-generator
Generates comprehensive operational runbooks for any system or process. Reads codebase, infrastructure config, and deployment scripts to produce structured runbook.md files formatted for on-call engineers.
Passed 11 of 20 test cases with the skill, and 11 of 20 without it.
and 1 more in the full report
4 fixed8 passed either way8 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Scan our repository to create `runbook.md`. Our codebase has web server code and Terraform configs, but we haven't implemented database backup or disaster recovery scripts yet. How should this missing capability be represented in the generated runbook?
| Checked | Without skill | With skill |
|---|---|---|
| Flags missing backup and recovery mechanisms using the marker `[ACTION REQUIRED]: ...`. | Missed | Passed |
| Refrains from generating non-existent database backup script commands. | Passed | Passed |
The instructions your model reads when the skill loads.
Generate a comprehensive operational runbook.md from a system's codebase, infrastructure config, and deployment scripts -- written for on-call engineers working incidents, deployments, and routine operations at 3am.
references/discovery-patterns.md -- Glob/Grep patterns and config files to inspect during discovery.references/output-template.md -- The full 9-section runbook.md structure to populate.references/writing-style.md -- Clarity, urgency, completeness, formatting, and accuracy rules plus output requirements.references/discovery-patterns.md (Step 1) to identify the stack and infrastructure.references/discovery-patterns.md (Step 2): IaC, containers, CI/CD, app config, deploy scripts, monitoring, migrations, load balancers, docs.references/discovery-patterns.md (Step 3) to surface health checks, metrics, caching, jobs, migrations, rollback, scaling, backups, TLS, secrets, alerting, and more.runbook.md following the structure in references/output-template.md. Cover all 9 sections; adapt content to what discovery found; never include purely speculative sections.references/writing-style.md -- copy-pasteable commands, expected outputs, sequential steps, P1-first ordering, tables for structured data, and the accuracy rules.[VERIFY] and missing sections with [ACTION REQUIRED]: ... so the runbook doubles as a gap analysis.Write runbook.md to the project root (or a directory the user specifies). It must be 500+ lines, cover all 9 sections, contain real commands derived from the codebase, include at least one architecture diagram, carry a complete table of contents, and never fabricate infrastructure details. See references/writing-style.md for the full output checklist.
test cases passed, vs 11 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.