AGENT SKILLBY GITHUB
Email drafter
AT A GLANCE
Email drafter is an email agent skill from github. Draft and review professional emails that match your personal writing style. The github/awesome-copilot repository on GitHub has 38.2K stars and the MIT license. To add it, run npx skills add github/awesome-copilot --skill email-drafter
- SOURCE REPOSITORY
- github/awesome-copilot (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- CATEGORIES
- SKILL.MD SIZE
- 4.1 KB96 LINES
QUICK ANSWER
- WHAT IT IS01
- Draft and review professional emails that match your personal writing style. Analyzes your sent emails for tone, greeting, structure, and sign-off patterns via WorkIQ, then generates context-aware drafts for any. It brings GitHub's specific operating context into email marketing, so the agent is guided by a sharper source than a generic prompt.
- INPUTS02
- Context for email marketing: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result for email marketing: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add github/awesome-copilot --skill email-drafterREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 9
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:
- Recipient(s) — who is the email for?
- Purpose — what is the email about? (proposal, follow-up, technical guidance, introduction, status update, etc.)
- Key points — what needs to be communicated?
- 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:
- Pull 3–5 recent sent emails from the user to the same recipient or similar recipients
- 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
- 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#
- Present the draft for review with a brief note on the tone/style applied
- Apply edits as the user requests — iterate until satisfied
- 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
FAQ
07 QUESTIONS
01What is the Email drafter agent skill?
Draft and review professional emails that match your personal writing style. Analyzes your sent emails for tone, greeting, structure, and sign-off patterns via WorkIQ, then generates context-aware drafts for any. It is listed under email in the 100xLab agent skills directory.
02How do I install Email drafter in Cursor, Claude Code, or Codex?
Run npx skills add github/awesome-copilot --skill email-drafter in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Email drafter, not every skill in the repository.
03What does the Email drafter SKILL.md cover?
The SKILL.md includes sections on When to Use, Workflow, Step 1 — Gather Context, Step 2 — Analyze Tone, Step 3 — Draft the Email and Step 4 — Output. Read the full text on this page or in plain markdown at /resources/agent-skills/github-awesome-copilot--email-drafter--1m4qja/raw.
04Which agents can use Email drafter?
Email drafter installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Email drafter under?
The github/awesome-copilot repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is Email drafter free to use?
Reading, copying and installing Email drafter costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of Email drafter?
Email drafter comes from https://github.com/github/awesome-copilot, which has 38.2K GitHub stars. The SKILL.md is at https://github.com/github/awesome-copilot/blob/HEAD/skills/email-drafter/SKILL.md. The author is github.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Email drafter was written by its original authors and is published in github/awesome-copilot (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.