email-drafter
Skill0 starsChanged 4 months agoMITView on GitHub
Use when someone asks to draft an email, turn bullet points into an email, write a professional email, or convert rough notes into a polite email draft.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- github/awesome-copilottheir own version, first seen Oct 25, 2026
- genspark-ai/genofficetheir own version, first seen Oct 25, 2026
- ARCASSystems/FounderOStheir own version, first seen Oct 24, 2026
- schuligan/claude-skills-collectiontheir own version, first seen Oct 13, 2026
- Hassaan146/claude-skillstheir own version, first seen Jul 25, 2026
- ReaperOAK/ForgeOStheir own version, first seen Jun 8, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- github/awesome-copilot★ 41ksame name
- genspark-ai/genoffice★ 12ksame name
- claude-office-skills/skills★ 433same name
- Hassaan146/claude-skills★ 18same name
- ARCASSystems/FounderOS★ 7same name
- xcrrr/claude-skills★ 6same name
- pb-jwhitlock/claude-skills★ 0same name
- ReaperOAK/ForgeOS★ 0same name
- schuligan/claude-skills-collection★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- humanize-notesSkill
- session-recapSkill
- skill-builderSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Before drafting, read and apply the shared writing principles in ../_shared/human-voice.md (sound human, preserve voice, don't invent, stay …
- Very specific: line 16
If bullet points were passed inline as arguments, use $ARGUMENTS as the content.
- Distinctive: line 17
If no arguments were given, ask the user to paste their bullet points (one idea per line).
- Distinctive: line 19
Capture context: Ask for these two things in a single question (offer a default so the user can skip):
- Distinctive: line 47
If the bullets are too vague to form a coherent email, tell the user what's missing instead of producing a hollow draft.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What This Skill Does
Converts bullet points of what you want to say into a polite, professional, and concise email draft. Produces the draft as text in chat. It never sends anything.
Before drafting, read and apply the shared writing principles in ../_shared/human-voice.md (sound human, preserve voice, don't invent, stay proportional, plain punctuation).
Steps
- Gather the bullet points.
- If bullet points were passed inline as arguments, use
$ARGUMENTSas the content. - If no arguments were given, ask the user to paste their bullet points (one idea per line).
- If bullet points were passed inline as arguments, use
- Capture context. Ask for these two things in a single question (offer a default so the user can skip):
- Recipient / relationship: who it's going to (boss, client, teammate, vendor, etc.). Default: neutral professional.
- Desired tone: formal, friendly-professional, or firm. Default: friendly-professional.
- Draft the email using the structure below:
- Greeting appropriate to the recipient/relationship.
- A concise body that covers every bullet point, in a logical order, in complete sentences.
- A polite closing line.
- Body only — do not add a subject line and do not add a signature/sign-off name.
- Present the draft in a code block or clearly delimited so it's easy to copy. Then offer to revise (shorter, warmer, more direct, more formal, etc.).
Output Template
[Greeting],
[Concise, polite body that addresses each bullet point in complete sentences.]
[Polite closing line.]Notes
The shared human-voice principles above already cover not inventing details, staying proportional, and plain punctuation. These are specific to email drafting:
- Draft only. This skill has no ability to send email and must never claim or imply that it sent anything. Its output is a draft for the user to review and send themselves.
- Match the tone to the recipient and the tone choice. A firm email to a vendor reads differently than a friendly note to a teammate.
- If the bullets are too vague to form a coherent email, tell the user what's missing instead of producing a hollow draft.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.