OR
On-Call Runbook
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Write an on-call runbook for a service — covering alert definitions, escalation paths, common incident responses, and on-call handoff procedures. Use when asked to write an on-call guide, create alert runbooks, document escalation procedures, or prepare an on-call handoff document. Produces a structured on-call runbook with per-alert response procedures, escalation matrix, diagnostic commands, and handoff template.
📚 Based on Google SRE on-call practice
What to give it
▸Service name — and what it does
▸Team — and tech lead name
▸Alert list — names of alerts that currently page on-call
▸Monitoring setup — Datadog / Grafana / CloudWatch / PagerDuty / etc.
▸Common failure modes — what breaks most often, and what fixes it
▸Escalation contacts — who to call when on-call can't resolve it
▸Deployment setup — can on-call roll back? How?
▸Service dependencies — what does this service depend on, and what depends on it?
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Every alert that pages on-call has a runbook entry — no alert is missing
✓Rollback command is accurate and tested recently
✓Escalation contacts have current phone numbers and Slack handles
✓Diagnostic commands work — they have been run by at least one person recently
✓Handoff template is used at every shift change — not just during incidents
✓"Things I had to figure out that weren't documented" are added to this runbook after every incident
⚠️ What it refuses to do
Do not write alert runbooks with vague diagnostic steps like "check the logs" — every step must specify the exact command, dashboard link, or query to run
Do not include an alert in the runbook that has no specific on-call action — an alert that pages someone with no defined response path creates panic, not resolution
Do not leave the rollback command undocumented or untested — a rollback procedure that has never been run will fail when needed most
Do not list escalation contacts without phone numbers and Slack handles — email-only escalation paths are useless during a 3am incident
Do not write the runbook once and treat it as permanent — runbooks go stale after incidents; every incident must trigger a review of the relevant runbook entries
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="oncall-runbook"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
On-Call Runbook is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog