Email Drafter

OrganizationPopular

genspark-ai

email-drafter

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

Overview

Publisher	genspark-ai
Repository	`genoffice`
Skill name	`email-drafter`
Stars	11.3K
Forks	1.6K
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by genspark-ai on GitHub. Read the source before you install it.

Installation

Install the Email Drafter AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/genspark-ai/genoffice/tree/main/skills/recommended/email-drafter
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/genspark-ai/genoffice.git /tmp/genoffice
mkdir -p .claude/skills
cp -r /tmp/genoffice/skills/recommended/email-drafter .claude/skills/email-drafter

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Email Drafter in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Email Drafter on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Email Drafter is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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).
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.
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.
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.
Deliver the result as a Markdown document with the tools available here (or directly in the reply if the user prefers), titled " E-mail Drafts".
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 ?" 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.

Frequently asked questions

What does the Email Drafter AI skill do?

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

Why use Email Drafter on TypingMind?

Because you install it once and use it with any model. Email Drafter is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Email Drafter in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/genspark-ai/genoffice/tree/main/skills/recommended/email-drafter. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Email Drafter?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Email Drafter?

As many as you like. As long as a model supports skills, you can use Email Drafter with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Email Drafter AI skill free?

Yes. It is published on GitHub by genspark-ai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Executing Plans

obra

CommunityPopular

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Context And Decisions

affaan-m

CommunityPopular

Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require…

Docs Governance

Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Workflow

Document structure

English conventions

Rules

Output

Frequently asked questions

Related AI Skills

Set up your own AI workspace now