eng-runbook
The eng-runbook skill generates a single-page HTML engineering runbook by extracting service details from a DESIGN.md file and organizing them into a structured document. It includes service metadata, dependency lists, alert tables, dashboard links, common operational procedures with code examples, on-call rotation schedules, and incident response checklists, suitable for on-call engineers needing quick operational reference material.
git clone --depth 1 https://github.com/nexu-io/open-design /tmp/eng-runbook && cp -r /tmp/eng-runbook/design-templates/eng-runbook ~/.claude/skills/eng-runbookSKILL.md
# 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 ``` <artifact identifier="runbook-name" type="text/html" title="Service Runbook"> <!doctype html>...</artifact> ```
One-click contribution flow for Open Design (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.
|
|
|
Self-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.
|
|