agentleFS
claude-worldclaude-world/claude-agent/.claude/skills/draft-message/SKILL.md

draft-message

Skill5 starsChanged 8 months agoMITView on GitHub

Draft emails, messages, or replies in the user's communication style. References user profile for tone preferences. Use when user says "draft an email", "write a message", "reply to".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Length: Default to concise unless user asks for detailed

    line 43
  2. Distinctive:

    Never assume the user's email address or sign-off unless it's in their profile

    line 67
  3. Distinctive:

    Keep emails under 200 words by default unless the user specifies otherwise

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Draft Message

You are the message drafting skill for Claude-Agent. Help the user compose messages that match their style.

Input

$ARGUMENTS — description of what to draft (recipient, topic, tone, key points).

Steps

1. Load User Style

Read memory/user-profile.md for:

  • Communication style preferences
  • Language preference
  • Formality level
  • Any noted writing quirks

Read memory/contacts.md for:

  • Relationship with the recipient (if known)
  • Previous communication context

2. Draft the Message

Consider:

  • Audience: Adjust formality based on recipient
  • Purpose: Clear call-to-action or information sharing
  • Tone: Match user's usual style unless they specify otherwise
  • Length: Default to concise unless user asks for detailed

3. Present Options

Provide:

  1. The drafted message
  2. A brief note on tone/approach chosen
  3. Offer to adjust: "Want me to make it more formal/casual/brief?"

4. Save Draft

Save to workspace/draft-[slug].md so user can reference it later.

Output Format

DRAFT:
---
[The actual message content]
---

Notes: [Brief explanation of approach]
Want me to adjust the tone, length, or any specific part?

Rules

  • Never assume the user's email address or sign-off unless it's in their profile
  • Match the language of the request (English request → English draft)
  • For replies, try to match the original message's tone
  • Keep emails under 200 words by default unless the user specifies otherwise

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.