vendor-breakup-email
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.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill vendor-breakup-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.
# Vendor Breakup Email Skill Ending a vendor relationship is a transaction wearing a relationship's clothes — and both halves need handling. The transaction: notice per the contract, data returned in usable formats, access revoked, final invoices bounded. The relationship: no grievance dump (you may need them again; the industry is small), a reason that's true but spare, and a close that leaves the door ajar. The email is short; the offboarding checklist behind it is where switching actually succeeds or fails. ## What This Skill Produces - **The contract check** — notice period, termination clause, auto-renewal deadline: the email's timing is set by these, not by mood - **The breakup email** — clean notice, effective date, the transition asks, the door-open close - **The retention-response plan** — the counter-offer is coming; decide now whether any price changes the answer - **The offboarding checklist** — data export (formats named), access revocation, final-invoice bounds, the internal switch plan ## Required Inputs Ask for these if not provided: - **The contract's exit terms** — notice period, renewal date, termination-for-convenience clause; an email sent after the auto-renew
- What This Skill Produces
- Required Inputs
- Framework: The Clean-Exit Rules
- Output Format
- The Contract Check
- The Email
- Retention Response (pre-decided)
- Offboarding Checklist
- Quality Checks
- Anti-Patterns
What does the vendor-breakup-email skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill vendor-breakup-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.