/follow-up-draft
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`
$ npx -y skills add kbanc85/claudia --skill follow-up-draft --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/follow-up-draft
Context preview
The summary Claude sees to decide when to auto-load this skill.
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`
SKILL.md
follow-up-draft.SKILL.mdname: 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.
Read more
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.
Terminal-based AI chief of staff. Remembers relationships, tracks commitments, helps you think strategically. Runs on Claude Code.
Repo: kbanc85/claudia
Other skills on claudia.
- /auto-research
Iteratively improve a local artifact (draft, document, page) by running a hill-climbing loop. The user names the artifact, the evaluator, and the budget. Claudia edits the artifact, scores it, keeps it if better or reverts if worse, repeats. Use when user says "iterate on this",
Open skill - /brain-monitor
Launch the Brain Monitor TUI, a real-time terminal dashboard for watching Claudia's memory system. Triggers on "brain monitor", "show dashboard", "memory dashboard", "terminal brain". See also: `brain` for a 3D graph view in the browser.
Open skill - /brain
Launch the Brain Visualizer, a real-time 3D view of memory and relationships. Triggers on "show your brain", "visualize memory", "open the brain", "memory graph". See also: `brain-monitor` for a terminal dashboard alternative.
Open skill - /build-team
Propose a personalized team of specialized agents based on the user's profile, goals, and how they actually work. Runs the proposal through an independent Checker, gates on the user's approval, and applies with rollback. Use when the user says "build my team", "set up my
Open skill - /capture-meeting
Process meeting notes or transcript to extract decisions, commitments, and insights. Use when user shares transcript or says "capture this meeting", "here are my notes from the call". See also: `meeting-prep` for pre-call briefings; `follow-up-draft` for post-meeting emails.
Open skill - /client-health
Health check across active client engagements showing status, deliverables, and concerns. Triggers on "how are my clients?", "client status", "client health check".
Open skill

