agentsclimarketplace

Follow up email writer

Skill stephenrogan/csm-skills/skills/follow-up-email-writer

Writes post-meeting follow-up emails that reinforce commitments, document decisions, and maintain momentum. Produces a customer-facing email that both parties can reference as the record of what was agreed. Use when asked to write a follow-up email, draft a post-meeting recap, summarise a call in an email, document next steps after a meeting, or when a CSM needs to send a professional recap after any customer interaction. Also triggers for questions about post-meeting communication, follow-up email drafting, commitment documentation, or meeting recap emails.From its SKILL.md

Install
npx -y skills add stephenrogan/csm-skills --skill follow-up-email-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.1 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it

Follow-Up Email Writer

Writes the post-meeting email that serves as the shared record of what happened and what was agreed. A good follow-up email is not just courteous -- it is an accountability tool that prevents the "I thought you said..." conversation 3 weeks later.

How to Use

Provide:

  • Meeting type (check-in, QBR, escalation review, kickoff, renewal, ad hoc)
  • Key discussion points (what was covered)
  • Decisions made (what was agreed)
  • Action items (what each side committed to, with deadlines)
  • Anything notable (sentiment shifts, new information, concerns raised)
  • Tone context (relationship depth, account health, formality level)

Follow-Up Structure

Every follow-up email has four sections:

1. Opening (1-2 sentences)

Thank them for the time. Reference one specific thing from the conversation that shows you were engaged, not running a template.

Bad: "Thank you for taking the time to meet today." Good: "Thanks for the conversation today, Tom. The insight about your team's Q2 expansion plans was really helpful in shaping how we can support you."

2. Summary (3-5 sentences)

What was discussed and decided. Not a transcript -- a curated summary of what matters.

Rule: Only include things the customer should see in writing. Internal observations, risk assessments, and political reads do not go in the follow-up.

3. Action Items (Table)

ActionOwnerDeadline
[action][name][date]

Rules:

  • Include items from both sides. The customer's commitments belong here alongside yours
  • Use specific dates, not "next week" or "soon"
  • Every item has a named owner -- not "us" or "the team"

4. Next Touchpoint (1 sentence)

When you will next be in contact and what that touchpoint will cover.

"I will follow up on [date] to check progress on the action items. Our next scheduled call is [date]."

Tone by Meeting Type

Meeting TypeToneLengthSpecial Considerations
Routine check-inWarm, brief50-80 words + action tableKeep it light. Do not over-document a casual conversation
QBRProfessional, thorough100-150 words + action tableThis is a formal record. Include key data points discussed and strategic agreements
Escalation reviewAccountable, specific80-120 words + action tableLead with the resolution update. Include what has been done and what remains
KickoffEnthusiastic but structured100-150 words + action tableRestate the goals, timeline, and responsibilities agreed in the kickoff
RenewalValue-forward, clear80-120 words + action tableReinforce value delivered. Document any commercial terms discussed
Difficult conversationEmpathetic, precise80-100 words + action tableAcknowledge the difficulty. Document exactly what was agreed to prevent misinterpretation

What Not to Include

ExcludeWhy
Risk assessmentsCustomer-facing email. Your internal read on account health is for internal notes, not the follow-up
Speculation"I think they might be looking at competitors" does not go in the follow-up
Vague action items"Follow up on the thing we discussed" is useless. Be specific or do not include it
Internal jargonHealth scores, NPS references, QBR acronyms (unless the customer uses these terms)
Multiple CTAsThe follow-up documents what happened. It is not a place for new asks. One CTA maximum (usually "let me know if I missed anything")

Output Format

Subject: [Account Name] -- [Meeting Type] Follow-Up: [Date]

Hi [name],

[Opening: 1-2 sentences acknowledging the conversation]

[Summary: 3-5 sentences covering key discussion points and decisions]

Action items from our conversation:

| Action | Owner | Deadline |
|--------|-------|----------|
| [action 1] | [owner] | [date] |
| [action 2] | [owner] | [date] |

[Next touchpoint: 1 sentence]

Let me know if I missed anything.

Best,
[your name]

Quality Gates

  • Is it sent within 4 hours of the meeting? Same-day follow-ups are professional. Next-day is acceptable. Anything later and the email feels like an afterthought
  • Does every action item have a named owner and specific date? If you cannot specify these, the item was not clearly committed in the meeting. Either clarify or note "to be confirmed"
  • Are customer action items included? The follow-up is bilateral. Including their commitments alongside yours signals partnership and accountability
  • Is it under 150 words (excluding the action table)? Follow-up emails that take 3 minutes to read do not get read
  • Would both sides agree with this as the record of what happened? If the customer would push back on the summary, revise

Principles

  • The follow-up email is the official record. What was said in the meeting is memory. What was written in the follow-up is documentation. If a disagreement arises later, the follow-up is what both sides reference
  • Speed signals professionalism. A follow-up sent within 2 hours of the meeting tells the customer you are organised, attentive, and take the relationship seriously
  • The action table is the most valuable part. Summaries are read once. Action tables are referenced repeatedly. Invest your effort in getting the actions right
  • Sending a follow-up after every meeting, every time, without exception, is a professional habit that compounds. Customers start to expect and rely on it. That reliability is relationship capital

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,506. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.