skills/follow-up-email-writer/SKILL.md
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.
npx skillsauth add stephenrogan/csm-skills follow-up-email-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Provide:
Every follow-up email has four sections:
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."
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.
| Action | Owner | Deadline | |--------|-------|----------| | [action] | [name] | [date] |
Rules:
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]."
| Meeting Type | Tone | Length | Special Considerations | |-------------|------|--------|----------------------| | Routine check-in | Warm, brief | 50-80 words + action table | Keep it light. Do not over-document a casual conversation | | QBR | Professional, thorough | 100-150 words + action table | This is a formal record. Include key data points discussed and strategic agreements | | Escalation review | Accountable, specific | 80-120 words + action table | Lead with the resolution update. Include what has been done and what remains | | Kickoff | Enthusiastic but structured | 100-150 words + action table | Restate the goals, timeline, and responsibilities agreed in the kickoff | | Renewal | Value-forward, clear | 80-120 words + action table | Reinforce value delivered. Document any commercial terms discussed | | Difficult conversation | Empathetic, precise | 80-100 words + action table | Acknowledge the difficulty. Document exactly what was agreed to prevent misinterpretation |
| Exclude | Why | |---------|-----| | Risk assessments | Customer-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 jargon | Health scores, NPS references, QBR acronyms (unless the customer uses these terms) | | Multiple CTAs | The follow-up documents what happened. It is not a place for new asks. One CTA maximum (usually "let me know if I missed anything") |
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]
development
Structures the CSM's week based on their portfolio status, upcoming events, overdue items, and strategic priorities. Produces a time-blocked plan that balances reactive demands with proactive account management. Use when asked to plan a week, structure daily priorities, build a weekly schedule, allocate time across accounts, manage a busy week, or when a CSM feels overwhelmed and needs to determine where to focus. Also triggers for questions about time management, weekly planning, account prioritisation for the week, daily priority setting, or how to balance competing demands across a portfolio.
development
Constructs a compelling value narrative for a customer account by connecting product usage to business outcomes in the customer's language. Produces different versions for different audiences -- the champion, the CFO, the board. Use when asked to build a value story, articulate ROI, create a business case for the customer, prepare value evidence for a renewal or QBR, or when a CSM needs to translate usage metrics into business impact the customer will recognise. Also triggers for questions about value articulation, ROI storytelling, customer business case, value evidence, or how to prove the product is worth the investment.
data-ai
Takes raw usage data -- even a spreadsheet export or pasted metrics -- and identifies patterns, risks, and opportunities. Translates product analytics into account intelligence a CSM can act on. Use when asked to interpret usage data, analyse product metrics, make sense of a usage report, identify trends in customer behaviour, flag usage-based risks, or when a CSM has data but does not know what it means for the account. Also triggers for questions about usage analysis, product analytics interpretation, behavioural pattern detection, usage-based risk identification, or turning raw metrics into actionable insight.
development
Builds a structured 30-60-90 day plan for a CSM taking over a new book of accounts or joining a new team. Prioritises accounts by risk and value, identifies immediate relationship actions, and structures the ramp to full productivity. Use when asked to plan a book transition, create a new CSM onboarding plan, structure a territory takeover, build a 30-60-90 plan for a new role, or when a CSM is inheriting accounts and needs a systematic approach to getting up to speed. Also triggers for questions about account transitions, new book ramp-up, CSM onboarding to a portfolio, territory planning, or how to take over accounts from another CSM.