# Email Drafting

> Draft clear, well-structured emails and messages in the right tone: outreach, replies, follow-ups, requests, apologies, announcements, and declines. Use when users ask to write/draft/reply to an email or message, or want help phrasing something professionally or diplomatically. Triggers on mentions of email, draft a message, reply to, follow up, reach out, write to, politely decline, 邮件, 回复邮件, 写封邮件, 措辞, 委婉, 跟进.

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

---


# Email Drafting

Write emails people actually read and act on: clear ask, right tone, no wasted words.

## Structure

- **Subject** — specific and skimmable ("Re: pricing — need approval by Fri", not "Question").
- **Open** — one line of context or a warm hook; skip if it's a quick internal reply.
- **The point / ask** — what you want and by when, up front. Don't bury it.
- **Details** — only what's needed to act; bullets for multiple items.
- **Close** — clear next step + a polite sign-off.

Keep it short. Most good emails are 3–6 sentences.

## Tone presets

- **Professional** (default): warm but efficient, contractions ok.
- **Formal**: for outside/senior/legal — full sentences, no slang, measured.
- **Friendly**: peers/known contacts — light, direct.
- **Diplomatic**: for pushback/declines/bad news — acknowledge, be clear, offer an alternative.

## Tricky cases

- **Decline**: thank → clear no → brief reason or alternative → goodwill. Don't over-apologize.
- **Follow-up**: reference the prior thread, restate the ask, make it easy to say yes.
- **Apology**: own it plainly, state the fix, don't grovel.

## Guidance

- Ask for the essentials only if missing: recipient relationship, the goal, any deadline.
- Don't invent facts, names, or commitments — leave `[placeholders]` for the user to fill.
- Offer 2 tone options if the situation is sensitive and you're unsure which they want.
- Match the user's language; mirror the formality of the thread they're replying to.