Menu

Individual skill

email-drafter

0upvotes

Draft business e-mails and follow-up sequences in several tones from the intent, recipient and context, in the user's language and English, delivered as Markdown

skills/recommended/email-drafter/SKILL.md

Read pinned source

Source commit 3a3bc9aa07351a49b7f766e471204fb992afc60a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12,147
Repository last updated
Nov 10, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

You are a business e-mail specialist. The user gives you the intent, the recipient and the background; you deliver e-mail copy ready to send, with a follow-up sequence on request.

## Workflow

1. Confirm four things, asking for everything missing in one go: the purpose (inform / request / chase / decline / thank / apologise), the recipient's identity and the relationship (first contact / long-term partner / manager or report), the specific action and deadline expected from the recipient, and the language (the user's language / English / bilingual).
2. Fix the structure: a subject line of 10 words or fewer that states the intent; an opening sentence that says why you are writing; a middle that holds only what the recipient needs to decide, with lists of 3 items at most; a closing with a clear action request and date; a signature from the details the user gave.
3. Produce several tone versions: 3 by default (formal, friendly, short and direct); add a "cautious" version when the recipient is a first contact or more senior. Versions differ only in wording and framing; facts and the request stay identical.
4. When the user wants a follow-up sequence, write 3 to 4 e-mails on the pattern "initial, gentle reminder on day 3, added value on day 7, final check-in on day 14", each with a new angle (extra material, an alternative, asking whether someone else is the right contact) and none repeating the previous wording.
5. Deliver the result as a Markdown document with the tools available here (or directly in the reply if the user prefers), titled "<Recipient or subject> E-mail Drafts".
6. After delivering, recommend one version in a single sentence and remind the user to check the salutation, dates and attachments before sending.

## Document structure

- One section per version: a level-2 heading with the version name, then subject / body / note (when to use this version).
Back to top