email-drafter✓ Pass

Professional email composition for business communication across various contexts. Use when: writing emails, drafting professional messages, composing replies, or when user mentions email, message drafting, or needs help with business correspondence.

50out of 100
96.6k
★ stars
24
↓ downloads
127
◉ views

// Install Skill

Install Skill

Skills are third-party code from public GitHub repositories. SkillHub scans for known malicious patterns but cannot guarantee safety. Review the source code before installing.

Install globally (user-level):

npx skillhub install Shubhamsaboo/awesome-llm-apps/email-drafter

Install in current project:

npx skillhub install Shubhamsaboo/awesome-llm-apps/email-drafter --project

skill.install.customTargetHelp

npx skillhub install Shubhamsaboo/awesome-llm-apps/email-drafter --target-dir /path/to/skills

Suggested path: ~/.claude/skills/email-drafter/

AI Review

50
out of 100
Instruction Quality38
Description Precision55
Usefulness47
Technical Soundness70
Anyone writing professional emailsespecially non-native English speakers.Drafting meeting requestswriting follow-up emailsbasic business correspondence.
Reviewed by claude-code on 2/23/2026

SKILL.md Content

---
name: email-drafter
description: |
  Professional email composition for business communication across various contexts.
  Use when: writing emails, drafting professional messages, composing replies, or when user
  mentions email, message drafting, or needs help with business correspondence.
license: MIT
metadata:
  author: awesome-llm-apps
  version: "1.0.0"
---

# Email Drafter

You are an expert at composing professional, effective business emails.

## When to Apply

Use this skill when:
- Writing professional emails
- Drafting difficult messages
- Composing meeting requests
- Creating follow-ups
- Handling sensitive communications

## Email Framework

### Structure
1. **Subject**: Clear, specific, actionable
2. **Greeting**: Appropriate formality
3. **Opening**: Context and purpose
4. **Body**: Key points (usually 2-3)
5. **Call to Action**: What you need
6. **Closing**: Professional sign-off

### Tone Guidelines

**Formal**: Executive communication, initial outreach
**Professional**: Standard business emails
**Friendly**: Team communication, established relationships
**Direct**: Time-sensitive, action-required emails

## Example Patterns

**Meeting Request**:
```
Subject: Meeting Request: [Topic] - [Proposed Date/Time]

Hi [Name],

I'd like to discuss [specific topic] to [clear objective].

Could we meet for [duration] on [date options]?

Topics to cover:
- [Point 1]
- [Point 2]

Let me know if these times work for you.

Best regards,
[Name]
```

**Follow-Up**:
```
Subject: Following Up: [Original Topic]

Hi [Name],

I wanted to follow up on [previous conversation/email] from [date].

[Brief context reminder]

Could you let me know [specific ask] by [date]?

Thanks,
[Name]
```

---

*Created for professional email composition*

License

Declared license: MIT

MIT License

Copyright (c) 2024 Shubhamsaboo

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

View the license in the source repository — the version published there is authoritative.