support-runbook
Write a support runbook for handling a recurring issue type consistently. Use when asked to write a support runbook, a troubleshooting playbook for agents, a handling guide for a common issue, or a tier-1 response procedure. Produces a runbook — issue identification, triage/severity, step-by-step diagnosis & resolution, decision tree, when/how to escalate, and the customer-comms templates — so any agent resolves it the same way.
npx skills add mohitagw15856/pm-claude-skills --skill support-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.
# Support Runbook Skill When the same issue hits support repeatedly, every agent shouldn't reinvent the fix. A support runbook makes the resolution consistent and fast: how to recognise it, how urgent it is, the diagnostic steps, the decision tree, and exactly when to escalate (with what info). This skill writes that — turning tribal knowledge into a procedure tier-1 can follow. ## Required Inputs Ask for these only if they aren't already provided: - **The issue type** — the recurring problem this runbook covers (e.g. "sync failures," "login loops," "billing discrepancy"). - **How to recognise it** — symptoms and how it's reported. - **The resolution path(s)** — diagnostic steps and fixes (including the branches — "if X then…"). - **Escalation** — when it exceeds tier-1, who it goes to, and with what diagnostics. ## Output Format ### Support Runbook: [issue type] **1. Identify** — the symptoms and how customers describe it (so agents recognise it from a vague ticket). What it's often confused with. **2. Severity / triage** — how to rate urgency (is it down vs. degraded vs. cosmetic? affecting one user or many?) and the response-time expectation per level. **3. Diagnose** — ordered
- Required Inputs
- Output Format
- Support Runbook: [issue type]
- Quality Checks
- Anti-Patterns
- Based On
What does the support-runbook skill do?
Write a support runbook for handling a recurring issue type consistently. Use when asked to write a support runbook, a troubleshooting playbook for agents, a handling guide for a common issue, or a tier-1 response procedure. Produces a runbook — issue identification, triage/severity, step-by-step diagnosis & resolution, decision tree, when/how to escalate, and the customer-comms templates — so any agent resolves it the same way.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill support-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.