eng-runbook
An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief mentions "runbook", "ops doc", "on-call guide", "SRE doc", or "运维手册".
71
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The canonical home for this skill is eng-runbook in nexu-io/open-design
Engineering Runbook Skill
Produce a single-page engineering runbook.
Workflow
- Read DESIGN.md.
- Identify the service from the brief.
- Layout:
- Header: service name, owner team, severity tier, version.
- Service summary paragraph + dependency list.
- Alerts table: alert name / severity / what it means / first response.
- Dashboards & links list.
- Common procedures block (3–4) with code blocks (deploy, rollback, rotate keys).
- On-call rotation table (week / primary / secondary / backup).
- Incident response checklist (5 numbered steps).
- One inline
<style>, semantic HTML, monospace for code blocks.
Output contract
<artifact identifier="runbook-name" type="text/html" title="Service Runbook">
<!doctype html>...</artifact>- Repository
nexu-io/open-design
- Revision
78d5637
- Last updated
- First committed
Canonical home
since Oct 4, 2026
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.