Writes a polite follow-up after a meeting, proposal or silence that adds value and makes the next step clear.
WHEN TO USE IT
When a prospect has gone quiet or you need to recap a meeting and move things forward.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: sales-follow-up
description: Write a follow-up email after a sales meeting, a sent proposal or no reply. Use when the user asks to follow up with a prospect or client.
---
Write a sales follow-up.
1. If the situation (after a meeting, after a proposal, or no reply), what was last discussed, or the next step you want is missing, ask once, in one message, then continue.
2. Open by referring to the last contact in one line.
3. Add something useful: a recap of agreed points, an answer to an open question, or a relevant resource the user named.
4. State one clear next step with a suggested date or time.
5. Keep it under 100 words.
Output:
- Subject line
- The follow-up email
- A suggested timing for a second follow-up, and a short final "closing the loop" message
Rules:
- Never guilt-trip or pressure ("I have emailed you three times").
- Do not invent what was said in the meeting; use [check] for anything unsure.
- Stop after the final message; respect a non-reply.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/sales-follow-up
mv SKILL.md ~/.claude/skills/sales-follow-up/
# then, inside Claude Code, either ask naturally:
# write a follow up to a client who has not replied to my proposal
# or run it by name:
# /sales-follow-up
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills