New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vendor Breakup Email

by mohitagw15856 in mohitagw15856/pm-claude-skills

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…

MITAuto-check passed

Install Vendor Breakup Email

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill vendor-breakup-email -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills vendor-breakup-email --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vendor-breakup-email .claude/skills/vendor-breakup-email && rm -rf skills-src

Use ~/.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/

Facts

Skill name
vendor-breakup-email
GitHub stars
1.4k
Token cost
~1.4k tokens
SKILL.md length
701 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 5 steps: The calendar outranks the prose: find… → True but spare: "We're consolidating… → Transition asks go in the first email:… → …
  • Asked write a cancellation email to our vendor
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Clean-Exit Rules and Output Format, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vendor Breakup Email is an agent skill from mohitagw15856/pm-claude-skills. 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…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

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 write a cancellation email to our vendor
  • Were not renewing how do I tell them
  • End this contractor relationship professionally
  • Switch providers without drama

Example prompts

  • “/vendor-breakup-email”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. The calendar outranks the prose: find the auto-renewal date and notice window first — a perfect email sent one day late costs a full term…
  2. True but spare: "We're consolidating tools" / "our needs have shifted" — one honest sentence, no itemized grievances. A feedback list…
  3. Transition asks go in the first email: data export (format named — "CSV export of all records, not a PDF report"), handover of any…
  4. Pre-decide the retention counter: vendors counter — often meaningfully. If a number would change the answer, name it internally before…
  5. The door stays ajar for free: "We'd gladly consider [vendor] again as needs evolve" costs nothing and is often true. Vendors remember…

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

Vendor Breakup Email loads about 1.4k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 701 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~137
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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). 701 words, ~1,367 tokens.

Download SKILL.mdSave it as .claude/skills/vendor-breakup-email/SKILL.md (or your agent's skills folder).
name
vendor-breakup-email
description
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.

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 deadline is a year-long postscript (route the document through tos-decoder-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

Framework: The Clean-Exit Rules

  1. The calendar outranks the prose: find the auto-renewal date and notice window first — a perfect email sent one day late costs a full term. The send date is the notice deadline minus buffer, and the email cites the clause ("per section 8, this is our notice of non-renewal effective [date]").
  2. True but spare: "We're consolidating tools" / "our needs have shifted" — one honest sentence, no itemized grievances. A feedback list invites rebuttal and negotiation; if they ask for detail, a short call after the notice is filed is the generous version.
  3. Transition asks go in the first email: data export (format named — "CSV export of all records, not a PDF report"), handover of any credentials/ownerships, the final-invoice expectation ("services through [date], no charges after"). Asks made while notice is fresh get serviced; asks made post-offboarding get queued behind current customers.
  4. Pre-decide the retention counter: vendors counter — often meaningfully. If a number would change the answer, name it internally before sending (and consider just asking for it instead of leaving). If nothing changes the answer, the response is drafted now: "appreciated, but the decision is final."
  5. The door stays ajar for free: "We'd gladly consider [vendor] again as needs evolve" costs nothing and is often true. Vendors remember exits; the graceful ones get priority when you're back — and reference calls about you happen in this industry too.
Show full SKILL.md (226 more words)Show less

Output Format

Vendor Exit: [vendor] — notice deadline: [date]

The Contract Check

[Clause cited · notice period · renewal date · send-by date]

The Email

[Notice with clause + effective date · the spare reason · transition asks itemized (data format, credentials, invoice bound) · the door-open close]

Retention Response (pre-decided)

[The number that changes the answer, or "none — final"; the reply draft either way]

Offboarding Checklist

[Export verified before access ends · credentials rotated · billing/card removed · internal cutover date · the calendar note for contract archive]

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
  • No grievance list — the reason is one true sentence

Anti-Patterns

  • 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

Example Trigger Phrases

  • "Write a cancellation email to our vendor."
  • "We're not renewing how do I tell them."
  • "End this contractor relationship professionally."
  • "Switch providers without drama."

© 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/vendor-breakup-email of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Vendor Breakup 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.

Vendor Breakup Email compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vendor Breakup Email this skillmohitagw15856/pm-claude-skills1.4k—~1.4kAutomated safety check: PassMIT
Emailasgeirtj/system_prompts_leaks69k—~3.5kAutomated safety check: PassCC0-1.0
Emailscoreyhaines31/marketingskills54k1 repos~2.8kAutomated safety check: PassMIT
Mailtrap Email Integrationaffaan-m/ECC277k1 repos~955Automated safety check: PassMIT
Email Marketing Biblesickn33/agentic-awesome-skills47k—~8.7kAutomated safety check: PassMIT
Email Systemsdavila7/claude-code-templates33k2 repos~548Automated safety check: PassMIT

Similar skills

  • Email

    asgeirtj/system_prompts_leaks

    Read or triage email, clean up an inbox, draft or send messages, and check delivery.

    69k GitHub stars~3.5k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

  • Emails

    coreyhaines31/marketingskills

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    54k GitHub starsUsed in 1 repo~2.8k tokens
    Marketing & SEOAuto-check passed

  • Mailtrap Email Integration

    affaan-m/ECC

    Guides agents through integrating transactional email sending via Mailtrap's Email API, including sandbox testing, domain verification, and API authentication.

    277k GitHub starsUsed in 1 repo~955 tokens
    Backend & APIsAuto-check passed

  • Email Marketing Bible

    sickn33/agentic-awesome-skills

    Data-backed email marketing for AI agents: automation flows, deliverability triage, copy de-slopping, AI email design, ESP control via MCP with send gates and compliance.

    47k GitHub stars~8.7k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

  • Email Systems

    davila7/claude-code-templates

    Email has the highest ROI of any marketing channel. An agent skill from davila7/claude-code-templates.

    33k GitHub starsUsed in 2 repos~548 tokens
    Backend & APIsAuto-check passed

  • Vendor Management

    alirezarezvani/claude-skills

    A skill your agent uses when reviewing, scoring, or auditing third-party SaaS / vendor relationships — running a vendor scorecard with industry tuning, tracking SLA compliance with credit-claim…

    28k GitHub stars~2.8k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo

  • Car 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…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed

  • 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.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • 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.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • 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.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Vendor Breakup Email

What does Vendor Breakup Email 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…. Vendor Breakup Email is an agent skill from mohitagw15856/pm-claude-skills. 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.

When should I use Vendor Breakup Email?

Vendor Breakup Email fits situations like: asked write a cancellation email to our vendor; were not renewing how do I tell them; end this contractor relationship professionally; switch providers without drama.

How do I install Vendor Breakup Email in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill vendor-breakup-email -a claude-code`. Or copy the skill folder (skills/vendor-breakup-email in mohitagw15856/pm-claude-skills) into .claude/skills/vendor-breakup-email in your project. Claude Code loads it when a task matches its description.

How do I install Vendor Breakup Email in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill vendor-breakup-email -a codex`. Or copy the skill folder (skills/vendor-breakup-email in mohitagw15856/pm-claude-skills) into .agents/skills/vendor-breakup-email in your project. Codex loads it when a task matches its description.

Can I use Vendor Breakup 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 vendor-breakup-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/vendor-breakup-email, .gemini/skills/vendor-breakup-email, .github/skills/vendor-breakup-email and .opencode/skills/vendor-breakup-email in your project.

What does Vendor Breakup Email need to run?

SKILL.md names no scripts, command-line tools or credentials: Vendor Breakup Email is instructions for the agent only.

Does Vendor Breakup 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 Vendor Breakup 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 Vendor Breakup Email use?

Vendor Breakup 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 Vendor Breakup Email use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Vendor Breakup Email?

Skills that share tags, products or a category with Vendor Breakup Email: Email (asgeirtj/system_prompts_leaks, 69k stars), Emails (coreyhaines31/marketingskills, 54k stars), Mailtrap Email Integration (affaan-m/ECC, 277k stars) and Email Marketing Bible (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vendor Breakup 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.