New to Claude Skills? Learn how to install them →

github on GitHub

Email Drafter

OfficialFree

Effortlessly draft professional emails in your style.

by github37.7k stars on github/awesome-copilot
4 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What Email Drafter does

The Email Drafter skill is designed to assist users in creating professional emails that reflect their personal writing style and tone. By utilizing WorkIQ, this skill analyzes your previous email correspondence to generate drafts that are contextually aware and tailored to the recipient. This means that whether you're drafting a follow-up, a proposal, or a simple reply, the Email Drafter can help you maintain consistency in your communication while saving you time.

The drafting process begins by gathering essential context about the email, including the recipient, the purpose, and key points to communicate. If you provide this information upfront, the skill can generate a draft directly. If not, it will ask clarifying questions to ensure that the final output meets your needs. Once the context is set, the skill analyzes your prior emails to identify patterns in tone, greeting, structure, and sign-off, which are then applied to the draft.

After the draft is created, it is presented for your review, allowing you to make any necessary edits. The skill iterates on your feedback until you are satisfied with the final version, which is then saved as a markdown file in a designated folder structure. This organization helps keep your drafts accessible and easy to manage.

The Email Drafter is particularly useful for professionals who frequently communicate via email and want to ensure their messages are polished and consistent. It is ideal for those who may struggle with wording or structuring their emails effectively, providing a straightforward solution to enhance their written communication.

When to use it

Use this skill when you need to draft, reply to, or follow up on emails, especially when you want to maintain a consistent tone and style.

When not to use it

This skill may not be suitable for casual or informal communication where a personalized touch is more appropriate, or if you prefer to write emails entirely from scratch without assistance.

What you can build with it

Drafting a Proposal Email

Use the skill to create a professional proposal email for a new initiative, ensuring it aligns with your usual tone.

Following Up on a Customer Inquiry

Quickly generate a follow-up email to a customer regarding their questions, maintaining a friendly yet professional tone.

Replying to a Colleague

Draft a concise reply to a colleague's email, incorporating your established greeting and sign-off patterns.

How to install Email Drafter

View source

1. Install with the skills CLI

npx skills add github/awesome-copilot/email-drafter --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by github

Email Drafter

Draft professional emails that match your established writing style and tone. Uses WorkIQ to analyze your sent emails and prior correspondence with recipients, then produces context-aware drafts you can review and refine.

When to Use

  • "Draft an email to [person] about [topic]"
  • "Write a follow-up email to [customer] regarding [project]"
  • "Reply to [person]'s email about [subject]"
  • "Compose a proposal email for [initiative]"
  • "Analyze my email tone with [recipient]"

Workflow

Step 1 — Gather Context

Before drafting, collect:

  1. Recipient(s) — who is the email for?
  2. Purpose — what is the email about? (proposal, follow-up, technical guidance, introduction, status update, etc.)
  3. Key points — what needs to be communicated?
  4. Relationship context — use WorkIQ to check prior email history with the recipient if available

If the user provides all of these upfront, proceed directly. Otherwise, ask clarifying questions (max 3).

Step 2 — Analyze Tone

When drafting for a recipient, use WorkIQ to understand the user's established communication patterns:

  1. Pull 3–5 recent sent emails from the user to the same recipient or similar recipients
  2. Identify patterns:
    • Greeting style — formal ("Dear"), standard ("Hello"), casual ("Hi"), or direct (no greeting)
    • Structure — short paragraphs vs. bullet lists vs. numbered steps
    • Sign-off — what closing and name format the user typically uses
    • Formality level — professional, friendly-professional, casual
    • Language — which language the user writes in with this recipient
  3. Apply those patterns to the draft

If WorkIQ is unavailable or no prior emails exist, use sensible professional defaults and note that the tone was inferred.

Step 3 — Draft the Email

Apply the discovered (or default) style rules:

Greeting:

  • Match whatever greeting style was found in Step 2
  • Default: "Hello [FirstName]," for external, "Hi [FirstName]," for internal
  • For multiple recipients: "Hello [Name1], [Name2],"

Tone:

  • Direct and concise — no filler language
  • Friendly but professional
  • Get to the point quickly
  • Offer help proactively where appropriate ("Happy to discuss further", "Let me know if you need anything")

Structure:

  • Short emails (1–2 points): simple paragraphs, no bullets needed
  • Longer emails (proposals, multi-point updates): use bullet points or numbered lists
  • Include context from prior conversations when relevant ("Following our recent conversation about...")

Sign-off:

  • Match the user's established sign-off pattern from Step 2
  • Default: "Best regards," followed by the user's first name on the next line

Language:

  • Default to English unless the user specifies otherwise
  • Match the recipient's language if prior correspondence was in another language

Step 4 — Output

  1. Present the draft for review with a brief note on the tone/style applied
  2. Apply edits as the user requests — iterate until satisfied
  3. Save the final draft to outputs/<year>/<month>/ with a descriptive filename (e.g., 2026-03-26-email-acme-followup.md)

Important Rules

  • Never send emails — only draft them as files for the user to review and send manually
  • Always check WorkIQ for prior context with the recipient when available
  • If the user says "draft email" or "write email", activate this skill automatically
  • Save drafts using the outputs/<year>/<month>/ folder convention
  • Respect privacy: do not include sensitive information from unrelated email threads

Example Prompts

  • "Draft an email to Sarah about the project timeline"
  • "Write a follow-up to the customer about their migration questions"
  • "Compose a proposal email for the new training initiative"
  • "Reply to John's email — agree with his approach but suggest we add monitoring"
  • "Analyze my email tone with the Acme team"

Requirements

  • WorkIQ MCP tool is recommended for tone analysis and recipient context (Microsoft 365 / Outlook)
  • Without WorkIQ, the skill still works but uses professional defaults instead of personalized tone matching
  • Output is saved as markdown files in the workspace

Frequently asked questions about Email Drafter

Similar skills