agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/follow-up-email-writer/SKILL.md

follow-up-email-writer

Skill13 starsChanged 25 days agoMITView on GitHub

Use this skill when you need to follow up after no reply, after a meeting, after a proposal or after a prospect went quiet: \"write a follow-up email\", \"they ghosted me\", \"follow up after the demo\". Diagnoses the situation, picks the right follow-up type (add value, new angle, recap, nudge on a decision, re-engage), and writes a short follow-up that gives the reader a reason to respond without guilt-tripping or saying \"just checking in\".

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 whenever the next email is a follow-up.

    line 16
  2. Distinctive:

    Every follow-up carries one new thing: an insight, a short customer story, an answer to a question they had, a resource, a relevant change.

    line 36
  3. Distinctive:

    MUST add one new piece of value or one clear, easy question.

    line 64
  4. Distinctive:

    MUST reference the actual previous conversation accurately.

    line 65
  5. Distinctive:

    NEVER guilt-trip ("I've tried to reach you several times").

    line 66
  6. Distinctive:

    NEVER fake urgency or deadlines that do not exist.

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 whenever the next email is a follow-up. It produces a follow-up that adds something new, because "just checking in" gives the reader nothing to respond to.

Inputs

  • The thread so far, or the meeting notes.
  • Stage: cold (no reply yet), post-meeting, post-proposal, gone quiet mid-deal.
  • How long it has been and any known deadlines.

The play

1. Diagnose

SituationLikely reason for silenceFollow-up type
Cold, no replyNot relevant enough, or bad timingNew angle or value add
After a first meetingBusy; next step was vagueRecap with a clear next step
After a demo or proposalInternal discussion, competing priorities, objection not voicedDecision nudge with an easy answer
Quiet for 3+ weeks mid-dealPriority dropped or a blocker appearedHonest re-engage, permission to close
After an event or callMomentum fadingDeliver what was promised

2. Add something

Every follow-up carries one new thing: an insight, a short customer story, an answer to a question they had, a resource, a relevant change. If there is nothing new, the follow-up should be a short, honest question instead.

3. Make replying easy

End with a question that can be answered in one line or one word. Multiple-choice questions work well mid-deal: "Is this (a) still a priority, (b) on hold until Q3, or (c) solved another way?"

4. Keep it short

Cold follow-ups: 25-70 words. Post-meeting recaps: as long as the next steps need, in bullets.

Examples

Post-meeting recap

Hi Tom, thanks for the time today. What I heard: close takes 9 days, approvals are the bottleneck, and you want options before the budget review on the 14th.

Next steps: I send the Contoso checklist today; you loop in Priya; we meet Thursday at 10 to review it together. Does that still work?

Gone quiet mid-deal

Hi Tom, it has been a few weeks since the proposal, so I suspect priorities have shifted. Is it (a) still on for this quarter, (b) paused until later, or (c) solved another way? Any answer helps me stop guessing.

What good looks like

  • The reader learns something or gets something in every follow-up.
  • Post-meeting emails go out the same day.
  • The common mistake is "just bumping this", "circling back" or "did you get a chance to look", which signal you have nothing to add.

Rules

  • MUST add one new piece of value or one clear, easy question.
  • MUST reference the actual previous conversation accurately.
  • NEVER guilt-trip ("I've tried to reach you several times").
  • NEVER fake urgency or deadlines that do not exist.

Example prompts

  • "They went quiet after the proposal two weeks ago. Write the follow-up."
  • "Write a recap email after today's discovery call. Notes below."
  • "Follow up on my cold email from last week with a new angle."

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.