email-drafter

What this skill does

# Email Drafter Skill

Generate professional, well-structured emails from bullet points or conversation summaries with consistent tone and formatting.

## Use Cases

- Convert meeting notes into status update emails
- Draft professional requests or proposals
- Create announcements to teams or stakeholders
- Write follow-up emails after conversations
- Respond to inquiries professionally
- Draft meeting recaps and action items

## How to Use This Skill

Provide Claude with:

1. **Content**: Bullet points, notes, or conversation summary
2. **Tone**: One of (formal, casual, technical)
3. **Context**: One of (status_update, request, announcement, follow_up, response, recap)
4. **Optional**: Recipient name/title, any specific requirements

Claude will transform the input into a polished, professional email with:

- Appropriate greeting and sign-off
- Clear structure and flow
- Consistent tone throughout
- Professional formatting
- Proper punctuation and grammar

## Supported Tones

### Formal

- Professional business language
- Complete sentences and formal grammar
- Respectful and courteous
- Suitable for: executives, external stakeholders, important announcements
- Example phrases: "I would like to...", "Thank you for your consideration...", "Please find attached..."

### Casual

- Friendly and approachable tone
- Conversational language
- Professional but relaxed
- Suitable for: teammates, internal communications, collaborative contexts
- Example phrases: "Just wanted to let you know...", "Feel free to reach out...", "Let's connect..."

### Technical

- Precise and detailed
- Uses domain-specific terminology
- Direct and clear
- Suitable for: technical teams, system documentation, architecture discussions
- Example phrases: "The implementation includes...", "The system parameters are configured to...", "Technical specifications..."

## Supported Contexts

### Status Update

**Purpose**: Inform recipients about current progress, completed work, and next steps

**Structure**:

1. Opening: What period/project this covers
2. Completed items: What was accomplished
3. In-progress items: Current work
4. Upcoming items: What's next
5. Blockers/Issues: Any challenges (if applicable)
6. Closing: Invitation for questions/discussion

**Best for**: Weekly updates, sprint reviews, project progress reports

### Request

**Purpose**: Ask for action, approval, resources, or input from recipients

**Structure**:

1. Context: Why this request is important
2. What's being asked: Clear, specific request
3. Why it matters: Benefits or urgency
4. Timeline: When needed
5. Next steps: How to respond
6. Closing: Appreciation and contact info

**Best for**: Budget requests, time off, resources, approvals, feedback

### Announcement

**Purpose**: Communicate news, changes, or information to a team or stakeholder group

**Structure**:

1. Hook: Lead with the announcement
2. Context: Why this change/news matters
3. Details: Specific information
4. Impact: How it affects recipients
5. Next steps: What recipients should know/do
6. Closing: Point of contact for questions

**Best for**: Product launches, policy changes, team updates, organizational changes

### Follow-up

**Purpose**: Continue a conversation, remind about commitments, or move items forward

**Structure**:

1. Reference: What previous conversation/commitment this relates to
2. Update: What's happened since
3. Call to action: What's needed next
4. Offer to help: Your contribution/availability
5. Closing: Clear next steps

**Best for**: After meetings, checking on decisions, ensuring progress

### Response

**Purpose**: Reply to an inquiry, offer, or question

**Structure**:

1. Appreciation: Thank them for reaching out
2. Answer: Direct response to their question/request
3. Details: Additional relevant information
4. Next steps: How to proceed
5. Closing: Reaffirm helpfulness

**Best for**: Replying to inquiries, addressing questions, responding to proposals

### Recap

**Purpose**: Summarize a meeting, conversation, or decision for the record

**Structure**:

1. Opening: What was discussed
2. Key decisions: What was decided
3. Action items: Who's doing what by when
4. Outstanding issues: What still needs resolution
5. Closing: Confirmation and next meeting

**Best for**: Meeting summaries, decision documentation, action item tracking

## Examples

### Example 1: Status Update (Formal Tone)

**Input**:

- Tone: formal
- Context: status_update
- Bullet points:
  - Completed authentication module implementation
  - Unit tests at 94% coverage
  - Performance benchmarks show 15% improvement
  - Database migration testing in progress
  - Need approval on API schema changes
  - Team meeting scheduled for Thursday

**Output**:

```
Dear Team,

I am writing to provide a status update on the authentication module project for the week of November 4-8.

Completed Items:
The authentication module implementation has been completed and is ready for integration testing. Unit test coverage has reached 94%, demonstrating comprehensive code validation. Performance benchmarks indicate a 15% improvement over the previous implementation.

In Progress:
Database migration testing is currently underway to ensure data integrity during the transition. We anticipate completion by end of day Friday.

Upcoming:
The team will gather on Thursday to discuss and potentially approve the proposed API schema changes. Your input on this matter would be greatly appreciated.

Please let me know if you have any questions or concerns regarding this update.

Best regards,
[Your Name]
```

### Example 2: Request (Casual Tone)

**Input**:

- Tone: casual
- Context: request
- Recipient: Engineering Manager
- Bullet points:
  - Need to attend conference next month
  - Will present technical talk on distributed systems
  - Conference dates March 15-17
  - Budget needed for travel and registration
  - Will share updates with team while there

**Output**:

```
Hi [Manager Name],

I wanted to reach out about an opportunity I'd like to pursue. I've been selected to give a talk on distributed systems architecture at the upcoming tech conference on March 15-17. It's a great chance to represent the company and share what we've learned.

Here's what I'd need:
- Travel and lodging budget (I'll keep it reasonable)
- Time off for the conference dates
- Conference registration fee

I'll definitely share key learnings and insights with the team when I get back, so we can all benefit from the experience. I'm happy to discuss this further if you have any questions.

Let me know what you think!

Thanks,
[Your Name]
```

### Example 3: Announcement (Formal Tone)

**Input**:

- Tone: formal
- Context: announcement
- Bullet points:
  - New deployment pipeline going live
  - Reduces deployment time from 2 hours to 15 minutes
  - All teams can self-serve deployments
  - Training session Thursday
  - FAQ document shared in wiki
  - Questions? Contact DevOps team

**Output**:

```
Subject: New Deployment Pipeline Now Available

Dear Team,

We are pleased to announce the launch of our new automated deployment pipeline, effective immediately. This infrastructure improvement represents a significant operational enhancement for our entire organization.

Key Benefits:
Deployment time has been reduced from 2 hours to approximately 15 minutes, enabling more frequent and reliable releases. Additionally, all development teams now have self-service deployment capabilities, reducing dependency on centralized operations.

What You Need to Know:
A comprehensive training session will be held on Thursday at 2:00 PM to walk through the new process. A detailed FAQ document has been posted to our internal wiki for reference.

Next Steps:
Please plan to attend the training session or review the documentation at your earliest convenience. If you have questions or encounter any issues, please reach out to the DevOps team.

We are confident this will improve our development velocity and system reliability.