agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/breakup-email/SKILL.md

breakup-email

Skill13 starsChanged 22 days agoMITView on GitHub

Use this skill when you want to close the loop with a prospect who has not replied after several touches, or a deal that went silent: \"write a breakup email\", \"last email in the sequence\", \"close the loop politely\". Writes a short, gracious final email that gives an easy out, invites a one-word reply, leaves the door open for later and often gets more replies than any earlier step. Includes versions for cold sequences, stalled deals and lost champions.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this for the last touch.

    line 16
  2. Distinctive:

    Leave something useful or a reason to come back later.

    line 36
  3. Distinctive:

    After the break-up, contacts move to a nurture: no sales email for 90 days unless they reply or a strong new signal fires.

    line 42
  4. Distinctive:

    No guilt, no passive aggression, no "I guess you're not interested".

    line 60
  5. Distinctive:

    MUST make it clear this is the last email in the sequence.

    line 66
  6. Distinctive:

    MUST stop all sequence emails afterwards unless they reply.

    line 67
  7. Distinctive:

    NEVER use sarcasm, guilt or fake scarcity.

    line 68
  8. Distinctive:

    NEVER claim you are "closing their file" in a way that sounds like a threat.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this for the last touch. A good break-up email respects the reader's silence, removes pressure and makes a one-line answer easy, which is why it often pulls the highest reply rate of the sequence.

Inputs

  • The thread so far.
  • Stage: cold sequence, stalled deal, or a relationship you want to keep.
  • What you would send if they said yes later (a checklist, a story, a short demo).

The play

1. Choose the version

VersionUse whenTone
Cold closeNo reply after 3-4 cold touchesLight, brief, easy out
Deal closeEngaged prospect went silent for 3+ weeksHonest, direct, helpful
Door openGood fit, wrong timeWarm, with a future trigger

2. Keep the structure tight

  1. Say this is the last note (without drama).
  2. Offer one easy reply: a single word, or a multiple-choice.
  3. Leave something useful or a reason to come back later.
  4. Wish them well, sincerely.

25-50 words for cold; up to 80 for deals.

3. Set the next step

After the break-up, contacts move to a nurture: no sales email for 90 days unless they reply or a strong new signal fires.

Examples

Cold close

Hi Maya, I will stop here so I don't clutter your inbox. If faster month-end closes become a priority, reply "close" and I will send the checklist Contoso used. Good luck with quarter end.

Deal close

Hi Tom, I have not heard back since the proposal, so I am going to assume this has moved down the list and close it on my side. If that is wrong, a one-line reply is all it takes to pick up where we left off. Either way, thank you for the time your team gave us.

Door open

Hi Ana, sounds like timing is the issue rather than fit. I will check back in Q3 when you mentioned the budget cycle starts. In the meantime, here is the rollout plan other 10-location groups used, in case it is useful.

What good looks like

  • No guilt, no passive aggression, no "I guess you're not interested".
  • A real one-word reply option.
  • The common mistake is the sarcastic break-up ("Have you been eaten by a bear?"). It sometimes gets replies but costs goodwill with exactly the people you want to sell to later.

Rules

  • MUST make it clear this is the last email in the sequence.
  • MUST stop all sequence emails afterwards unless they reply.
  • NEVER use sarcasm, guilt or fake scarcity.
  • NEVER claim you are "closing their file" in a way that sounds like a threat.

Example prompts

  • "Write the final email for our 4-step cold sequence to CFOs."
  • "This deal went quiet for a month after the demo. Write a break-up email."
  • "Write a door-open email for a prospect who said maybe next year."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free