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 "运维手册".
Profile →npx skills add nexu-io/open-design --skill eng-runbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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> ```
- Workflow
- Output contract
What does the eng-runbook skill do?
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 "运维手册".
How do I install it?
Run `npx skills add nexu-io/open-design --skill eng-runbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.