escalation-email
Escalate an issue up the chain without burning the person you're escalating past — the facts-first structure, the tried-already section that earns the escalation, and the specific ask that makes action easy. Use when asked I need to escalate this, write an email to my boss's boss, this vendor issue needs to go up, or how do I go over someone's head professionally. Produces the escalation email with its evidence spine, the pre-escalation courtesy step, and the relationship-preserving framing.
npx skills add mohitagw15856/pm-claude-skills --skill escalation-email --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.
# Escalation Email Skill Escalations fail in both directions: too soft (a vent that asks for nothing, filed as noise) or too hot (an ambush that makes an enemy at the layer you skipped). The working escalation is a *case*: what's stuck, what was already tried (this section earns the right to escalate), what it costs while stuck, and the one specific thing the recipient can do. And it's rarely a surprise attack — the person being escalated past usually gets told first, which converts most escalations into resolutions before they're even sent. ## What This Skill Produces - **The escalation email** — facts-first, tried-already documented, cost stated, one specific ask - **The courtesy step** — the heads-up to the person being escalated past, drafted (and the cases where it's skipped) - **The evidence spine** — dates, attempts, responses, quoted where load-bearing - **The de-escalation branch** — because the heads-up often resolves it, and that's the best outcome ## Required Inputs Ask for these if not provided: - **The stuck thing** — what's blocked, since when, what it's costing (time, money, a customer) — costs make escalations move - **The attempts log** — what was tried, when, wha
- What This Skill Produces
- Required Inputs
- Framework: The Case Rules
- Output Format
- The Courtesy Step (usually first)
- The Email
- Evidence Spine
- Quality Checks
- Anti-Patterns
What does the escalation-email skill do?
Escalate an issue up the chain without burning the person you're escalating past — the facts-first structure, the tried-already section that earns the escalation, and the specific ask that makes action easy. Use when asked I need to escalate this, write an email to my boss's boss, this vendor issue needs to go up, or how do I go over someone's head professionally. Produces the escalation email with its evidence spine, the pre-escalation courtesy step, and the relationship-preserving framing.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill escalation-email --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.