Engineering Runbook Skill
SkillMonitoring & opsLets your agent pull up an engineering runbook with service overviews, alerts, dashboards, on-call info, and incident steps.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Engineering Runbook Skill skill
About this capability
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 "运维手册".
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
- 95k
- Forks
- 11k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
eng-runbook-nexu-io- Source
- github.com/nexu-io/open-design