Menu
Drafts professional emails with appropriate tone, clarity, and effectiveness for any communication scenario.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | draft-email |
| description | Drafts professional emails with appropriate tone, clarity, and effectiveness for any communication scenario. |
Generate professional, effective emails for any communication scenario with appropriate tone, structure, and clarity.
The Draft Email skill helps you:
Basic Usage (L1):
/draft-email [recipient] [topic] --purpose [goal]
/draft-email reply --context [previous conversation]
/draft-email template [type] --customize [details]
Advanced Usage (L2):
/draft-email --tone [formal/casual/friendly] --audience [executive/peer/client]
/draft-email --from-reference [similar email] --adapt [new context]
/draft-email polish --existing-draft [text] --improve [aspects]
Expert Usage (L3):
/draft-email --learn-from [sent emails] --style-match
/draft-email --sequence [multi-email campaign] --maintain-context
/draft-email --negotiation --strategy [collaborative/competitive]
Email Drafting by Scenario:
Tone Adjustment:
Email Structure:
Introduction / New Outreach:
Subject: Introduction - [Your Name] - [Your Company/Role]
Hi [Name],
My name is [Name] and I'm [your role] at [company].
I'm reaching out because [specific reason - show you've done research].
I'd love to [specific ask - meeting, call, or next step].
Would you have time for a [15-30 min] call [week of dates] to discuss?
Best,
[Name]
[Title]
[Contact info]
Meeting Request:
Subject: Meeting Request: [Topic] - [Your Name]
Hi [Name],
I'd like to request a meeting to discuss [specific topic].
The goal of this meeting would be [clear objective].
I'm available [specific time options] and can meet for [duration].
Let me know if any of those times work, or suggest an alternative that's better for you.
Thanks,
[Name]
Follow-Up:
Subject: Following up: [Previous subject]
Hi [Name],
I wanted to follow up on our [conversation/meeting/call] on [date] regarding [topic].
[Reference what was discussed or agreed upon]
[Update or ask - what's the next step?]
Let me know if you have any questions or need more information.
Best,
[Name]
Status Update:
Subject: [Project Name] Status Update - [Date]
Hi [Name/Team],
Here's the status update for [project]:
**Completed:**
- [Item 1]
- [Item 2]
**In Progress:**
- [Item 1] (ETA: [date])
- [Item 2] (ETA: [date])
**Blockers:**
- [Blocker 1] - [Proposed solution/owner]
- [Blocker 2] - [Proposed solution/owner]
**Next Steps:**
- [Step 1]
- [Step 2]
Let me know if you have any questions.
Best,
[Name]
Thank You:
Subject: Thank you - [Context]
Hi [Name],
Thank you so much for [what they did - be specific].
[Explain impact or why it matters]
I really appreciate your help with [aspect].
Let me know if there's anything I can do to return the favor.
Best,
[Name]
Example 1: Introduction Email
User: /draft-email russell@company.com "product partnership" --purpose "explore partnership opportunities"
PersonalOS:
Subject: Partnership Opportunity - PersonalOS for Cowork
Hi Russell,
My name is Alex and I'm the founder of PersonalOS, a productivity skill pack for Claude Cowork.
I've been following your work on AI agent systems and was impressed by your recent work on [specific achievement/research]. I think there could be interesting synergies between PersonalOS's adaptive learning capabilities and your work on [their area of expertise].
I'd love to explore potential partnership opportunities - whether that's integrating our systems, collaborating on research, or sharing insights with our respective communities.
Would you be open to a 30-minute call next week to discuss?
I'm available:
- Tuesday, April 2nd: 10:00 AM - 12:00 PM EST
- Thursday, April 4th: 2:00 PM - 4:00 PM EST
- Friday, April 5th: 11:00 AM - 1:00 PM EST
Let me know if any of those times work, or suggest an alternative that's better for you.
Best,
Alex
Founder, PersonalOS
GitHub: https://github.com/your-username/personal-os-cowork
---
Review before sending:
✓ Personal introduction with credibility
✓ Specific research on recipient (mention their achievement)
✓ Clear value proposition (synergies, collaboration)
✓ Specific call to action (30-min call)
✓ Multiple time options provided
✓ Professional closing with signature
Example 2: Follow-Up Email
User: /draft-email follow-up --context "Sent partnership email to Russell on March 27, no response yet"
PersonalOS:
Subject: Re: Partnership Opportunity - PersonalOS for Cowork
Hi Russell,
I wanted to follow up on my email from last week about a potential partnership between PersonalOS and your work on AI agent systems.
I understand you're likely busy, but I wanted to reiterate my interest in exploring how we might collaborate. Specifically, I think there's value in:
1. Integrating PersonalOS's adaptive learning capabilities with your agent architecture
2. Sharing research insights between our communities
3. Potential joint workshops or presentations
If this isn't a priority right now, no problem at all. But if you're interested, I'm still open to that 30-minute call to discuss.
Alternatively, if you know someone else on your team who might be a better fit for this conversation, I'd appreciate an introduction.
Best regards,
Alex
---
Review before sending:
✓ Followed up within reasonable timeframe (5 days)
✓ Reiterated value with specific points
✓ Gave graceful "no pressure" out
✓ Suggested alternative contact if appropriate
✓ Professional and respectful tone
Example 3: Proposal Email
User: /draft-email "client@company.com" "proposal for AI agent consulting engagement" --purpose "propose $15k 4-week engagement"
PersonalOS:
Subject: Proposal: AI Agent Consulting Engagement - PersonalOS
Hi [Client Name],
Following our discussion last week about your team's AI agent development challenges, I'd like to propose a consulting engagement to help accelerate your project.
**Proposal: AI Agent Architecture & Development (4 Weeks)**
**Scope:**
- Week 1: Architecture review and recommendations
- Analyze current system design
- Identify bottlenecks and optimization opportunities
- Propose improvements to agent orchestration and tool calling
- Week 2: Feature implementation sprint
- Implement 2-3 high-impact features based on Week 1 findings
- Code reviews and best practices guidance
- Documentation and team training
- Week 3: Integration and testing
- Integrate new features with existing system
- Performance testing and optimization
- Bug fixes and refinement
- Week 4: Knowledge transfer and handoff
- Comprehensive documentation
- Team training sessions
- Future roadmap recommendations
**Deliverables:**
- Architecture review document
- 2-3 implemented features with code
- Performance optimization recommendations
- Comprehensive documentation
- 4 hours of team training
**Investment:** $15,000
**Timeline:** Start week of [date], complete by [date]
**Next Steps:**
If this proposal aligns with your needs, I'd like to schedule a 30-minute call to:
- Confirm scope and priorities
- Discuss timeline adjustments if needed
- Answer any questions
Would [day/time] work for you?
Best,
Alex
---
Review before sending:
✓ Clear scope broken into weeks
✓ Specific deliverables listed
✓ Pricing and timeline explicit
✓ Clear next step (confirmation call)
✓ Professional proposal format
❌ Mistake 1: Vague subject line like "Question"
❌ Mistake 2: Burying the request in last paragraph
❌ Mistake 3: Too long, rambling emails
❌ Mistake 4: No clear call to action
❌ Mistake 5: Wrong tone for relationship
Audience Analysis:
Tone Matching:
Style Transfer:
Email Polishing:
Example 1: Tone Adjustment
User: /draft-email --tone formal --audience executive "CEO" "product launch update"
PersonalOS:
Subject: Product Launch Status Update - Q2 2026
Dear [CEO Name],
I am writing to provide a status update on the Q2 product launch.
**Launch Readiness:**
Current status: 78% complete
Key milestone: Alpha release scheduled for [date]
**Completed Milestones:**
- Core feature development (100%)
- Beta testing preparation (90%)
- Marketing materials (85%)
**Remaining Work:**
- Performance optimization (2 weeks)
- Bug fixes (1 week)
- Final QA (1 week)
**Risk Assessment:**
Risk level: Medium
Primary risk: Performance optimization may require additional testing
Mitigation plan: Allocating 2 additional engineers to optimization team
**Recommendation:**
Proceed with launch as scheduled, with contingency plan for 2-week delay if optimization requires more time.
I will provide weekly updates until launch.
Best regards,
[Your Name]
---
Tone analysis:
✓ Formal and professional (appropriate for CEO)
✓ Concise and results-oriented (executive preference)
✓ Clear risk assessment (executive decision-making)
✓ Specific action needed (approval to proceed)
Example 2: Style Transfer (Make More Concise)
User: /draft-email polish --existing-draft "Hi team, I hope everyone is having a good week. I wanted to reach out because I've been thinking about the project and I think we should probably consider moving the timeline back a little bit. The reason for this is that we've encountered some unexpected challenges with the integration work, and it's going to take us more time than we originally estimated. I think if we move the deadline back by about two weeks, it would give us enough time to make sure everything is working properly before we launch. Let me know what you think about this suggestion. Thanks!" --improve "conciseness"
PersonalOS:
Subject: Timeline Adjustment Request - [Project Name]
Hi team,
I recommend moving the project timeline back by two weeks to [new date].
**Reason:**
Integration challenges have taken longer than estimated, and additional time is needed to ensure quality before launch.
**Impact:**
New deadline: [date]
No other dependencies affected
Please confirm if this adjustment works for everyone.
Thanks,
[Your Name]
---
Improvements made:
✓ Reduced from 120 words to 45 words (62% shorter)
✓ Removed hedging language ("probably", "a little bit")
✓ Organized into clear structure with headers
✓ Specific new date and impact assessment
✓ Clear call to action
Example 3: Email Polishing for Client
User: /draft-email polish --existing-draft "Hi client, about your issue with the software, we looked into it and it seems like there's a bug. We're working on fixing it. Should be done soon. Let us know if you have more questions. Thanks!" --audience client
PersonalOS:
Subject: Update: Software Issue Resolution - [Ticket #]
Hi [Client Name],
Thank you for bringing the software issue to our attention. I wanted to provide you with an update.
**Issue Status:**
Our team has identified the cause and is currently implementing a fix.
**Timeline:**
We expect to resolve this issue and deploy the fix by [date/time].
**Next Steps:**
I'll send you a confirmation once the fix is live, along with instructions for any steps you may need to take.
If you experience any further issues or have questions, please don't hesitate to reach out.
We appreciate your patience as we work to resolve this.
Best regards,
[Your Name]
[Support Team]
---
Improvements made:
✓ Professional and reassuring tone (appropriate for client)
✓ Clear status and timeline provided
✓ Set expectations for next steps
✓ Added appreciation and reassurance
✓ Professional closing
❌ Mistake 1: One tone for all recipients
❌ Mistake 2: Too formal for internal team, too casual for executives
❌ Mistake 3: No consideration of cultural differences
❌ Mistake 4: Sending drafts without polishing
❌ Mistake 5: Ignoring which styles get good responses
Style Learning from Sent Emails:
Multi-Email Sequences:
Negotiation Emails:
Persuasion Frameworks:
Example 1: Style Learning & Matching
User: /draft-email --learn-from "my sent emails" --style-match
PersonalOS:
✓ Analyzed 1,247 sent emails from the past year
Your Email Style Profile:
- Length: Average 87 words (concise)
- Tone: Semi-formal to professional
- Structure: Often uses bullet points for clarity
- Subject lines: Usually 6-10 words, specific
- Opening: Direct, states purpose quickly
- Closing: Simple "Best, [Name]"
Patterns That Get Good Responses:
- Emails with bullet points have 40% higher response rate
- "Question" subject lines get fastest responses
- Direct ask in last paragraph improves response rate by 35%
- Short emails (under 100 words) get 25% more replies
Example of your style applied to new email:
Subject: Partnership Opportunity - PersonalOS
Hi Russell,
I'd like to explore a potential partnership between PersonalOS and your work on AI agent systems.
I think there's value in:
1. Integrating our adaptive learning capabilities
2. Sharing research insights
3. Potential collaboration opportunities
Would you be open to a 30-minute call next week to discuss?
I'm available Tuesday or Thursday afternoons.
Best,
Alex
---
Style matched to your profile:
✓ Concise (67 words)
✓ Bullet points for clarity
✓ Direct ask in last paragraph
✓ Simple closing
✓ Specific availability
Example 2: Multi-Email Sequence
User: /draft-email --sequence "sales outreach" prospect@company.com "product demo" --maintain-context
PersonalOS:
✓ Generated 4-email outreach sequence
Email 1: Initial Outreach
Subject: Demo Invitation: PersonalOS for Cowork
Hi [Name],
I'm reaching out to introduce PersonalOS, an adaptive productivity system for Claude Cowork users.
We help teams work smarter by:
- Learning your workflow patterns over time
- Automating repetitive tasks
- Suggesting optimizations based on your work style
Would you be open to a 20-minute demo to see if it's a good fit?
Best,
Alex
---
Email 2: Follow-Up (3 days later)
Subject: Re: Demo Invitation: PersonalOS
Hi [Name],
Following up on my previous email about PersonalOS.
I understand you're busy, but I wanted to mention that teams using PersonalOS have seen a 30% productivity increase on average.
If you're interested, I'm still open to that 20-minute demo.
Best,
Alex
---
Email 3: Value-Add Follow-Up (7 days later)
Subject: PersonalOS case study: [Similar Company]
Hi [Name],
I thought you might be interested in this case study about how [Similar Company] used PersonalOS to improve their team's workflow.
They saw results in just 2 weeks of implementation.
If you'd like to see the full case study or discuss how it might apply to your team, let me know.
Best,
Alex
---
Email 4: Final Outreach (14 days later)
Subject: One last question about PersonalOS
Hi [Name],
I'll make this my last email.
Before we close the loop, I had one question: Is now a good time to explore productivity tools, or should I reach out in a few months?
I want to respect your time and not be a pest, so your honest answer would be helpful.
Best,
Alex
---
Sequence strategy:
✓ Email 1: Initial outreach with clear value
✓ Email 2: Social proof and benefit reinforcement
✓ Email 3: Case study for credibility
✓ Email 4: Respectful close with question
Schedule:
- Email 1: Send now
- Email 2: Wait 3 days if no response
- Email 3: Wait 7 days after Email 2 if no response
- Email 4: Wait 14 days after Email 3 if no response
Example 3: Negotiation Email
User: /draft-email --negotiation --strategy collaborative client@company.com "contract terms discussion"
PersonalOS:
Subject: Contract Terms Discussion - [Project Name]
Hi [Client Name],
Thank you for sending over the contract. I've reviewed the terms and would like to discuss a few points.
**Where We Align:**
I'm in full agreement on:
- Project scope (3 phases as outlined)
- Timeline (8-week delivery)
- Quality standards (as specified in SOW)
**Areas for Discussion:**
1. Payment Schedule
- Your proposal: 50% upfront, 50% on delivery
- My suggestion: 25% upfront, 25% on phase 1 complete, 25% on phase 2 complete, 25% on delivery
- Rationale: This aligns payments with milestone progress and reduces risk for both parties
2. Revision Rounds
- Your proposal: 2 revision rounds
- My suggestion: 3 revision rounds
- Rationale: Ensures final deliverable meets your expectations without excessive back-and-forth
3. Timeline Buffer
- Your proposal: Fixed 8-week deadline
- My suggestion: 8-week target with 1-week buffer for unforeseen issues
- Rationale: Provides flexibility if unexpected challenges arise; you still get deliverables on original date
**My Commitment:**
I'm fully committed to delivering high-quality work within the agreed timeline. These adjustments help ensure a successful outcome for both of us.
**Next Steps:**
I'm open to discussing these points and finding a solution that works for you. Would you have time for a 30-minute call this week?
I'm available:
- [Day], [Time]
- [Day], [Time]
Let me know what works best for you.
Best regards,
Alex
---
Negotiation strategy applied:
✓ Collaborative approach (win-win focus)
✓ Start with agreement (builds rapport)
✓ Clear rationale for each request
✓ Reasonable compromises
✓ Maintains relationship focus
✓ Specific call to action
❌ Mistake 1: One-size-fits-all approach
❌ Mistake 2: Not learning from past emails
❌ Mistake 3: Wrong negotiation style for situation
❌ Mistake 4: Spamming with too many follow-ups
❌ Mistake 5: No measurement of effectiveness
Issue: Emails not getting responses
Issue: Wrong tone for recipient
Issue: Emails are too long and rambling
Issue: Can't find the right words for difficult email
Issue: Inconsistent style across emails
| After drafting... | Suggest... |
|---|---|
| Always | "Review before sending — nothing goes out without your approval." |
| Mentioned new person | Silently add to context/team-directory.md if not there |
| Decision in email | "Should I log this decision to your decision log?" |
| Follow-up pattern detected | Note in memory/patterns.md if this type of email is recurring |
PersonalOS skill: account-management
API endpoint testing, mocking, and integration testing for robust API development.
Optimize images, icons, and design assets for performance, quality, and developer handoff
Plan, track, and optimize budgets to maximize value and financial performance
CI/CD pipeline optimization, build failures, and deployment automation for DevOps workflows.
Code quality improvement, technical debt reduction, and refactoring patterns for maintainable software.