Skip to content
Back to skills

Writing An Email

ASecurity

Use when drafting any email - replies, cold outreach, asks, status updates, thank-yous

  • 9 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added May 27, 2026
toolsgo

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add redhuntlabs/wizard --skill writing-an-email --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Writing An Email?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Writing An Email
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/redhuntlabs-writing-an-email/badge)](https://www.skillsdirectory.com/skills/redhuntlabs-writing-an-email)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: writing-an-email
description: Use when drafting any email - replies, cold outreach, asks, status updates, thank-yous
kind: content
audience: anyone
ai-tools: any
complexity: simple
time: 2-5 min
version: 1.0.0
source: bundled
---

# Writing an Email

## What this does

Drafts a focused email that opens with the point, has one ask, and ends without padding. Works for replies, cold outreach, status notes, asks, and thank-yous.

## When to use

- Drafting any new email
- Replying to a long thread that needs a clear answer
- Sending a request that has a specific ask

## What you bring (Inputs)

- Recipient name and one thing about them (role, prior context, shared connection)
- The single thing you want them to do or know
- Tone target (warm / neutral / formal — defaults to neutral)

## What you get (Output)

A complete email: subject line, opener, body, ask, sign-off.

## How it works (Steps)

1. Identify the single goal: information / ask / acknowledgment.
2. Write the subject line so it names the goal in 4-7 words.
3. Open with one sentence that names the recipient-specific context.
4. State the goal in one sentence.
5. Add at most 2 supporting sentences.
6. State the ask explicitly: what action, by when.
7. Sign off without "I hope this finds you well" or apology.

## Quality bar

- Under 150 words for routine emails
- One clear ask (or zero, if it's just info)
- Subject line stands alone (recipient knows the topic without opening)
- No opener filler ("Hope you're well", "Sorry for the delay")

## Variations

- **Cold outreach**: opener cites a specific recent thing about the recipient
- **Long-thread reply**: open with one-sentence summary of the decision before details
- **Apology email**: state what happened, what you're doing about it, what they can expect; no excuses
- **Thank-you**: name the specific thing you're thanking for; no ask

## Example

**Input**: Recipient: Sara, my manager. Goal: ask for headcount approval for one designer hire.

**Output**:

> Subject: Headcount ask: 1 designer for Q3
>
> Hi Sara,
>
> Following our roadmap convo last Friday, I'd like to lock in one designer hire for Q3.
>
> The case: shipping the new dashboard on time needs design ownership we don't have today. I've sourced 4 candidates already and can have an offer out by end of June.
>
> Can you approve this by Friday so I can start interviews next week?
>
> Thanks,
> Alex

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.