Engineering Runbook Skill

What your AI can do with it

• Builds a single-page HTML runbook for a named service
• Creates a header with ownership details for the service
• Adds an alerts table with first responses for each alert
• Includes dashboard links for the service
• Writes three or four copy-pasteable procedures such as deploy and rollback
• Adds an on-call schedule and a five-step incident checklist

Getting started

1. Have an agent that supports loading skills.
2. Add the eng-runbook skill to the agent's available skills.
3. Ask the agent to build a runbook, mentioning "runbook", "ops doc", "on-call guide", "SRE doc", or "运维手册".
4. Provide the service name and any ownership, alert, dashboard, and on-call details the agent should include.
5. Review the generated single-page HTML runbook and adjust as needed.

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.

<artifact identifier="runbook-name" type="text/html" title="Service Runbook">
<!doctype html>...</artifact>

Signals

GitHub stars

99k

Forks

11k

Last commit

Oct 2026

Others that do the same job

Questions

What does the runbook include?

A header with ownership details, an alerts table with first responses, dashboard links, three or four copy-pasteable procedures like deploy and rollback, an on-call schedule, and a five-step incident checklist.

What format is the output?

A single-page HTML document covering the service.

When should the skill be used?

When the brief mentions "runbook", "ops doc", "on-call guide", "SRE doc", or "运维手册".

How many procedures does it include?

Three or four copy-pasteable procedures, such as deploy and rollback.