# Email Drafting

> Professional email drafting — structure, tone, and templates for common business contexts

- Skill: `furkangonel/email-drafting` (Agent Skill)
- Install (CLI): `npx skillmds@latest add furkangonel/email-drafting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/furkangonel/email-drafting/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: furkangonel (https://skillmd.com/u/furkangonel)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/furkangonel/email-drafting

---


# Email Drafting SOP

## Goal
Write clear, professional emails that get read and acted upon. Match tone to context. Drive the desired outcome with minimal friction for the recipient.

## Email Anatomy

```
Subject: [Category] Specific, actionable title

Hi [Name / Team],

[Opening: 1 sentence — context or reason for writing]

[Body: 2-4 sentences — the point, details, or ask]

[CTA: 1 clear ask or next step]

[Closing],
[Your name]
```

## Subject Line Formulas

| Pattern | Example |
|---|---|
| Direct action | "Review needed: API proposal by Friday" |
| Question | "Quick question about Q3 roadmap scope" |
| FYI/update | "Update: auth migration completed" |
| Number | "3 options for the database decision" |
| Deadline | "Decision needed before Thursday standup" |

**Rules:**
- Under 50 characters where possible
- Put the most important word first
- Avoid "Hello", "Following up", "Just checking in" as openers
- Never use ALL CAPS

## Tone Calibration

| Context | Tone | Avoid |
|---|---|---|
| Executive / C-suite | Concise, direct, no fluff | Long intros, excessive detail |
| Colleague / peer | Conversational, collaborative | Overly formal language |
| Client / external | Professional, warm | Jargon, internal acronyms |
| Vendor / support | Clear, factual, firm | Aggressive or passive |
| Sensitive topics | Empathetic, non-accusatory | Blame, assumptions |

## Templates

### Follow-up
```
Subject: Following up — [topic]

Hi [Name],

I wanted to follow up on [topic] from [context/date].

[One sentence on current status or what you're waiting on]

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

Thanks,
[Name]
```

### Meeting request
```
Subject: 30 min: [topic] this week?

Hi [Name],

I'd love to get 30 minutes with you to discuss [topic and why it matters].

My availability this week:
- [Day], [time range]
- [Day], [time range]

Does any of these work? Happy to adjust.

[Calendly link if available]

Thanks,
[Name]
```

### Cold outreach
```
Subject: [Specific hook — their work, mutual connection, or shared interest]

Hi [Name],

[1 sentence: who you are + why you're reaching out — be specific, not generic]

[1-2 sentences: the value or relevance to them specifically]

[Clear, low-friction ask — not "let me know if you're interested" but a specific question or step]

[Name]
```

### Decline / no
```
Subject: Re: [original subject]

Hi [Name],

Thank you for thinking of me / reaching out about [topic].

Unfortunately, [reason — brief and honest, not over-explained].

[Optional: alternative or redirect if helpful]

I appreciate your understanding.

Best,
[Name]
```

### Escalation
```
Subject: [ESCALATION] [topic] — needs resolution by [date]

Hi [Name],

I'm escalating [issue] as it's blocking [impact].

**Background**: [2 sentences max]
**What's needed**: [specific decision or action]
**Deadline**: [date/time and why]
**Who's involved**: [names]

Let me know how you'd like to proceed.

[Name]
```

### Status update / progress report
```
Subject: [Project] update — [date or sprint]

Hi [Name/Team],

Quick update on [project]:

✅ Done: [key completions]
🔄 In progress: [current work, ETA]
⚠️ Blocked: [blockers, if any]
📅 Next: [upcoming milestones]

Full details in [link if applicable].

[Name]
```

## Opening Lines That Work

**Instead of "I hope this finds you well":**
- "I wanted to share a quick update on..."
- "Following our conversation last Tuesday..."
- "I have a decision I need your input on."
- "Good news — [milestone] is complete."

**For cold email:**
- "I read your post on [topic] and wanted to..."
- "[Mutual contact] suggested I reach out..."
- "I noticed [specific thing about their work]..."

## Proofreading Checklist

- [ ] Subject line is specific and under 50 chars
- [ ] Recipient name spelled correctly
- [ ] One clear ask per email
- [ ] No passive-aggressive tone ("as per my last email", "per our conversation")
- [ ] Attachments actually attached (if mentioned)
- [ ] Reply-all vs reply checked
- [ ] No internal info that shouldn't go external
- [ ] Deadline is explicit (not "soon" or "ASAP")
- [ ] CTA requires a yes/no or a date, not an open-ended response

## Length Guide

| Email type | Target length |
|---|---|
| Internal quick update | 3-5 sentences |
| Meeting request | 5-8 sentences |
| External professional | 100-150 words |
| Escalation | 150-200 words with structure |
| Cold outreach | Under 100 words |