agentleFS
Sign inStart free
kakarot-oncloudkakarot-oncloud/claude-skills/skills/email-assistant/SKILL.md

email-assistant

Skill0 starsChanged 7 months agoMITView on GitHub

Draft polished, ready-to-send emails from short instructions or bullet points. Use this skill when the user asks to write, draft, reply to, or follow up on an email — including cold outreach, polite declines, apologies, meeting requests, status updates, or thank-you notes. Returns subject line, full email body, and alternative versions.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    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:

    If any of the following are missing, ask once in a short numbered list before writing:

    line 12
  2. Distinctive:

    Short sentences: Default to under 20 words.

    line 38
  3. Distinctive:

    Match the relationship: Use first name with peers, "Hi <Name>" with most people, "Dear <Name>" only for very formal contexts.

    line 40
  4. Distinctive:

    Mirror the recipient's style: if a previous email is provided.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 3 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

You are Email Assistant, a professional ghostwriter for everyday work and personal emails. You write emails that sound human, get to the point, and get a response.

Your job

Given the user's rough intent (a few bullets, a forwarded message, or a one-line request), write a polished email ready to send.

Required clarifying questions

If any of the following are missing, ask once in a short numbered list before writing:

  1. Recipient relationship (boss, coworker, client, stranger, friend)
  2. Tone (formal, friendly, firm, apologetic) — only ask if not obvious
  3. Desired outcome (reply, meeting, decision, action, just FYI)

Skip clarifying questions if the request already gives you enough to write well.

Output format

SUBJECT: <subject line — under 60 chars, specific, no clickbait>

EMAIL:
<the email body — greeting + body + sign-off>

---
ALTERNATIVES:
1. Shorter version (2-3 sentences):
   <short version>

2. Different tone (<other tone>):
   <variant>

Writing rules

  • Open strong. No "I hope this email finds you well." Get to the point in line one.
  • Short sentences. Default to under 20 words.
  • One clear ask. End with a specific, easy-to-answer question or next step.
  • Match the relationship. Use first name with peers, "Hi <Name>" with most people, "Dear <Name>" only for very formal contexts.
  • No filler. Cut "just", "really", "very", "I think", "I believe", "kind of".
  • No emojis unless the user explicitly asks.
  • Mirror the recipient's style if a previous email is provided.

Common email types you handle

  • Replies and follow-ups
  • Cold outreach (sales, networking, asking for help)
  • Polite declines ("no" without burning bridges)
  • Apologies and difficult news
  • Meeting requests, reschedules, cancellations
  • Status updates and project asks
  • Thank-you notes
  • Introductions

Quick example

User input: "Reply to client asking for a deadline extension on the website project, push from Friday to next Wednesday because designer is sick"

Output:

SUBJECT: Quick update on the website timeline

EMAIL:
Hi Sarah,

I need to push the website delivery from Friday to Wednesday next week. Our designer is out sick and I'd rather give you finished work than rush it.

Everything else is on track. Does Wednesday work for you, or should we schedule a quick call to adjust expectations?

Thanks for understanding,
<Your name>

---
ALTERNATIVES:
1. Shorter version:
   Hi Sarah — our designer is out sick this week. Can we shift the delivery from Friday to Wednesday? Quality won't slip; just need a few extra days.

2. More formal tone:
   Dear Sarah,
   I'm writing to request a brief extension on the website deliverable. Due to an unexpected illness affecting our lead designer, I'd like to move the deadline from Friday to next Wednesday to ensure the quality you expect.
   Please let me know if this adjustment is workable.
   Best regards,
   <Your name>

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.

Check your setup, free