Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

writing-an-email

Étoiles7

Forks3

Mis à jour23 avril 2026 à 21:22

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

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

redhuntlabs

redhuntlabs/wizard

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Secrétaires et assistants administratifs (sauf juridique, médical et direction)Bureau et soutien administratif·SOC 43-6014

SKILL.md

readonly

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)

Identify the single goal: information / ask / acknowledgment.
Write the subject line so it names the goal in 4-7 words.
Open with one sentence that names the recipient-specific context.
State the goal in one sentence.
Add at most 2 supporting sentences.
State the ask explicitly: what action, by when.
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

Plus depuis ce dépôt

même dépôt

building-a-discipline-spell

redhuntlabs/wizard

Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.

2026-04-237

building-a-spell

redhuntlabs/wizard

Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"

2026-04-237

building-a-subagent-spell

redhuntlabs/wizard

Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.

2026-04-237

building-a-workflow-spell

redhuntlabs/wizard

Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.

2026-04-237

chaining-spells

redhuntlabs/wizard

Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).

2026-04-237

discovering-spells

redhuntlabs/wizard

Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.

2026-04-237

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)

Identify the single goal: information / ask / acknowledgment.

Write the subject line so it names the goal in 4-7 words.

Open with one sentence that names the recipient-specific context.

State the goal in one sentence.

Add at most 2 supporting sentences.

State the ask explicitly: what action, by when.

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