/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:
Claude Code
$ npx -y skills add kbanc85/claudia --skill draft-reply --agent claude-code
Codex
$ npx skills add kbanc85/claudia --skill draft-reply -a codex -y
Cursor
$ npx skills add kbanc85/claudia --skill draft-reply -a cursor -y
Gemini CLI
$ npx skills add kbanc85/claudia --skill draft-reply -a gemini-cli -y
GitHub Copilot
$ npx skills add kbanc85/claudia --skill draft-reply -a github-copilot -y
OpenCode
$ npx skills add kbanc85/claudia --skill draft-reply -a opencode -y
Windsurf
$ npx skills add kbanc85/claudia --skill draft-reply -a windsurf -y
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.
Other skills on claudia.
More skills from other plugins.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
distilly
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…
Questions about draft-reply.
- Which coding agents can use draft-reply?
- draft-reply installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

