Agent skill · Code Review & Quality

resignation-letter

Write a resignation letter that closes a chapter without burning it — short, warm, legally clean, and silent on everything that doesn't belong in a permanent file. Use when asked write my resignation letter, how do I resign professionally, what do I say when I quit, or review my resignation email. Produces the letter itself, the tell-your-manager-first script, the timing plan, and the list of things that must NOT go in writing.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill resignation-letter --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/resignation-letter/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Resignation Letter Skill A resignation letter has exactly one job: create a clean, dated record that you resigned, effective when. It is not the place for grievances, gratitude essays, or explanations — it goes in a permanent file, may be read by lawyers, and will outlive every feeling in it. This skill writes the three-sentence version that professionals use, plus the parts that actually matter and happen *around* the letter: the conversation before it, the timing, and the discipline about what stays verbal. ## What This Skill Produces - **The letter** — 3–5 sentences: resignation, effective date, transition willingness, one line of thanks; nothing else - **The manager conversation script** — the letter is never how your manager finds out; the 5-minute verbal comes first - **The timing plan** — notice period, when to tell whom in what order, and what to have done *before* the conversation - **The not-in-writing list** — everything the person is tempted to include, with where each item actually belongs ## Required Inputs Ask for these if not provided: - **The basics** — role, manager, intended last day, contractual/customary notice period - **The reason and the temperature** — le

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Clean-Exit Rules
  4. Output Format
  5. The Letter
  6. The Conversation (before the letter)
  7. Timing Plan
  8. Not In Writing
  9. Quality Checks
  10. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the resignation-letter skill do?

Write a resignation letter that closes a chapter without burning it — short, warm, legally clean, and silent on everything that doesn't belong in a permanent file. Use when asked write my resignation letter, how do I resign professionally, what do I say when I quit, or review my resignation email. Produces the letter itself, the tell-your-manager-first script, the timing plan, and the list of things that must NOT go in writing.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill resignation-letter --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.

Keep going