Menu

Individual skill

escalation-email

0upvotes

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.

plugins/pm-cowork/skills/escalation-email/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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:
Back to top