Create a post-meeting thank-you or follow-up email with key points and next steps. Use when user says \"follow-up email\", \"thank you note\", \"post-meeting email\", \"send a follow-up to [person]\", or after a meeting capture when next steps need communicating. See also: `draft-reply` for general email responses unrelated to a meeting.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add kbanc85/claudia --skill follow-up-draft --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Follow Up Draft?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/kbanc85-follow-up-draft-claudia)More formats (shields.io, HTML) on the badges page.
---
name: follow-up-draft
description: "Create a post-meeting thank-you or follow-up email with key points and next steps. Use when user says \"follow-up email\", \"thank you note\", \"post-meeting email\", \"send a follow-up to [person]\", or after a meeting capture when next steps need communicating. See also: `draft-reply` for general email responses unrelated to a meeting."
argument-hint: "[person name]"
effort-level: medium
---
# Follow-Up Draft
Draft a post-meeting follow-up or thank-you email.
## Usage
`/follow-up-draft [person name]`
## Context Gathering
### Check Existing Context
1. Recent meeting notes with this person
2. Their file in `people/`
3. Any commitments made
4. Topics discussed
### Ask If Needed
- "What was the meeting about?"
- "Any specific commitments to confirm?"
- "Anything particular to emphasize?"
## Output Format
```
## Follow-Up Email: [Person Name]
### Re: [Meeting/Topic]
---
**To:** [Name] <[email if known]>
**Subject:** [Suggested subject line]
---
Hi [Name],
[Opening - thank them, reference the conversation]
[Key points or takeaways from discussion]
[Confirm any commitments - what you'll do, what they mentioned]
[Next steps or call to action]
[Warm close]
[Your name]
---
**Notes:**
- [Any context about tone or relationship]
- [Timing suggestion for sending]
**Before sending:**
- [ ] Confirm accuracy of commitments mentioned
- [ ] Check tone matches relationship
- [ ] Verify email address
---
Ready to send? Let me know if you want adjustments.
```
## Email Types
### Thank You + Recap
After a productive meeting:
- Express appreciation
- Summarize key points
- Confirm next steps
### Commitment Confirmation
When specific promises were made:
- Clearly state what each party committed to
- Include deadlines
- Suggest follow-up touchpoint
### Continued Discussion
When more conversation needed:
- Reference where you left off
- Propose next steps
- Offer availability
### Re-engagement
After time has passed:
- Reference last interaction
- Share relevant update
- Propose reconnection
## Tone Calibration
Based on relationship:
- **New relationship:** More formal, clear context
- **Established:** Warmer, can be briefer
- **Client:** Professional, confirm value
- **Peer:** Conversational, mutual respect
- **Mentor/Senior:** Appreciative, respectful
Based on meeting outcome:
- **Positive:** Enthusiastic, forward-looking
- **Neutral:** Professional, clear next steps
- **Challenging:** Diplomatic, solution-focused
## Length
- Keep short: 100-200 words
- Get to the point quickly
- One clear ask or next step
- Easy to respond to
## Common Patterns
### "Great to meet you"
For first-time meetings, new relationships
### "Thanks for your time"
For meetings where they gave valuable input
### "Following up on our discussion"
For ongoing conversations
### "Wanted to confirm"
When specific commitments need clarity
## Safety Note
I'll draft the email and show it to you. I will NOT send anything without your explicit approval.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!