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
- stephenrogan/csm-skillstheir own version, first seen Mar 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- stephenrogan/csm-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository77 other files it gives its agents.
- AGENTS.mdAGENTS.md
- abm-account-planSkill
- account-research-briefSkill
- account-tieringSkill
- aeo-answer-optimizerSkill
- breakup-emailSkill
- buyer-persona-builderSkill
- buying-committee-mapperSkill
- buying-signal-scoringSkill
- call-coaching-scorecardSkill
- campaign-performance-analyzerSkill
- case-study-writerSkill
- churn-win-backSkill
- closed-lost-reactivationSkill
- cold-call-scriptSkill
- cold-email-sequenceSkill
- cold-email-writerSkill
- comparison-page-writerSkill
- competitive-battlecardSkill
- competitor-teardownSkill
- crm-hygiene-auditSkill
- customer-interview-guideSkill
- deal-qualificationSkill
- deliverability-auditSkill
- discovery-call-prepSkill
- domain-warmup-planSkill
- email-authentication-setupSkill
- email-copy-reviewSkill
- event-follow-upSkill
- expansion-opportunity-finderSkill
- first-line-personalizationSkill
- funding-signal-outreachSkill
- gtm-global-rulesSkill
- hiring-signal-outreachSkill
- icp-builderSkill
- job-change-playsSkill
- lead-list-builderSkill
- lead-magnet-builderSkill
- lead-scoring-modelSkill
- linkedin-comment-strategySkill
- linkedin-connection-noteSkill
- linkedin-message-sequenceSkill
- linkedin-post-writerSkill
- linkedin-profile-optimizerSkill
- list-cleaningSkill
- lookalike-account-finderSkill
- meeting-booking-replySkill
- messaging-matrixSkill
- multichannel-cadenceSkill
- mutual-action-planSkill
- negotiation-playbookSkill
- no-show-recoverySkill
- objection-handlerSkill
- outbound-ab-testSkill
- outbound-mathSkill
- outreach-compliance-checkSkill
- pipeline-reviewSkill
- post-engagement-outreachSkill
- proposal-follow-upSkill
- prospect-research-briefSkill
- The first 60 shown.
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
- Distinctive: line 16
Use this whenever the next email is a follow-up.
- Distinctive: line 36
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.
- Distinctive: line 64
MUST add one new piece of value or one clear, easy question.
- Distinctive: line 65
MUST reference the actual previous conversation accurately.
- Distinctive: line 66
NEVER guilt-trip ("I've tried to reach you several times").
- Distinctive: line 67
NEVER fake urgency or deadlines that do not exist.
≈ “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.
Files
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
| Situation | Likely reason for silence | Follow-up type |
| Cold, no reply | Not relevant enough, or bad timing | New angle or value add |
| After a first meeting | Busy; next step was vague | Recap with a clear next step |
| After a demo or proposal | Internal discussion, competing priorities, objection not voiced | Decision nudge with an easy answer |
| Quiet for 3+ weeks mid-deal | Priority dropped or a blocker appeared | Honest re-engage, permission to close |
| After an event or call | Momentum fading | Deliver 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."
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
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.

