post-call-follow-up
Skill1 starsChanged 10 days agoMITView on GitHub
Drafts a B2B follow-up email after a sales, discovery or partnership call, from rough notes or a transcript. Use whenever the user shares call notes, a transcript or a call summary and wants a follow-up, recap, next-steps or thank-you email, even if they only say "write the email after my call with X".
In this repository7 other files it gives its agents.
- account-research-briefSkill
- call-prep-briefSkill
- cold-outreach-emailSkill
- deal-qualification-checkSkill
- discovery-call-guideSkill
- re-engagement-emailSkill
- sales-process-guideSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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 21
If any of these are still placeholders, ask for them once before drafting.
- Distinctive: line 24
Ask only for what is missing:
- Distinctive: line 25
Call notes or transcript (any language, any state)
- Distinctive: line 30
Read all the notes. Pull out the prospect's stated problem, what was agreed, open questions, and who owes what by when.
- Distinctive: line 32
Read references/tone-by-country.md and set formality and sign-off for the recipient's country.
- Distinctive: line 34
Check it against the rules, then deliver it with short flags: what you left out, missing names or dates, anything uncertain.
- Distinctive: line 41
Add 1–2 sentences on where we fit, tied to that need.
- Distinctive: line 55
One thread per email: Keep unrelated product lines and sensitive topics out so the ask stays clear.
≈ “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.
Files
Post-call follow-up email
A good follow-up is short, proves you listened, and makes the next step easy. Prospects skim on mobile, so every sentence has to earn its place.
Setup (fill in once)
- SENDER_NAME: {{your first name}}
- COMPANY_NAME: {{your company}}
- BOOKING_LINK: {{your scheduling link}}
- SIGNATURE: does the email client add it automatically? {{yes/no}}
- LANGUAGE: {{language for external emails, e.g. English}}
If any of these are still placeholders, ask for them once before drafting.
Inputs
Ask only for what is missing:
- Call notes or transcript (any language, any state)
- Recipient name, role, company, country
- Anything promised on the call (materials, NDA, intro, date)
Steps
- Read all the notes. Pull out the prospect's stated problem, what was agreed, open questions, and who owes what by when.
- Choose one thread to push forward. A follow-up that chases several topics gets no clear answer, so leave the rest out.
- Read references/tone-by-country.md and set formality and sign-off for the recipient's country.
- Draft one email in LANGUAGE using the format below.
- Check it against the rules, then deliver it with short flags: what you left out, missing names or dates, anything uncertain.
Format
Subject: [Their company] × COMPANY_NAME – [specific topic]: next steps
- Open with thanks plus one specific detail from the call, which shows the notes were read.
- Recap 3–5 points of their need, in their words.
- Add 1–2 sentences on where we fit, tied to that need. Skip generic capability lists.
- List next steps with owner and date ("We: X by [date]"; "[Their company]: Y").
- End with one clear ask. The deal is active after a call, so make it specific: a concrete item or a proposed date.
- Close per the tone table. Stop there if the email client adds the signature.
- Stay under about 200 words, with short sentences and 1–2 line paragraphs.
Links
Send links as HTML anchor text, for example <a href="BOOKING_LINK">pick a time here</a>, because raw URLs can be rewritten into long redirect links that look like spam. Offer BOOKING_LINK only after two concrete time slots in the recipient's time zone. If you send through a connected mail tool, open the sent message and check the link renders as anchor text.
Rules, and why
- One variant only. Choosing between drafts is the user's time; a single considered draft is faster to review.
- Only facts from the notes. An invented number or commitment can damage trust or bind the sender to something they never said. Leave a [placeholder] for any missing name, owner or date and flag it.
- No pricing, ROI claims or hype words. Pricing needs context a short email can't give. If cost came up, the next step is a proposal or discovery phase.
- No budget or funding questions. They belong on a call, where tone and context are clear.
- One thread per email. Keep unrelated product lines and sensitive topics out so the ask stays clear.
- No apologies for delay, "just checking in" or filler. They signal low confidence and add words without adding information.
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.

