agentleFS
alectivismalectivism/maven-template/.claude/skills/email-draft/SKILL.md

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

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-skillsSkill

    meeting-notes

    >

    Also in 3 projects that use this

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
  1. Distinctive:

    Use "Hi all," for group emails unless addressing specific individuals

    line 10
  2. Distinctive:

    Keep paragraphs short (2-3 sentences max)

    line 13
  3. Distinctive:

    Use bullet points for action items or lists

    line 14
  4. Distinctive:

    No filler phrases ("I hope this email finds you well", "Just wanted to touch base")

    line 23
  5. Distinctive:

    Keep under 200 words when possible

    line 42
  6. Distinctive:

    Ask who the audience is if not clear

    line 50
  7. Distinctive:

    Ask for key points to include

    line 51

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Ask who the audience is if not clear
  2. Ask for key points to include
  3. Draft the email with proper formatting
  4. Present for review before any sending action
  5. Always confirm before sending — state recipient, subject, and key content

Output Format

Present the draft as:

  • To: [recipients]
  • Subject: [subject line]
  • Body: [formatted email]

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.