Engineering Runbook Skill
SkillMonitoring & opseng-runbook is a skill that guides an AI agent to build a one-page engineering runbook for a named service. It produces a single-page HTML document covering alerts, dashboards, common procedures, on-call rotation, and incident steps, so the team has one place to look during operations.
Available today. Use it from your connected AI after setup.
No other account needed.
Have a brief that names the service and mentions a runbook, ops doc, on-call guide, SRE doc, or 运维手册.
Then ask your AI: use the Engineering Runbook Skill skill
What your AI can do with it
- Builds a header with service name, owner team, severity tier, and version
- Creates an alerts table with alert name, severity, meaning, and first response
- Lists dashboards and links for the service
- Writes 3-4 copy-pasteable procedures such as deploy, rollback, and key rotation
- Formats an on-call rotation table with week, primary, secondary, and backup
- Produces a five-step incident response checklist
Getting started
- Have a brief that names the service and mentions a runbook, ops doc, on-call guide, SRE doc, or 运维手册.
- Have a DESIGN.md available, since the skill reads it before building the page.
- Ask the agent to write the runbook, for example: write a runbook for the auth service with alerts, dashboards, common procedures, and on-call rotation.
- Review the generated single-page HTML artifact and fill in service-specific details.
What this skill tells your AI
The instructions your AI receives, as published by nexu-io/open-design in design-templates/eng-runbook/SKILL.md and read by ahel’s review.
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>
Signals
- GitHub stars
- 98k
- Forks
- 11k
- Last commit
- Sep 2026
Others that do the same job
Questions
- What does the runbook include?
- A header with ownership details, a service summary with dependencies, an alerts table, dashboard links, three or four procedures with code blocks, an on-call rotation table, and a five-step incident checklist.
- What format is the output?
- A single-page HTML artifact with semantic markup, one inline style block, and monospace code blocks, titled Service Runbook.
- When should the skill be used?
- When the brief mentions runbook, ops doc, on-call guide, SRE doc, service runbook, or 运维手册.
Advanced
- Item type
- skill
- Key
eng-runbook-2- Source
- github.com/nexu-io/open-design