email-draft
Skill1 starsChanged 6 months agoMITView on GitHub
Draft emails in MMA brand voice. Use for "write an email", "draft a message", "reply to", "follow up with".
10 other projects use a version of this.
Adopted by
Most recently taken up by
- CatCatUncle/openworkbuddytheir own version, first seen Nov 5, 2026
- FishRaposo/aria-agenttheir own version, first seen Nov 1, 2026
- procpalee/claude-skillstheir own version, first seen Oct 23, 2026
- greatSumini/cc-systemtheir own version, first seen Oct 8, 2026
- metadist/synaplan-desktoptheir own version, first seen Sep 26, 2026
- oswarld/notion-skillstheir own version, first seen Sep 23, 2026
Used with
Projects with it also use meeting-notes.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
claude-office-skillsSkillmeeting-notes
>
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- shiwenwen/hope-agent★ 1.9ksame name
- greatSumini/cc-system★ 438same name
- CatCatUncle/openworkbuddy★ 398same name
- metadist/synaplan-desktop★ 257same name
- oswarld/notion-skills★ 11same name
- KhaledSaeed18/dotclaude★ 5same name
- koach08/claude-code-skills★ 4same name
- yakatotech/claude_code_env★ 1same name
- FishRaposo/aria-agent★ 0same name
- procpalee/claude-skills★ 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 repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asana-taskSkill
- briefing-prepSkill
- case-studySkill
- content-draftSkill
- content-strategySkill
- event-promoSkill
- handoffSkill
- lab-summarySkill
- launch-strategySkill
- linkedin-scrapeSkill
- meeting-followupSkill
- member-commsSkill
- mma-brand-guidelinesSkill
- mma-org-contextSkill
- mma-pptx-builderSkill
- mma-writing-styleSkill
- office-editingSkill
- press-releaseSkill
- reddit-scrapeSkill
- research-briefSkill
- researchSkill
- search-and-scrapeSkill
- sharepoint-findSkill
- slack-summarySkill
- zapier-workflow-builderSkill
- commitSkill
- content-shippedSkill
- daily-briefingSkill
- endSkill
- marvinSkill
- mavenSkill
- skill-creatorSkill
- template-skillSkill
- updateSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use "Hi all," for group emails unless addressing specific individuals
- Distinctive: line 13
Keep paragraphs short (2-3 sentences max)
- Distinctive: line 14
Use bullet points for action items or lists
- Distinctive: line 23
No filler phrases ("I hope this email finds you well", "Just wanted to touch base")
- Distinctive: line 42
Keep under 200 words when possible
- Distinctive: line 50
Ask who the audience is if not clear
- Distinctive: line 51
Ask for key points to include
“Common” is measured: kept by at least 6 in 10 of the 4 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
Email Drafting — MMA Style
Formatting Standards
- Font: Aptos 12pt (Outlook default) — do not specify other fonts
- Use "Hi all," for group emails unless addressing specific individuals
- For 1:1 emails, use "Hi [First Name],"
- Sign-off: Match the sender's typical style. Default: "Best," or "Thanks,"
- Keep paragraphs short (2-3 sentences max)
- Use bullet points for action items or lists
Voice & Tone
MMA's voice is the Hero archetype: energetic, sharp, smart, clear, confident, generous.
- Lead with the purpose/ask in the first sentence
- Be direct — respect the reader's time
- Use active voice
- Include specific dates, numbers, and next steps
- No filler phrases ("I hope this email finds you well", "Just wanted to touch base")
Audience-Specific Guidelines
Internal (MMA Staff)
- Casual but professional
- Reference Slack channels, Asana tasks, SharePoint links as appropriate
- Use first names
Members (CMOs, Marketing Leaders)
- Professional, peer-level tone
- Reference MMA programs by full name on first mention, then acronym
- Highlight value and outcomes, not process
- Include relevant data points (CAP +160% lift, MMGF +50% ROAS, etc.)
Board Members
- Executive-level brevity
- Lead with impact/decision needed
- Bullet key points
- Keep under 200 words when possible
External / Prospects
- Include MMA boilerplate in signature area
- Reference member count (825+), reach (350,000+ marketers)
- Focus on peer-driven collaboration and evidence-based approaches
Process
- Ask who the audience is if not clear
- Ask for key points to include
- Draft the email with proper formatting
- Present for review before any sending action
- Always confirm before sending — state recipient, subject, and key content
Output Format
Present the draft as:
- To: [recipients]
- Subject: [subject line]
- Body: [formatted email]
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.

