Agent skill

Email Composer

by curiositech in curiositech/some_claude_skills

Draft professional emails for various contexts including business, technical, and customer communication.

MITAuto-check passedWriting & Content

Install Email Composer

skills CLI
$ npx skills add curiositech/some_claude_skills --skill email-composer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install curiositech/some_claude_skills email-composer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/email-composer .claude/skills/email-composer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
email-composer
GitHub stars
243
Used in
4 other repos
Token cost
~1.8k tokens
SKILL.md length
282 words
Files
2
Skills in repo
109
Repo updated
First seen
Licence
MIT

At a glance

Draft professional emails for various contexts including business, technical, and customer communication.

  • The user needs help writing emails
  • SKILL.md covers Quick start, Email structure, Common email types and Tone guidelines, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Composing professional messages

What it does

Email Composer is an agent skill from curiositech/some_claude_skills. Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in Writing & Content, covering Email writing. The repository describes itself as: Claude skills that make my life easier. The licence is MIT.

When your agent uses it

  • The user needs help writing emails
  • Composing professional messages

Example prompts

  • “/email-composer”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit

What it can do on your machine

Read from SKILL.md and the folder at commit 6713fc7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Email Composer loads about 1.8k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 282 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from curiositech/some_claude_skills at commit 6713fc7, republished under its MIT licence (© curiositech). 282 words, ~1,834 tokens.

Download SKILL.mdSave it as .claude/skills/email-composer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
email-composer
description
Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.
allowed-tools
Read, Write, Edit
metadata.category
Content & Writing
metadata.tags
email, communication, professional-writing

Email Composer

Quick start

Provide context and purpose, and I'll draft an appropriate email.

What I need:

  • Purpose of email (request, follow-up, announcement, etc.)
  • Recipient relationship (colleague, customer, manager, vendor)
  • Key points to include
  • Desired tone (formal, casual, urgent, friendly)

Email structure

Standard professional email format:

Subject: [Clear, specific subject line]

[Greeting],

[Opening - context/purpose]

[Body - main points]

[Closing - call to action]

[Sign-off]
[Your name]

Common email types

Request for information
Subject: Question about Q4 project timeline

Hi [Name],

I hope this email finds you well. I'm reaching out regarding the Q4 product launch timeline.

Could you provide an update on:
- Current progress on feature development
- Expected completion date for testing phase
- Any blockers or dependencies we should be aware of

This will help us coordinate with the marketing team for the launch materials.

Thanks in advance for your help!

Best regards,
[Your name]
Follow-up email
Subject: Following up: Proposal for new payment system

Hi [Name],

I wanted to follow up on the payment system proposal I sent last week. I understand you're busy, so I wanted to make sure it didn't get lost in your inbox.

To recap, the proposed system would:
- Reduce transaction fees by 30%
- Integrate with existing accounting software
- Improve customer checkout experience

I'd be happy to schedule a brief call to discuss any questions you might have.

Looking forward to hearing from you.

Best,
[Your name]
Technical update
Subject: API Maintenance Window - [Date]

Team,

This is a reminder that we'll be performing scheduled maintenance on our API infrastructure on [Date] from [Time] to [Time] [Timezone].

During this window:
- API endpoints will be unavailable
- Database will be upgraded to v14
- SSL certificates will be renewed

Expected downtime: 2 hours

What you need to do:
- Notify your users of the planned downtime
- Ensure retry logic is in place for API calls
- Monitor your application after maintenance completes

If you have any concerns or conflicts with this schedule, please let me know by [Date].

Technical details available in our status page: [link]

Thanks,
[Your name]
Customer support
Subject: Re: Issue with order #12345

Hi [Customer name],

Thank you for reaching out about your order. I'm sorry to hear you're experiencing this issue.

I've looked into your order (#12345) and found the following:

[Explanation of the issue]

To resolve this, I've:
- [Action taken 1]
- [Action taken 2]

You should see [expected outcome] within [timeframe].

If you continue to experience any problems, please don't hesitate to reply to this email or call us at [phone number].

We appreciate your patience and understanding.

Best regards,
[Your name]
Customer Support Team
Meeting request
Subject: Meeting request: Discuss database migration strategy

Hi [Name],

I'd like to schedule a meeting to discuss our approach for the upcoming database migration.

Agenda items:
- Review migration timeline and milestones
- Discuss rollback strategy
- Identify potential risks and mitigation plans
- Assign team responsibilities

Estimated duration: 45 minutes

I'm available:
- Monday 2-4 PM
- Wednesday 10 AM - 12 PM
- Friday 1-3 PM

Please let me know what works best for you, or feel free to suggest alternative times.

Best,
[Your name]

Tone guidelines

Formal tone
  • Use complete sentences
  • Avoid contractions
  • Professional language
  • Proper titles (Dr., Mr., Ms.)
Casual tone
  • Contractions acceptable
  • Conversational language
  • Still professional
  • First names
Urgent tone
  • Clear subject line with [URGENT] or [ACTION REQUIRED]
  • Bold key points
  • Explicit deadline
  • Direct call to action

Subject line best practices

Good subject lines:

  • "Action required: Submit timesheet by Friday"
  • "Q4 Sales Report - Review needed"
  • "Meeting rescheduled: Project kickoff now Thursday"
  • "Quick question about deployment process"

Bad subject lines:

  • "Update"
  • "Question"
  • "Hello"
  • "Following up"

Email etiquette

DO:

  • Respond within 24 hours (even if just to acknowledge)
  • Use clear, specific subject lines
  • Keep it concise
  • Proofread before sending
  • Include relevant context
  • Use bullet points for multiple items
  • End with clear call to action

DON'T:

  • Use ALL CAPS
  • Over-use exclamation marks!!!
  • Mark everything as urgent
  • Reply all unless necessary
  • Send when emotional
  • Include unnecessary recipients
  • Forget attachments mentioned in email

Templates by scenario

Decline request politely
Subject: Re: [Original subject]

Hi [Name],

Thank you for thinking of me for [request/opportunity].

Unfortunately, I won't be able to [participate/help/attend] due to [brief reason - optional]. However, I'd recommend [alternative suggestion if applicable].

I appreciate your understanding, and I hope we can collaborate on future opportunities.

Best regards,
[Your name]
Apologize for mistake
Subject: Apology and correction: [Issue]

Hi [Name],

I'm writing to apologize for [specific mistake]. This was an error on my part, and I take full responsibility.

To correct this:
- [Action 1 already taken]
- [Action 2 in progress]
- [Preventive measure for future]

I understand this may have caused [impact], and I'm committed to ensuring it doesn't happen again.

If you have any concerns or questions, please don't hesitate to reach out.

Sincerely,
[Your name]
Share good news
Subject: Great news: [Achievement/milestone]

Team,

I'm excited to share that we've [accomplished goal]!

This success is thanks to:
- [Team/person contribution 1]
- [Team/person contribution 2]

Impact:
- [Metric improvement]
- [Business benefit]

Thank you all for your hard work and dedication. Let's keep up the momentum!

Cheers,
[Your name]

Closing phrases by context

Formal:

  • Sincerely
  • Best regards
  • Respectfully
  • Cordially

Professional:

  • Best
  • Thanks
  • Kind regards
  • Regards

Casual:

  • Cheers
  • Thanks!
  • Talk soon
  • Best

Email composition checklist

  • Clear, specific subject line
  • Appropriate greeting
  • Purpose stated upfront
  • Key points organized with bullets/numbers
  • Clear call to action or next steps
  • Appropriate tone for audience
  • Proofread for typos
  • Attachments included (if mentioned)
  • Recipients correct (To, CC, BCC)
  • Professional signature

© curiositech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .claude/skills/email-composer of curiositech/some_claude_skills.

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit 6713fc7

Used in 4 other repositories

We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in curiositech/some_claude_skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Email Composer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Email Composer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Composer this skillcuriositech/some_claude_skills2434 repos~1.8kAutomated safety check: PassMIT
End-of-Life Announcement Writergetcrew44/crew44356—~3.1kAutomated safety check: PassMIT
Write Like Me Bootstrapjxnl/personal-monorepo-template562—~1.1kAutomated safety check: PassNone
Email Voice Profileyc-software/qm15k—~856Automated safety check: PassMIT
Compose Outreachw95/awesome-claude-corporate-skills237—~1.4kAutomated safety check: PassMIT
Email Opsaffaan-m/ECC275k1 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Drafts a clear, empathetic end-of-life announcement for a product, feature or plan, covering rationale, customer impact, transition support, timeline and next steps.

    356 GitHub stars~3.1k tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed
  • Write Like Me Bootstrap

    jxnl/personal-monorepo-template

    Bootstrap a durable "write like me" skill from the user's own Slack and email writing.

    562 GitHub stars~1.1k tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed
  • Email Voice Profile

    yc-software/qm

    Build (or refresh) a voice profile of how the user writes email, from their own sent Gmail.

    15k GitHub stars~856 tokensUpdated today
    Writing & ContentAuto-check passed
  • Compose Outreach

    w95/awesome-claude-corporate-skills

    Generate personalized outreach messages using Common Room signals.

    237 GitHub stars~1.4k tokensUpdated 7 mo ago
    Writing & ContentAuto-check passed
  • Email Ops

    affaan-m/ECC

    Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.

    275k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed
  • Email Draft In Voice

    yc-software/qm

    Draft Gmail in the user's own voice from the voice profile built by email-voice-profile.

    15k GitHub stars~481 tokensUpdated today
    Writing & ContentAuto-check passed

More from curiositech/some_claude_skills

All 109 skills in this repo
  • Crisis Detection Intervention AI

    curiositech/some_claude_skills

    Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols.

    243 GitHub starsUsed in 3 repos~3.8k tokens
    Auto-check passed
  • Form Validation Architect

    curiositech/some_claude_skills

    End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards.

    243 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Competitive Cartographer

    curiositech/some_claude_skills

    Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.

    243 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • GitHub Actions Pipeline Builder

    curiositech/some_claude_skills

    Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.

    243 GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check: notes
  • Computer Vision Pipeline

    curiositech/some_claude_skills

    Build production computer vision pipelines for object detection, tracking, and video analysis.

    243 GitHub starsUsed in 1 repo~4k tokens
    Auto-check passed
  • Design Archivist

    curiositech/some_claude_skills

    Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction…

    243 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Questions about Email Composer

What does Email Composer do?

Draft professional emails for various contexts including business, technical, and customer communication. Email Composer is an agent skill from curiositech/some_claude_skills. Draft professional emails for various contexts including business, technical, and customer communication.

When should I use Email Composer?

Email Composer fits situations like: the user needs help writing emails; composing professional messages.

How do I install Email Composer in Claude Code?

Run `npx skills add curiositech/some_claude_skills --skill email-composer -a claude-code`. Or copy the skill folder (.claude/skills/email-composer in curiositech/some_claude_skills) into .claude/skills/email-composer in your project. Claude Code loads it when a task matches its description.

How do I install Email Composer in Codex?

Run `npx skills add curiositech/some_claude_skills --skill email-composer -a codex`. Or copy the skill folder (.claude/skills/email-composer in curiositech/some_claude_skills) into .agents/skills/email-composer in your project. Codex loads it when a task matches its description.

Can I use Email Composer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add curiositech/some_claude_skills --skill email-composer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-composer, .gemini/skills/email-composer, .github/skills/email-composer and .opencode/skills/email-composer in your project.

What does Email Composer need to run?

SKILL.md names no scripts, command-line tools or credentials: Email Composer is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit.

Does Email Composer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Email Composer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Email Composer use?

Email Composer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Email Composer use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Email Composer?

Skills that share tags, products or a category with Email Composer: End-of-Life Announcement Writer (getcrew44/crew44, 356 stars), Write Like Me Bootstrap (jxnl/personal-monorepo-template, 562 stars), Email Voice Profile (yc-software/qm, 15k stars) and Compose Outreach (w95/awesome-claude-corporate-skills, 237 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Composer?

curiositech (a GitHub organization) maintains it in curiositech/some_claude_skills, which has 243 GitHub stars. The repository holds 109 skills in this directory. The repository was last updated on September 6, 2026.

Source: curiositech/some_claude_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.