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 "运维手册".
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Eng Runbook when an AI agent needs a reusable SKILL.md workflow for this job: 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 "运维手册".
When not to use it
Skip Eng Runbook when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/eng-runbook # Save SKILL.md to ~/.claude/skills/eng-runbook/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/eng-runbook/SKILL.md. For a shared project, commit the folder at .claude/skills/eng-runbook/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Eng Runbook skill for this task: Read DESIGN.md. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
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
``` <artifact identifier="runbook-name" type="text/html" title="Service Runbook"> <!doctype html>...</artifact> ```
Intended uses
- 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.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.