What do I need to use Vendor Breakup Email?

The contract's exit terms; The real reason and the stated reason; What you need back; The retention answer.

Is Vendor Breakup Email free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Vendor Breakup Email

Q: How do I know the Vendor Breakup Email output is good?

The skill verifies itself against its own quality checks: The send date beats the notice deadline with buffer; The clause is cited — notice that doesn't reference the contract invites disputes; Data comes back in named, usable formats, verified before access ends; The retention answer was decided before sending.

🔵 Stable🕐 updated 2026-07-19 🔷 SkillSpec L3 pm-cowork

End a vendor, freelancer, or service relationship cleanly — the notice email that cites the contract, the transition asks that protect your data and continuity, and the door-open close that costs nothing. Use when asked write a cancellation email to our vendor, we're not renewing how do I tell them, end this contractor relationship professionally, or switch providers without drama. Produces the notice-period check, the breakup email with transition terms, the retention-offer response plan, and the offboarding checklist.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸The contract's exit terms — notice period, renewal date, termination-for-convenience clause; an email sent after the auto-renew deadline is a year-long postscript (route the document through [tos-decoder](../tos-decoder/SKILL.md)-style reading if unclear)

▸The real reason and the stated reason — price, fit, quality, politics; the email states a true-but-spare version, and the skill helps pick it

▸What you need back — data, files, configurations, domain/account ownerships — named per item, with formats

▸The retention answer — if they counter at 40% off, does the answer change? Decided before the email, not during the call

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓The send date beats the notice deadline with buffer

✓The clause is cited — notice that doesn't reference the contract invites disputes

✓Data comes back in named, usable formats, verified before access ends

✓The retention answer was decided before sending

✓No grievance list — the reason is one true sentence

⚠️ What it refuses to do

Do not miss the auto-renew window while polishing the wording — the calendar is the whole game

Do not itemize grievances — feedback invites negotiation; exit emails state decisions

Do not revoke your own access before the export is verified — sequence is data, then keys

Do not negotiate live on the retention call unprepared — the pre-decided number is the armor

Do not burn the door — spare exits are free options on the future

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="vendor-breakup-email"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Vendor Breakup Email is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog