Agent skill · operations · nexu-io
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 "运维手册".
Why this skill is useful
Provides a structured template for creating engineering runbooks, including specific commands and procedures that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
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
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/eng-runbook