/draft-reply
Draft an email response with tone matching the relationship context. Shows draft for approval before sending. Use when user says "draft a reply", "respond to this email", "write a response to [person]", or shares an email and asks for help replying. See also: `follow-up-draft`
$ npx -y skills add kbanc85/claudia --skill draft-reply --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
/draft-reply
Context preview
The summary Claude sees to decide when to auto-load this skill.
Draft an email response with tone matching the relationship context. Shows draft for approval before sending. Use when user says "draft a reply", "respond to this email", "write a response to [person]", or shares an email and asks for help replying. See also: `follow-up-draft`
SKILL.md
draft-reply.SKILL.mdname: draft-reply
description: Draft an email response with tone matching the relationship context. Shows draft for approval before sending. Use when user says "draft a reply", "respond to this email", "write a response to [person]", or shares an email and asks for help replying. See also: `follow-up-draft` for post-meeting thank-yous with meeting context.
effort-level: medium
Draft Reply
Draft a response to an email or message.
Usage
`/draft-reply`
Then provide:
- The email/message to respond to
- Any specific direction for the response
Context Gathering
From the Message
- Who is it from? (Check `people/` for context)
- What are they asking or saying?
- What's the underlying need?
- Any urgency indicators?
From Relationship
- Communication style preferences
- Relationship history
- Current context with this person
From User
- "What's your goal with this response?"
- "Any constraints?" (Timeline, tone, etc.)
- "Anything to avoid?"
Output Format
## Reply Draft
**To:** [Name] <[email]>
**Re:** [Subject]
---
[The drafted response]
---
**Notes:**
- Tone: [Professional / Warm / Direct / etc.]
- Key points addressed: [List]
- [Any considerations about timing or approach]
---
Adjustments needed? Ready to send?
Response Types
Information Request
- Provide what's asked clearly
- Offer additional helpful context
- Easy to scan
Decision Needed
- Clear options if applicable
- Your recommendation
- Easy to respond yes/no
Scheduling
- Propose specific times
- Flexible alternatives
- Clear next step
Difficult Message
- Acknowledge their perspective
- Address concerns directly
- Professional and measured
Decline/No
- Respectful but clear
- Brief explanation if appropriate
- Leave door open if warranted
Thank You/Acknowledgment
- Genuine appreciation
- Specific about what you valued
- Forward-looking if appropriate
Tone Matching
Consider:
- Their tone in the original message
- Your relationship history
- Cultural context
- The topic sensitivity
Options:
- **Formal:** "I appreciate your inquiry..."
- **Professional:** "Thanks for reaching out..."
- **Casual:** "Hey! Great question..."
- **Warm:** "So good to hear from you..."
Length Calibration
Match the energy:
- Short message → Short response
- Detailed message → Address all points
- Simple question → Simple answer
- Complex topic → Thorough but organized
General rule: Shorter is usually better.
Structure for Long Responses
If multiple points to address: 1. Opening acknowledgment 2. Point-by-point responses (numbered or bulleted) 3. Summary of any actions 4. Clear next step 5. Warm close
Safety Note
I'll show you the draft first. I will NOT send anything without your explicit approval.
Quick Options
"Want me to: 1. Draft as written 2. Adjust tone to [more formal / more casual] 3. Make it shorter 4. Add/remove something specific"
Read more
name: draft-reply description: Draft an email response with tone matching the relationship context. Shows draft for approval before sending. Use when user says "draft a reply", "respond to this email", "write a response to [person]", or shares an email and asks for help replying. See also: `follow-up-draft` for post-meeting thank-yous with meeting context. effort-level: medium
Draft Reply
Draft a response to an email or message.
Usage
`/draft-reply`
Then provide:
- The email/message to respond to
- Any specific direction for the response
Context Gathering
From the Message
- Who is it from? (Check `people/` for context)
- What are they asking or saying?
- What's the underlying need?
- Any urgency indicators?
From Relationship
- Communication style preferences
- Relationship history
- Current context with this person
From User
- "What's your goal with this response?"
- "Any constraints?" (Timeline, tone, etc.)
- "Anything to avoid?"
Output Format
## Reply Draft **To:** [Name] <[email]> **Re:** [Subject] --- [The drafted response] --- **Notes:** - Tone: [Professional / Warm / Direct / etc.] - Key points addressed: [List] - [Any considerations about timing or approach] --- Adjustments needed? Ready to send?
Response Types
Information Request
- Provide what's asked clearly
- Offer additional helpful context
- Easy to scan
Decision Needed
- Clear options if applicable
- Your recommendation
- Easy to respond yes/no
Scheduling
- Propose specific times
- Flexible alternatives
- Clear next step
Difficult Message
- Acknowledge their perspective
- Address concerns directly
- Professional and measured
Decline/No
- Respectful but clear
- Brief explanation if appropriate
- Leave door open if warranted
Thank You/Acknowledgment
- Genuine appreciation
- Specific about what you valued
- Forward-looking if appropriate
Tone Matching
Consider:
- Their tone in the original message
- Your relationship history
- Cultural context
- The topic sensitivity
Options:
- **Formal:** "I appreciate your inquiry..."
- **Professional:** "Thanks for reaching out..."
- **Casual:** "Hey! Great question..."
- **Warm:** "So good to hear from you..."
Length Calibration
Match the energy:
- Short message → Short response
- Detailed message → Address all points
- Simple question → Simple answer
- Complex topic → Thorough but organized
General rule: Shorter is usually better.
Structure for Long Responses
If multiple points to address: 1. Opening acknowledgment 2. Point-by-point responses (numbered or bulleted) 3. Summary of any actions 4. Clear next step 5. Warm close
Safety Note
I'll show you the draft first. I will NOT send anything without your explicit approval.
Quick Options
"Want me to: 1. Draft as written 2. Adjust tone to [more formal / more casual] 3. Make it shorter 4. Add/remove something specific"
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

