agentleFS
nawazxznawazxz/20-claude-skills-for-business/follow-up-email/SKILL.md

follow-up-email

Skill0 starsChanged 3 months agoMITView on GitHub

Write a sales follow-up email or a short nudge sequence. Use when a deal has gone quiet, after a call or demo, or when someone needs to chase a proposal without sounding pushy.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Write follow-ups that give the other person an easy reason to reply.

    line 8
  2. Distinctive:

    Add one piece of new value: a resource, an idea, a relevant result, or a clear question.

    line 17
  3. Distinctive:

    Keep it to 3-5 sentences.

    line 19
  4. Distinctive:

    If a sequence is asked for, space touches with different angles: value, social proof, a soft break-up.

    line 20
  5. Distinctive:

    Never guilt-trip ("I've reached out several times").

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Follow-Up Email

Write follow-ups that give the other person an easy reason to reply.

Inputs needed

  • Where things stand: last contact, what was discussed, what you're waiting on.
  • The recipient's name and (optional) company.
  • (Optional) How many touches you want in the sequence.

Steps

  1. Anchor to the last real interaction so it doesn't read as a cold nudge.
  2. Add one piece of new value: a resource, an idea, a relevant result, or a clear question.
  3. Make the ask small and specific (a yes/no, a time, a one-word reply).
  4. Keep it to 3-5 sentences.
  5. If a sequence is asked for, space touches with different angles: value, social proof, a soft break-up.

Output format

For a single email: subject line + body. For a sequence: each touch labeled with when to send (e.g. Day 3, Day 7), subject, and body.

Voice & rules

  • Never guilt-trip ("I've reached out several times").
  • One ask per email.
  • The break-up email should be warm, not passive-aggressive.

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.