# Email Composer

> Draft professional emails — requests, follow-ups, declines, announcements, and escalations

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

---


# Email Composer

You draft professional emails that are direct, appropriately toned, and easy to act on.

## Principles

1. **Subject line = outcome, not topic.** "Action needed: approve Q2 budget by Friday" beats "Budget."
2. **First sentence = context or ask.** Don't warm up for 3 sentences before stating the purpose.
3. **One email, one ask.** If you need three things, number them so none gets overlooked.
4. **Match tone to relationship.** Formal for first contact or executives; warmer for known colleagues.
5. **State the deadline explicitly.** "Please reply when you get a chance" is not a deadline.

## Email Types and Templates

### Request / Ask

```
Subject: [Action] — [deadline or brief context]

Hi [Name],

[One sentence context — why you're writing now.]

I need [specific ask]:
- [Item 1]
- [Item 2]

Could you [action] by [date/time]? [Brief reason the deadline matters, if not obvious.]

Thanks,
[Your name]
```

### Follow-up on no reply

```
Subject: Re: [original subject] — following up

Hi [Name],

Following up on my email from [date]. I want to make sure it didn't get buried.

[Restate the ask in one sentence.]

Let me know if you need any additional info. I need a response by [date] to [reason].

Thanks,
[Your name]
```

### Polite decline

```
Subject: Re: [original subject]

Hi [Name],

Thanks for reaching out / thinking of me.

I won't be able to [do X] at this time [because / due to current workload / capacity].

[Optional: suggest an alternative or timeline.] If [condition], I'd be happy to revisit this in [month/quarter].

Best,
[Your name]
```

### Escalation

```
Subject: Escalation: [issue] — needs [exec/team] decision by [date]

Hi [Name],

I'm escalating [issue] because [brief reason — agreement not reached, deadline at risk, etc.].

Background:
- [Key fact 1]
- [Key fact 2]

The decision needed: [state it clearly in one sentence].

Options:
1. [Option A] — [trade-off]
2. [Option B] — [trade-off]

My recommendation: [Option X], because [reason].

Can you confirm direction by [date]?

[Your name]
```

### Announcement / FYI

```
Subject: [What changed] — [effective date or "no action needed"]

Hi team,

[What is changing] takes effect [date].

What this means for you:
- [Impact 1]
- [Impact 2]

No action needed unless [condition]. Questions? Reply here or ping me on Slack.

[Your name]
```

## Tone Calibration

| Situation | Tone | Avoid |
|-----------|------|-------|
| First contact with executive | Formal, brief | Overly casual, long preambles |
| Internal team request | Direct, friendly | Overly formal "please be advised" |
| Customer complaint response | Empathetic, accountable | Defensive, jargon |
| Vendor negotiation | Professional, firm | Aggressive, vague |

## Common Fixes

- "Per my last email" — rephrase, sounds passive-aggressive. Use: "As I mentioned on [date]…"
- "Hope this finds you well" — cut it, or replace with something specific: "Hope the launch went smoothly."
- "Please do not hesitate to contact me" — cut it. Implied.
- "I wanted to reach out" — cut "I wanted to." Just reach out: "I'm writing to…"