oncall-runbook
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.
npx skills add mohitagw15856/pm-claude-skills --skill oncall-runbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# On-Call Runbook Skill Produce a complete on-call runbook for a service — giving the on-call engineer everything they need to respond confidently to alerts at 3am, without having to ask anyone for help. A good on-call runbook reduces mean time to resolution (MTTR) by eliminating the "what do I do first?" problem. It is written for the on-call engineer who has just been paged and needs to act, not for someone calmly reading documentation. ## Required Inputs Ask for these if not already provided: - **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? ## Output Format --- # On-Call Runbook: [Service Name] **Team:** [Team name] | **Tech lead:** [Name] **PagerDuty service:** [Link] | **Escalation policy:** [Policy name] **Last updated:** [Date] | **Next review:**
- Required Inputs
- Output Format
- Quick Reference
- Escalation Matrix
- Service Architecture (Quick View)
- Alert Runbooks
- ALERT: [Alert Name 1 — e.g. HighErrorRate]
- ALERT: [Alert Name 2 — e.g. HighLatency]
- ALERT: [Alert Name 3 — e.g. DatabaseConnectionPoolExhausted]
- ALERT: [Alert Name 4 — e.g. QueueBacklogHigh / ConsumerLag]
- ALERT: [Add additional alerts following the same pattern]
- Diagnostic Cheat Sheet
- Useful Dashboard Links
- Incident Communication
Check current error rate Check which endpoints are erroring Any deploys in the last hour? Recent config changes? Is the database healthy? Is [downstream service] healthy? If caused by bad deploy — roll back: If caused by [specific issue]: If caused by upstream dependency: Check which endpoints are slow
What does the oncall-runbook skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill oncall-runbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.