New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Email Drafting

by seb1n in seb1n/awesome-ai-agent-skills

Draft a professional, audience-aware email or reply with calibrated tone and a clear call to action.

MITAuto-check passedSales & Support

Install Email Drafting

skills CLI
$ npx skills add seb1n/awesome-ai-agent-skills --skill email-drafting -a claude-code

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

GitHub CLI
$ gh skill install seb1n/awesome-ai-agent-skills email-drafting --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/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/communication/email-drafting .claude/skills/email-drafting && 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-drafting
GitHub stars
206
Token cost
~2k tokens
SKILL.md length
717 words
Files
1
Skills in repo
92
Repo updated
First seen
Licence
MIT

At a glance

Draft a professional, audience-aware email or reply with calibrated tone and a clear call to action.

  • Works in 6 steps: Identify the email type and objective.… → Profile the recipient and calibrate… → Compose the subject line. Write a… → …
  • The user needs one message
  • SKILL.md covers Workflow, Usage, Examples and Best Practices, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Email Drafting is an agent skill from seb1n/awesome-ai-agent-skills. Draft a professional, audience-aware email or reply with calibrated tone and a clear call to action. Use when the user needs one message, response, follow-up, support note, or meeting request; use sales-email-sequences for a coordinated multi-touch outbound campaign.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Email marketing and Customer support. The repository describes itself as: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.

When your agent uses it

  • The user needs one message
  • Meeting request
  • Use sales-email-sequences for a coordinated multi-touch outbound campaign

Example prompts

  • “/email-drafting”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Identify the email type and objective. Determine the category of the email — cold outreach, follow-up, customer support reply, internal…
  2. Profile the recipient and calibrate tone. Gather details about the recipient: name, title, company, relationship history, and any previous…
  3. Compose the subject line. Write a subject line that is specific, concise (under 60 characters), and action-oriented. Avoid generic phrases…
  4. Draft the email body with clear structure. Follow a proven structure: opening hook (1-2 sentences establishing relevance), body (2-3 short…
  5. Add signature and formatting polish. Include an appropriate sign-off ("Best regards," for formal, "Thanks," for casual, "Cheers," for…
  6. Review against checklist and deliver. Verify the email meets these criteria: subject line is compelling, tone matches the audience, the…

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    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 Drafting loads about 2k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 717 words of instructions outside code blocks.

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

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 seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 717 words, ~2,012 tokens.

Download SKILL.mdSave it as .claude/skills/email-drafting/SKILL.md (or your agent's skills folder).
name
email-drafting
description
Draft a professional, audience-aware email or reply with calibrated tone and a clear call to action. Use when the user needs one message, response, follow-up, support note, or meeting request; use sales-email-sequences for a coordinated multi-touch outbound campaign.
license
MIT
metadata.author
awesome-ai-agent-skills
metadata.version
1.0.0

Email Drafting

This skill enables an AI agent to compose professional, context-appropriate emails across a variety of scenarios. The agent analyzes the purpose, audience, and tone requirements, then produces a complete email with subject line, body, and call to action. It supports common email types including cold outreach, follow-up sequences, customer support responses, internal status updates, and meeting requests.

Workflow

  1. Identify the email type and objective. Determine the category of the email — cold outreach, follow-up, customer support reply, internal update, or meeting request. Each type has different structural expectations. A cold outreach email prioritizes a compelling hook, while a support response leads with empathy and resolution. Clarify the single desired outcome: a scheduled call, an acknowledged resolution, an informed team, etc.

  2. Profile the recipient and calibrate tone. Gather details about the recipient: name, title, company, relationship history, and any previous interactions. Use this context to select the appropriate tone — formal for executive outreach, conversational for peer updates, empathetic for complaint responses, or urgent when time-sensitive action is required. Apply personalization tokens such as {{first_name}}, {{company}}, and {{pain_point}} when drafting templates.

  3. Compose the subject line. Write a subject line that is specific, concise (under 60 characters), and action-oriented. Avoid generic phrases like "Quick question" or "Touching base." Instead, reference a concrete benefit or context point, e.g., "Cut your onboarding time by 40% — here's how" or "Follow-up: action items from Thursday's standup."

  4. Draft the email body with clear structure. Follow a proven structure: opening hook (1-2 sentences establishing relevance), body (2-3 short paragraphs delivering the core message with supporting evidence or context), and closing with a single, unambiguous call to action. Keep paragraphs under 3 sentences. Use bullet points for lists of items or benefits. Avoid walls of text.

  5. Add signature and formatting polish. Include an appropriate sign-off ("Best regards," for formal, "Thanks," for casual, "Cheers," for friendly) followed by the sender's name, title, and contact info. Review the draft for grammar, spelling, and readability. Ensure the email can be scanned in under 30 seconds.

  6. Review against checklist and deliver. Verify the email meets these criteria: subject line is compelling, tone matches the audience, the CTA is clear and singular, the email is under 200 words for outreach or under 300 words for detailed responses, and no placeholder tokens remain unresolved. Output the final email in a ready-to-send format.

Usage

Provide the agent with the email type, recipient details, purpose, key points to include, and desired tone. The agent will return a complete email with subject line, body, and signature.

Prompt format:

Draft a [type] email to [recipient details].
Purpose: [what you want to achieve]
Key points: [information to include]
Tone: [formal / casual / empathetic / urgent]

Examples

Show full SKILL.md (290 more words)Show less
Example 1: Cold Outreach Email

Input:

Draft a cold outreach email to Sarah Chen, VP of Engineering at Cloudstream Inc.
Purpose: Introduce our API monitoring platform and book a 15-minute demo.
Key points: Their engineering blog mentions scaling challenges; our tool reduces incident response time by 60%.
Tone: Professional but conversational.

Output:

Subject: Reducing incident response time at Cloudstream

Hi Sarah,

I read your recent post on scaling Cloudstream's microservices architecture — the challenges you described around observability gaps resonated with several of our customers who faced similar growing pains.

We built Watchdog specifically for engineering teams navigating that transition. Our API monitoring platform provides real-time anomaly detection and automated root-cause analysis. Teams using Watchdog have cut their mean incident response time by 60%, which typically saves 10+ engineering hours per week.

Would you be open to a 15-minute walkthrough? I can show you how Watchdog would map onto Cloudstream's stack. Here's a link to grab a time that works: [calendar link]

Best regards,
Alex Rivera
Account Executive, Watchdog
alex@watchdog.io | (555) 234-5678
Example 2: Customer Support Response to a Complaint

Input:

Draft a customer support response to Marcus Webb who is upset about being double-charged for his subscription renewal.
Purpose: Acknowledge the error, confirm the refund, and retain the customer.
Key points: Refund of $49.99 will appear within 3-5 business days; root cause was a billing system migration.
Tone: Empathetic and reassuring.

Output:

Subject: Your refund for the duplicate charge has been processed

Hi Marcus,

I'm truly sorry about the duplicate charge on your account — I completely understand how frustrating that must be, and I want to assure you that we've already taken care of it.

We've processed a full refund of $49.99 to your original payment method. You should see the credit reflected within 3-5 business days. The duplicate charge was caused by a one-time issue during our billing system migration, and our engineering team has deployed a fix to ensure this doesn't happen again.

Your subscription remains fully active and unaffected. As a thank-you for your patience, I've also applied a 15% discount to your next renewal.

If you have any other questions or concerns, please don't hesitate to reply to this email — I'm happy to help.

Warm regards,
Jamie Torres
Customer Support, BrightSaaS

Best Practices

  • One call to action per email. Multiple CTAs dilute urgency and reduce response rates. Choose the single most important next step and make it unmissable.
  • Front-load the most important information. Recipients often scan only the first two sentences. Lead with relevance — why should they care right now?
  • Match paragraph length to formality. Formal emails can tolerate slightly longer paragraphs; casual outreach should use 1-2 sentence paragraphs with generous whitespace.
  • Personalize beyond the name. Reference a recent achievement, shared connection, or specific pain point. Generic personalization ("I see you work at Acme") feels robotic.
  • Use time-bounded CTAs when appropriate. "Would Thursday or Friday afternoon work?" outperforms "Let me know when you're free" because it reduces decision friction.
  • Proofread for tone as well as grammar. Read the email aloud to catch phrases that sound condescending, pushy, or overly casual for the context.

Edge Cases

  • Unknown recipient name. When the recipient's name is unavailable, use a role-based greeting ("Hi there" or "Hello, Marketing Team") rather than "To whom it may concern," which reads as impersonal.
  • Emotionally charged complaints. For angry or frustrated customers, avoid defensive language. Lead with validation ("I understand why that's frustrating") before explaining the resolution. Never blame the customer.
  • Multi-recipient emails. When addressing a group, ensure the CTA specifies who should take action. Diffusion of responsibility leads to no one responding.
  • Follow-up after no response. Reference the original email briefly and add new value (a relevant case study, a deadline, or a simplified ask) rather than simply bumping the thread.
  • Legal or compliance-sensitive content. Flag emails that may involve contracts, NDAs, financial disclosures, or regulatory language for human review before sending.

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

Files

Just SKILL.md in communication/email-drafting of seb1n/awesome-ai-agent-skills.

Open the folder on GitHubat commit 75865a5

Compare with similar skills

Email Drafting 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 Drafting compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Drafting this skillseb1n/awesome-ai-agent-skills206—~2kAutomated safety check: PassMIT
Outreach Specialistognjengt/founder-skills406—~3.2kAutomated safety check: PassMIT
Money Outreachiamzifei/show-me-the-money1k—~3kAutomated safety check: PassCustom licence
Send Cold EmailOthmane-Khadri/YALC-the-GTM-operating-system317—~515Automated safety check: PassMIT
Memstack Product Feedback Analyzercwinvestments/memstack423—~2.7kAutomated safety check: PassProprietary
Outbound Email Strategymanojbajaj95/claude-gtm-plugin1041 repos~2.7kAutomated safety check: PassMIT

Similar skills

  • Outreach Specialist

    ognjengt/founder-skills

    Crafts high-converting outreach messages and email sequences for cold outreach, LinkedIn DMs, and follow-ups.

    406 GitHub stars~3.2k tokensUpdated 4 mo ago
    Sales & SupportAuto-check passed

  • Money Outreach

    iamzifei/show-me-the-money

    Automated outreach and sales pipeline — cold email sequences, partnership outreach, lead generation, and prospect management.

    1k GitHub stars~3k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

  • Send Cold Email

    Othmane-Khadri/YALC-the-GTM-operating-system

    Send a cold email campaign or single message via the configured email provider (Instantly by default), optionally pre-drafting the sequence.

    317 GitHub stars~515 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

  • Memstack Product Feedback Analyzer

    cwinvestments/memstack

    A skill your agent uses when the user says 'analyze feedback', 'feedback analysis', 'what are customers asking for', or has support tickets, reviews, or survey data to categorize, score, and…

    423 GitHub stars~2.7k tokensUpdated 11 days ago
    Sales & SupportAuto-check passed

  • Outbound Email Strategy

    manojbajaj95/claude-gtm-plugin

    Comprehensive outbound email strategy skill for cold outreach, email sequences, and multi-channel campaigns.

    104 GitHub starsUsed in 1 repo~2.7k tokens
    Sales & SupportAuto-check passed

  • Lifecycle Email

    aiskillstore/marketplace

    Draft a lifecycle email as a welcome, delivery of the bargain, then nurture tied to the pain they showed.

    430 GitHub stars~612 tokensUpdated today
    Sales & SupportAuto-check passed

More from seb1n/awesome-ai-agent-skills

All 92 skills in this repo

  • Agent Red Teaming

    seb1n/awesome-ai-agent-skills

    Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.

    206 GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Eu AI Act Readiness

    seb1n/awesome-ai-agent-skills

    Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…

    206 GitHub stars~3.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Human In The Loop

    seb1n/awesome-ai-agent-skills

    Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.

    206 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check passed

  • MCP Server Building

    seb1n/awesome-ai-agent-skills

    Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.

    206 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check passed

  • PDF Processing

    seb1n/awesome-ai-agent-skills

    Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.

    206 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Skill Supply Chain Audit

    seb1n/awesome-ai-agent-skills

    Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.

    206 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Email Drafting

What does Email Drafting do?

Draft a professional, audience-aware email or reply with calibrated tone and a clear call to action. Email Drafting is an agent skill from seb1n/awesome-ai-agent-skills. Draft a professional, audience-aware email or reply with calibrated tone and a clear call to action.

When should I use Email Drafting?

Email Drafting fits situations like: the user needs one message; meeting request; use sales-email-sequences for a coordinated multi-touch outbound campaign.

How do I install Email Drafting in Claude Code?

Run `npx skills add seb1n/awesome-ai-agent-skills --skill email-drafting -a claude-code`. Or copy the skill folder (communication/email-drafting in seb1n/awesome-ai-agent-skills) into .claude/skills/email-drafting in your project. Claude Code loads it when a task matches its description.

How do I install Email Drafting in Codex?

Run `npx skills add seb1n/awesome-ai-agent-skills --skill email-drafting -a codex`. Or copy the skill folder (communication/email-drafting in seb1n/awesome-ai-agent-skills) into .agents/skills/email-drafting in your project. Codex loads it when a task matches its description.

Can I use Email Drafting 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 seb1n/awesome-ai-agent-skills --skill email-drafting -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-drafting, .gemini/skills/email-drafting, .github/skills/email-drafting and .opencode/skills/email-drafting in your project.

What does Email Drafting need to run?

SKILL.md names no scripts, command-line tools or credentials: Email Drafting is instructions for the agent only.

Does Email Drafting 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 Drafting 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 Drafting use?

Email Drafting is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Email Drafting use?

About 2k tokens (SKILL.md is roughly 8k 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 Drafting?

Skills that share tags, products or a category with Email Drafting: Outreach Specialist (ognjengt/founder-skills, 406 stars), Money Outreach (iamzifei/show-me-the-money, 1k stars), Send Cold Email (Othmane-Khadri/YALC-the-GTM-operating-system, 317 stars) and Memstack Product Feedback Analyzer (cwinvestments/memstack, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Drafting?

seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 92 skills in this directory. The repository was last updated on August 9, 2026.

Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.