{"id":"d3807af6-8e3c-496b-b485-0ddd9a3abca8","shortId":"N2zADY","kind":"skill","title":"eng-runbook","tagline":"An engineering runbook — service overview, alerts table, dashboards\nlinks, common procedures with copy-pasteable commands, on-call rotation,\nand an incident-response checklist. Use when the brief mentions\n\"runbook\", \"ops doc\", \"on-call guide\", \"SRE doc\", or \"运维手册\".","description":"# Engineering Runbook Skill\n\nProduce a single-page engineering runbook.\n\n## Workflow\n\n1. Read DESIGN.md.\n2. Identify the service from the brief.\n3. Layout:\n - Header: service name, owner team, severity tier, version.\n - Service summary paragraph + dependency list.\n - Alerts table: alert name / severity / what it means / first response.\n - Dashboards & links list.\n - Common procedures block (3–4) with code blocks (deploy, rollback, rotate keys).\n - On-call rotation table (week / primary / secondary / backup).\n - Incident response checklist (5 numbered steps).\n4. One inline `