eng-runbook — Claude Code skill: what it does, how to install
eng-runbook generates a single-page HTML operations runbook with alerts, incident checklists, and terminal commands. Useful for on-call engineers and SRE teams.
Apache-2.0 231 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill eng-runbook -a claude-codeWhat eng-runbook does
This skill writes a standalone HTML runbook for any backend or platform service. The resulting document groups the team owner, severity tier, dependencies, and monitoring dashboards into a single view. It also formats an alerts table detailing severities and first-response instructions, alongside a five-step incident resolution checklist.
Common procedures feature terminal-ready snippets for actions like deploys, rollbacks, and key rotations. Monospace styling keeps shell commands legible.
The skill expects a DESIGN.md file in the project before generating markup. Without it, the layout will miss tokens for colors, typography, and spacing defined by the local design system.
What it helps with
- generate an on-call runbook for a production service
- document alert severities and immediate triage steps
- build a quick-reference page with deploy and rollback commands
- structure a five-step incident triage checklist
Example prompts for the agent
- Write a runbook for our auth service with alerts, dashboards, and rollback commands
- Draft an ops doc for the billing worker including an on-call rotation schedule
- Create an SRE doc with dependency mapping and key rotation steps
How to install eng-runbook
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill eng-runbook -a claude-code2Manually: put the files in place
~/.claude/skills/eng-runbook/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/eng-runbook/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill eng-runbook -a codex2Manually: put the files in place
.agents/skills/eng-runbook/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill eng-runbook -a cursor2Manually: put the files in place
.cursor/skills/eng-runbook/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/eng-runbook/SKILL.md2Manually: put the files in place
.github/skills/eng-runbook/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill eng-runbook -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/eng-runbookManually: put the files in place
.devin/skills/eng-runbook/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill eng-runbook -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about eng-runbook
How do I install eng-runbook in Claude Code?
Run npx skills add nexu-io/open-design --skill eng-runbook -a claude-code. The skill definition will be saved to ~/.claude/skills/eng-runbook/SKILL.md.
What output format does eng-runbook produce?
It outputs a semantic HTML file inside an artifact block, styled with an inline <style> block and monospace code snippets.
What prerequisites does the runbook skill require?
The skill workflow requires a DESIGN.md file in the workspace to supply styling specifications for colors, typography, and layout.
Source text
SKILL.md · Apache-2.0
---
name: eng-runbook
description: |
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 "运维手册".
triggers:
- "runbook"
- "ops doc"
- "on-call"
- "sre doc"
- "service runbook"
- "运维手册"
od:
mode: prototype
platform: desktop
scenario: engineering
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
example_prompt: "Write a runbook for our auth service — alerts, dashboards, common procedures, on-call rotation."
---
# Engineering Runbook Skill
Produce a single-page engineering runbook.
## Workflow
1. Read DESIGN.md.
2. Identify the service from the brief.
3. 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).
4. One inline `<style>`, semantic HTML, monospace for code blocks.
## Output contract
```
<artifact identifier="runbook-name" type="text/html" title="Service Runbook">
<!doctype html>...</artifact>
```
© nexu-io · Apache-2.0 · nexu-io/open-design