Email Writing Clarity SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as email-writing-clarity/SKILL.md.

---
name: email-writing-clarity
description: "Write emails that get read and acted on: bottom line up front, one topic per email, subject lines with purpose and date, explicit asks with owners and deadlines, skimmable structure, plain-word swaps, rules for emails to many people and a ten-second phone test from the reader's side. Use whenever someone needs a clearer email, a better subject line, to rewrite a long email, write to a senior leader, send an update or announcement, or wants people to actually act on their emails."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/email-inbox/email-writing-clarity/
  category: productivity
  subcategory: email-inbox
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-13"
---

# Email Writing Clarity

People skim email. They read the subject, the first line or two, and decide whether to act now, later or never. Nielsen Norman Group's research on reading behaviour has long shown that people scan screens rather than reading every word. [Reference, Nielsen Norman Group] Yet many emails hide the request in the fourth paragraph, cover three topics at once, use vague subject lines and leave readers guessing what to do and by when.

This skill writes and rewrites emails so they get read and acted on: a subject line that says what the email is for, the main point first (often called BLUF, bottom line up front), one topic per email, clear asks with owners and dates, scannable structure for longer messages, plain words and a final check from the reader's side.

## Operating principles
1. **Bottom line up front.** The decision, request or update goes in the first sentence.
2. **One email, one topic.** Separate topics get separate emails and subjects.
3. **Make the ask explicit.** Who needs to do what by when.
4. **Design for skimming.** Short paragraphs, bullets for lists, bold only for the key ask or date.
5. **Plain words.** Short sentences, common words, no jargon the reader may not share.

## Subject lines
| Weak | Clear |
|---|---|
| Update | Launch moved to 21 Oct: no action needed |
| Question | Approve budget by Thu? Q4 events |
| Meeting | Decision needed: vendor choice, 30 min Tue |
| Following up | Signed contract needed by Fri 18 Oct |
| Report | Weekly sales: up 8%, two risks inside |

Useful prefixes: Action:, Decision needed:, FYI:, Approve:, Reply by <date>:

## Structure for longer emails
```
Subject: <purpose and date>
Line 1: bottom line (what you need or what changed)
Context: 2 to 3 sentences, only what the reader needs
Details: bullets or a short table
Ask: who, what, by when
Next step: what happens after they reply
```

## When to use, and when not to
Use it for important updates, requests to busy people, emails to senior leaders, project summaries, announcements, emails sent to many people and rewriting long drafts.

Don't use it to soften conflict or bad news alone (`difficult-emails`) or for quick everyday replies (`email-reply-drafting`), though the same principles apply.

## Inputs
- The draft or notes.
- The audience: who reads it, how senior, how familiar with the topic.
- The purpose: inform, request, decide, persuade.
- Any deadlines and attachments.

## Workflow

### Step 1. Write the bottom line
In one sentence: what does the reader need to know or do?

### Step 2. Check the topic count
Split the email if it covers more than one topic that needs separate action.

### Step 3. Write the subject line
Purpose plus key date or action, under about 60 characters so it shows on phones.

### Step 4. Cut context
Keep only what the reader needs to act. Move background to an attachment or link.

### Step 5. Structure for skimming
Bullets for lists of three or more, a short table for comparisons, bold for the single key ask or deadline.

### Step 6. Make asks explicit
Name people for actions, give dates, and say what happens if there is no reply.

### Step 7. Simplify the language
Short sentences, active voice, everyday words, no unexplained acronyms.

### Step 8. Read as the recipient
On a phone, in ten seconds: what is this about and what must I do?

## Before and after
**Before:**
"Hi all, I hope everyone had a good weekend. As you may know, we have been looking at different options for the event venue for a while now and there have been a number of conversations with various suppliers. After a lot of discussion we think we might have narrowed it down, but we would really appreciate everyone's thoughts..."

**After:**
```
Subject: Decision needed by Thu: event venue (2 options)

Hi all, please vote for one of two venues by Thursday 5pm.
- Option A: Harbour Hall, 200 people, £4,800, near the station
- Option B: The Loft, 150 people, £3,900, includes catering
I recommend A because we expect 170 guests. Reply with A or B;
no reply counts as agreeing with the recommendation.
```

## Plain-word swaps
| Instead of | Use |
|---|---|
| At this point in time | Now |
| In order to | To |
| `Leverage` (as a verb) | Use |
| Utilise | Use |
| Going forward | From now on, or delete |
| Please be advised that | Delete |
| Circle back | Reply, or talk again |

## Emails to many people
- Put the action for each group at the top ("Managers: approve by Thu. Everyone else: no action").
- Use Bcc for large external lists to protect addresses.
- Avoid reply-all requests; ask for replies to the sender or a form.

## Output format
```
1. Bottom line (one sentence)
2. Subject line options (2 to 3)
3. Rewritten email
4. Asks: who, what, by when
5. What was cut or moved, and why
```

## Length guide
| Email type | Target |
|---|---|
| Quick reply | 2 to 5 sentences |
| Request | Under 150 words |
| Update or summary | Under 250 words, with a link for detail |
| Announcement | Under 300 words; key facts in a short list |
If an email needs more, it is probably a document.

## Formatting rules
- One idea per paragraph, two to three sentences each.
- Bullets for three or more parallel items; numbered steps for sequences.
- Bold only the single most important ask or date, never whole sentences.
- Dates written in full with the day and time zone where relevant, such as Thursday 17 October, 5pm WAT.
- Links described by what they open ("the signed contract"), not "click here".

## Attachments
Say what each attachment is and what the reader should do with it. For more than two, list them; for large or changing files, share a link with access checked.

## Using AI to tighten drafts
Ask the agent to rewrite a draft with the bottom line first, cut it by a third and list the asks. Then read the result as the recipient: the shorter version should still contain every fact needed to act.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Senior or executive reader | Three to five lines; options and a recommendation |
| Technical audience | Keep precise terms; still lead with the point |
| Readers in other languages | Simple sentences; avoid idioms; dates spelled out |
| Legal or formal notices | Keep required wording; add a plain summary first |
| The email keeps growing | Turn it into a short document and send a link |

## Handoffs to related skills
- Quick replies: `email-reply-drafting`
- Sensitive messages: `difficult-emails`
- Reusable formats: `email-templates`
- Longer workplace documents: the Workplace Writing skills

## Worked example
An operations manager's weekly update was 600 words and few people acted on it. The rewrite opened with a three-line summary ("Shipping is on track; two risks need decisions; one action for team leads"), moved metrics into a five-row table, put decisions needed at the top with names and dates, and linked to the full report. The subject changed from "Weekly update" to "Ops week 41: 2 decisions needed by Wed". Replies with decisions arrived the same day.

## Common mistakes
- Vague subjects such as "Update" or "Quick question".
- The ask in the last paragraph.
- Several topics in one email.
- Walls of text with no structure.
- Jargon and acronyms the reader may not know.

## Self-check before you answer
- Is the bottom line in the first sentence?
- Does the subject line show purpose and date?
- Is every ask assigned with a date?
- Can the email be understood on a phone in ten seconds?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/email-inbox/email-writing-clarity/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.