---

name: email-voice

description: >

Drafts, replies to, and rewrites emails in the user's established

writing voice using the companion email-tone.md reference.

Use whenever the user asks to write, draft, compose, reply to,

respond to, edit, rewrite, shorten, polish, or redraft an email.

Also use when the user provides an email or thread and asks

what to send back. Do not use for tasks that only involve

summarising, searching, analysing, or actioning emails.

---

# Email Voice

## Purpose

Create send-ready email copy that reflects the user's personal

writing style as defined in `email-tone.md`.

This skill is universal. All personal preferences, tone rules,

writing conventions, and examples belong in `email-tone.md`.

## Required reference

Before drafting or editing an email:

1. Read `email-tone.md` in full.

2. Apply its guidance throughout the email, including any

audience-specific and thread-specific conventions.

3. Use its worked examples to calibrate the writing style,

not as templates to copy.

4. Follow the reference unless the user explicitly requests

something different or higher-priority instructions apply.

Do not introduce additional stylistic rules or preferences

that conflict with the reference.

If `email-tone.md` is unavailable, use the available context

to produce a natural, appropriate email. Do not claim to have

matched the user's established voice.

## When to use

Use this skill for:

- New emails

- Replies to emails or threads

- Follow-ups and chasers

- Rewriting or polishing existing emails

- Shortening or adjusting email copy

- Any request to formulate an email response

Do not use it when the user only wants an email retrieved,

summarised, classified, analysed, or actioned without

drafting copy.

## Process

1. Understand the user's intended message and objective.

2. Identify the recipient, context, and position in the

email thread where possible.

3. Apply the relevant guidance from `email-tone.md`.

4. Preserve all material facts, requests, commitments,

and intended meaning.

5. Produce the email in the user's established voice.

Do not invent facts or commitments.

Do not ask unnecessary clarifying questions when a useful

draft can be produced from the available context.

## Output

Unless otherwise requested:

- Return one send-ready email.

- Include a subject line for new emails when useful.

- Omit the subject line for replies.

- Return only the email copy, without preambles,

explanations, or drafting notes.

- Use placeholders only when essential information

is missing.

If the user requests alternatives or commentary,

follow their instructions.

## Final check

Before responding:

1. Confirm the draft follows `email-tone.md`.

2. Check for any prohibited words or phrases.

3. Confirm the greeting and sign-off fit the thread.

4. Verify that the user's meaning and material facts

are preserved.

5. Return the final email.