---
name: Email Writer
slug: email-writer
category: Writing
description: Email Writer drafts clear, well-structured emails such as replies, outreach, and follow-ups in the right tone. Use it when you need a single email with an explicit ask, concrete next step, and recipient-appropriate register.
github: "https://github.com/holaboss-ai/holaOS/tree/main/apps/desktop/electron/default-skills/email-writer"
language: TypeScript
stars: 7385
forks: 641
install: "npx degit https://github.com/holaboss-ai/holaOS/tree/main/apps/desktop/electron/default-skills/email-writer ~/.claude/skills/email-writer"
installs_to: ~/.claude/skills/email-writer
source_path: apps/desktop/electron/default-skills/email-writer/SKILL.md
collection_size: 25
category_size: 1012
collection_url: "https://dirskills.com/collections/holaboss-ai/holaOS"
added: 2026-08-15T06:51:31.961Z
last_synced: 2026-08-15T06:51:31.961Z
canonical_url: "https://dirskills.com/skills/email-writer"
---

# Email Writer

Email Writer drafts clear, well-structured emails such as replies, outreach, and follow-ups in the right tone. Use it when you need a single email with an explicit ask, concrete next step, and recipient-appropriate register.

**Install:**

```bash
npx degit https://github.com/holaboss-ai/holaOS/tree/main/apps/desktop/electron/default-skills/email-writer ~/.claude/skills/email-writer
```

## README

# Email Writer

Write the email the reader can answer in one pass. Most email fails not on grammar but on clarity of ask: the recipient can't tell what you want, by when, or why it matters to them. Fix that first; everything else is polish.

## When to use this skill

Use Email Writer to draft or rewrite a single email — a reply, a cold or warm outreach, a follow-up, an update, a request. For multi-send marketing sequences and campaigns, use Email Marketing instead; for internal announcements to a whole team, use Internal Comms.

## Principles

- **One email, one job.** Lead with the purpose. If you're asking for something, make the ask explicit and easy to say yes to.
- **Front-load.** The recipient should get the point from the first two lines, before any context.
- **Respect their time.** Short by default. Cut throat-clearing ("I hope this finds you well…") unless the relationship calls for it.
- **Match the register.** Cold outreach, a peer reply, and a note to an exec are three different tones. Ask or infer the relationship and adjust formality, warmth, and length.
- **Make next steps concrete.** Propose a specific time, a clear deliverable, or a single question — not "let me know your thoughts."

## How to work

1. Establish the goal (what response do you want?), the recipient, and the relationship/tone.
2. Draft a subject line that states the point, not a vague topic.
3. Open with the ask or headline, add only the context that earns the yes, and close with a concrete next step.
4. Trim: remove hedges, filler, and anything the reader doesn't need to act.

## Output format

Return a **subject line** and the **body**. Keep paragraphs short. If useful, offer one alternative tone (e.g. warmer or more direct) rather than a single fixed draft.