End-of-Life Announcement Writer
getcrew44/crew44
Drafts a clear, empathetic end-of-life announcement for a product, feature or plan, covering rationale, customer impact, transition support, timeline and next steps.
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…
Install Escalation Email
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-email -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-email --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/escalation-email .claude/skills/escalation-email && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "escalation-email" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-email into .claude/skills/escalation-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-email", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-emailType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-email -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-email --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/escalation-email .agents/skills/escalation-email && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "escalation-email" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-email into .agents/skills/escalation-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-email", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-email -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-email --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/escalation-email .cursor/skills/escalation-email && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "escalation-email" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-email into .cursor/skills/escalation-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-email", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/escalation-email--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-email -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-email --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/escalation-email .gemini/skills/escalation-email && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "escalation-email" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-email into .gemini/skills/escalation-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-email", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills escalation-emailInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-email -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/escalation-email .github/skills/escalation-email && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "escalation-email" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-email into .github/skills/escalation-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-email", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill escalation-email -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills escalation-email --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/escalation-email .opencode/skills/escalation-email && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "escalation-email" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/escalation-email into .opencode/skills/escalation-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "escalation-email", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
escalation-email- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 663 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 5 steps: Facts first, temperature zero: dates and… → The tried-already section is the… → Cost converts sympathy to action:… → …
- Asked I need to escalate this
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Case Rules and Output Format, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Escalation Email is an agent skill from mohitagw15856/pm-claude-skills. 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.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Email writing. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked I need to escalate this
- Write an email to my bosss boss
- This vendor issue needs to go up
- How do I go over someones head professionally
Example prompts
- “s boss, this vendor issue needs to go up, or how do I go over someone”
- “/escalation-email”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Facts first, temperature zero: dates and events, no adjectives about people. "Requested on the 3rd, followed up on the 10th and 17th, no…
- The tried-already section is the license: two-to-three documented attempts through normal channels is what makes this an escalation…
- Cost converts sympathy to action: "blocked" is a status; "blocked, costing us the Q3 window / $X a week / the customer's renewal…
- The ask is one action, sized for the recipient: something they can do in their power in under a day. Multi-part asks and "thoughts?" both…
- The courtesy heads-up: "I'm going to raise this with [name] since we haven't been able to unblock it — wanted you to hear it from me"…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Escalation Email loads about 1.2k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 663 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 663 words, ~1,233 tokens.
Download SKILL.mdSave it as
.claude/skills/escalation-email/SKILL.md (or your agent's skills folder).- name
- escalation-email
- description
- 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.
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, what came back; an escalation without attempts is just skipping the line
- The players — who's being escalated to, who's being escalated past, and the relationship texture with each
- The ask — the specific action the recipient can take ("approve the exception," "reassign the ticket," "a 15-minute decision meeting") — never "please advise"
Framework: The Case Rules
- Facts first, temperature zero: dates and events, no adjectives about people. "Requested on the 3rd, followed up on the 10th and 17th, no response" indicts nobody and proves everything. The reader assigns the blame themselves — more durably than you could.
- The tried-already section is the license: two-to-three documented attempts through normal channels is what makes this an escalation instead of queue-jumping — and the section signals to the recipient that you escalate responsibly, which prices your future escalations.
- Cost converts sympathy to action: "blocked" is a status; "blocked, costing us the Q3 window / $X a week / the customer's renewal confidence" is a priority. One quantified cost line, honest, no inflation.
- The ask is one action, sized for the recipient: something they can do in their power in under a day. Multi-part asks and "thoughts?" both dissolve; "approve X" or "15 minutes to decide between A and B" both land.
- The courtesy heads-up: "I'm going to raise this with [name] since we haven't been able to unblock it — wanted you to hear it from me" — sent to the escalated-past person first in most cases. It's respectful, it prevents the ambush grudge, and ~half the time it resolves the issue on its own. Skip it only where the escalation is about that person's conduct (then it goes up quietly, and possibly to HR-shaped channels instead).
Show full SKILL.md (202 more words)Show less
Output Format
Escalation: [issue] → [recipient]
The Courtesy Step (usually first)
[The heads-up draft · or the documented reason it's being skipped]
The Email
[Subject: specific, not alarmed · Para 1: the situation + cost, two sentences · Para 2: the attempts, dated · Para 3: the one ask + timeline · warm close, zero blame-adjectives]
Evidence Spine
[The dated attempt log, quotes attached where they carry weight]
Quality Checks
- No adjectives about people — dates and events carry the case
- The attempts section shows 2+ real tries through normal channels
- The cost is quantified once, honestly
- The ask is one action within the recipient's power
- The escalated-past person hears it from you first (or the skip is justified explicitly)
Anti-Patterns
- Do not vent — an escalation that asks for nothing is filed as mood
- Do not ambush — the surprise escalation buys one win and a permanent enemy
- Do not inflate the cost — the first discovered inflation discounts all your future cases
- Do not escalate without attempts — that's queue-jumping wearing a process word
- Do not cc the world — the recipient plus the minimum necessary; audience size reads as aggression
Example Trigger Phrases
- "I need to escalate this."
- "Write an email to my boss's boss."
- "How do I go over someone's head professionally?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/escalation-email of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Escalation Email next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Escalation Email this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| End-of-Life Announcement Writergetcrew44/crew44 | 356 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Write Like Me Bootstrapjxnl/personal-monorepo-template | 563 | — | ~1.1k | Automated safety check: Pass | None | |
| Email Voice Profileyc-software/qm | 15k | — | ~856 | Automated safety check: Pass | MIT | |
| Compose Outreachw95/awesome-claude-corporate-skills | 244 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Email Opsaffaan-m/ECC | 277k | 1 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Write Like Me Bootstrap
jxnl/personal-monorepo-template
Bootstrap a durable "write like me" skill from the user's own Slack and email writing.
Email Voice Profile
yc-software/qm
Build (or refresh) a voice profile of how the user writes email, from their own sent Gmail.
Compose Outreach
w95/awesome-claude-corporate-skills
Generate personalized outreach messages using Common Room signals.
Email Ops
affaan-m/ECC
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.
Email Draft In Voice
yc-software/qm
Draft Gmail in the user's own voice from the voice profile built by email-voice-profile.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Escalation Email
What does Escalation Email 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…. Escalation Email is an agent skill from mohitagw15856/pm-claude-skills. 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.
When should I use Escalation Email?
Escalation Email fits situations like: asked I need to escalate this; write an email to my bosss boss; this vendor issue needs to go up; how do I go over someones head professionally.
How do I install Escalation Email in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill escalation-email -a claude-code`. Or copy the skill folder (skills/escalation-email in mohitagw15856/pm-claude-skills) into .claude/skills/escalation-email in your project. Claude Code loads it when a task matches its description.
How do I install Escalation Email in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill escalation-email -a codex`. Or copy the skill folder (skills/escalation-email in mohitagw15856/pm-claude-skills) into .agents/skills/escalation-email in your project. Codex loads it when a task matches its description.
Can I use Escalation Email in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill escalation-email -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/escalation-email, .gemini/skills/escalation-email, .github/skills/escalation-email and .opencode/skills/escalation-email in your project.
What does Escalation Email need to run?
SKILL.md names no scripts, command-line tools or credentials: Escalation Email is instructions for the agent only.
Does Escalation Email access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Escalation Email safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Escalation Email use?
Escalation Email is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Escalation Email use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Escalation Email?
Skills that share tags, products or a category with Escalation Email: End-of-Life Announcement Writer (getcrew44/crew44, 356 stars), Write Like Me Bootstrap (jxnl/personal-monorepo-template, 563 stars), Email Voice Profile (yc-software/qm, 15k stars) and Compose Outreach (w95/awesome-claude-corporate-skills, 244 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Escalation Email?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.