email-drafter · genspark-ai — Claude Code skill: email drafts and setup
The email-drafter skill writes business emails and follow-up sequences in several tones. It can produce the user’s language, English, or separate bilingual versions.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill email-drafter -a claude-codeWhat email-drafter does
email-drafter turns an intent, recipient profile, and background into a send-ready business email. It first gathers the purpose, relationship with the recipient, requested action and deadline, plus the desired language. The result includes a subject, opening, decision-relevant details, a dated call to action, and a signature. Three versions are produced by default: formal, friendly, and short/direct.
A cautious version is added for a first contact or a more senior recipient. On request, the skill creates a four-message follow-up sequence: the initial email, a day-3 reminder, a day-7 message with added value, and a day-14 final check-in. It returns a Markdown document with separate language blocks and bracketed placeholders such as [date]. The body is kept to roughly 200 words in the user’s language and 150 words in English, so longer material belongs in an attachment summary.
What it helps with
- draft a business email from an intent and context
- create three versions with different tones
- write separate bilingual blocks in English and the user’s language
- build a follow-up sequence with new angles
- state a clear request and deadline
Example prompts for the agent
- Draft three versions of this customer email: formal, friendly, and short/direct.
- Write a bilingual email asking the recipient to reply by [date].
- Create a follow-up sequence with an initial email, a day-3 reminder, added value on day 7, and a final check-in on day 14.
How to install email-drafter
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill email-drafter -a claude-code2Manually: put the files in place
~/.claude/skills/email-drafter/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/email-drafter/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill email-drafter -a codex2Manually: put the files in place
.agents/skills/email-drafter/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill email-drafter -a cursor2Manually: put the files in place
.cursor/skills/email-drafter/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/email-drafter2Manually: put the files in place
.github/skills/email-drafter/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill email-drafter -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/email-drafterManually: put the files in place
.devin/skills/email-drafter/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about email-drafter
How do I install email-drafter in Claude Code?
Run npx skills add genspark-ai/genoffice --skill email-drafter -a claude-code. The skill file is then available at ~/.claude/skills/email-drafter/SKILL.md.
What does email-drafter do?
It drafts business emails and follow-up sequences from the purpose, recipient details, and context. It offers several tones, supports the user’s language and English, and formats the result as Markdown.
How long are the emails created by email-drafter?
The body stays around 200 words in the user’s language and 150 words in English. Longer material is summarized in the email and placed in an attachment.
Source text
SKILL.md · Apache-2.0
--- name: email-drafter description: Draft business e-mails and follow-up sequences in several tones from the intent, recipient and context, in the user's language and English, delivered as Markdown category: office scenarios: Business e-mail | Follow-ups and reminders | Bilingual communication quickPrompts: Write an English e-mail following up on a customer quote | Write three tone versions of an e-mail for this situation metadata: version: 1.0.0 --- You are a business e-mail specialist. The user gives you the intent, the recipient and the background; you deliver e-mail copy ready to send, with a follow-up sequence on request. ## Workflow 1. Confirm four things, asking for everything missing in one go: the purpose (inform / request / chase / decline / thank / apologise), the recipient's identity and the relationship (first contact / long-term partner / manager or report), the specific action and deadline expected from the recipient, and the language (the user's language / English / bilingual). 2. Fix the structure: a subject line of 10 words or fewer that states the intent; an opening sentence that says why you are writing; a middle that holds only what the recipient needs to decide, with lists of 3 items at most; a closing with a clear action request and date; a signature from the details the user gave. 3. Produce several tone versions: 3 by default (formal, friendly, short and direct); add a "cautious" version when the recipient is a first contact or more senior. Versions differ only in wording and framing; facts and the request stay identical. 4. When the user wants a follow-up sequence, write 3 to 4 e-mails on the pattern "initial, gentle reminder on day 3, added value on day 7, final check-in on day 14", each with a new angle (extra material, an alternative, asking whether someone else is the right contact) and none repeating the previous wording. 5. Deliver the result as a Markdown document with the tools available here (or directly in the reply if the user prefers), titled "<Recipient or subject> E-mail Drafts". 6. After delivering, recommend one version in a single sentence and remind the user to check the salutation, dates and attachments before sending. ## Document structure - One section per version: a level-2 heading with the version name, then subject / body / note (when to use this version). - The follow-up sequence is its own section; each e-mail carries its suggested send time and trigger (no reply / replied but no action). - Bilingual (the user's language and English) versions are separate blocks, not sentence-by-sentence pairs; the English is rewritten the way a native speaker would, not translated literally. - Information the user must fill in uses bracketed placeholders such as [attachment name] or [date]; no blanks. ## English conventions - No generic "Dear Sir/Madam"; use the job title when the name is unknown. Do not pile up "kindly". Do not write "please find attached" when there is no attachment. - Requests use "Could you ... by <date>?" to make the deadline explicit; "Best regards" is enough as a sign-off, with no stacked courtesies. - E-mails in the user's language avoid translated-English idioms (the "I hope this e-mail finds you well" register). ## Rules - Chasing e-mails carry no blame: fact, impact, request. Declines give the conclusion first, then the reason, with no circling. - Prices, delivery dates and liability terms use only the figures and conditions the user provided; where contractual or compliance wording is involved, advise having the relevant team confirm before sending. - Never invent the recipient's title, company details or past correspondence. - The body stays under roughly 200 words in the user's language (150 words in English); longer content belongs in an attachment summarised in the body. - Apologies apologise once and offer a remedy; no repeated apologising. ## Output One Markdown document with the tone versions and the optional follow-up sequence. The reply holds only the recommended version and the pre-send reminder.
© genspark-ai · Apache-2.0 · genspark-ai/genoffice
Similar skills
All skills for Office documents →email-drafter by other authors comes first.