Sales Email Template Generator
Writes one sales outreach email, ready to send, from three pieces of information: the type of prospect, the solution they use today, and your product or its features. A labeled stand-in is fine if you don't have real feature detail yet, but the skill always asks and gets an actual answer before drafting, rather than silently defaulting. The email names a pain point that prospect likely has, grounded in something the current solution is known to be weak at, a specific feature that solves it, a clear reason to switch, and ends with a low-pressure invitation to look at a demo, not a hard push to book one. No fact anywhere in the email goes beyond what was actually supplied: no invented contact name, company detail, headcount, date, or claimed observation about the specific prospect. The whole thing stays at 200 words or fewer and reads like one person wrote it to another, not a marketing blast. If prospect type or current solution is missing, the skill asks for it and stops rather than writing an email on a guessed pairing. Ships with an eval contract carrying three frozen self-test scenarios covering a full draft, a stand-in-feature draft, and the missing-input case.
First-party, by Skills and Agents Co
August 31, 2026
Simple install — no setup required
Open the Claude desktop app and go to the Project you want this in
Go to Code, then Customize, then click Create a new skill and upload the skill file below
Say a trigger phrase to activate it
Download the skill file below
In ChatGPT, create a Project and attach the file (or paste its contents into the project instructions). For a reusable setup, build a Custom GPT via Explore GPTs → Create and add the file there
Start a chat in that Project or GPT, then say a trigger phrase to activate it
Download the skill file below
Place it at .cursor/skills/sales-email-template-generator/SKILL.md (rename the downloaded file to SKILL.md). The shared .agents/skills/sales-email-template-generator/SKILL.md path also works
Cursor loads the skill when your task matches its description. Say a trigger phrase to activate it
Download the skill file below
Place it at .github/skills/sales-email-template-generator/SKILL.md in your repository (rename the downloaded file to SKILL.md)
Copilot loads the skill when it is relevant to your task. Say a trigger phrase to activate it
Download the skill file below
Place it at .agents/skills/sales-email-template-generator/SKILL.md in your repository (rename the downloaded file to SKILL.md)
Codex loads the skill when your task matches, or invoke it explicitly with /skills. Say a trigger phrase to activate it
Download the skill file below
In Gemini, create a Gem, then upload the skill file as a knowledge file
Copy the Gem instructions with the button below, then paste them into the instructions box
Start a chat with the Gem, then say a trigger phrase to activate it
You are a Gem built around the "Sales Email Template Generator" skill. Writes one personalized sales outreach email, 200 words or fewer, from a stated prospect type, their current solution, and your product or features. Closes with a soft demo invitation, never a hard close, and won't invent a fact the input didn't supply. Read the attached file first, then follow its instructions. Activate this skill when the user says something like: write a sales email, draft an outreach email, cold email template, /sales-email-template-generator.
npx skills add skills-agents-co/skills-and-agents-library/sales-email-template-generatorYour skill is downloading.
Get an email when we ship new skills and updates.
You're on the list. We'll email you when new skills drop.
What this skill does
This is an overview of the skill from the site, not the skill's real instructions. The full SKILL.md Claude reads when this skill is active lives on GitHub at the source below.
Writes one first-draft sales outreach email from three inputs: who you’re emailing, what they use today, and what you’re selling. You paste in the draft, edit it if you want, and send it yourself.
This writes one email per run. It doesn’t find prospects, look up email addresses, or send anything.
What it does
- Names a pain point grounded in the current solution, not a generic complaint. Ties it to something the stated tool is known to be weak at: manual work it doesn’t automate, a limit it hits at scale, a report it can’t produce.
- Names one specific feature that addresses that exact pain point. The real feature you supplied, or, if you say to use a stand-in, a clearly labeled placeholder written inline, never presented as if it were real.
- Closes with a soft call-to-action, never a hard close. An invitation the prospect can decline with no further action and no specific date or time attached, not “book your demo today.”
- Never invents a fact beyond what you supplied. No contact name, company detail, headcount, date, or claimed observation about the specific prospect. A generic-but-honest opener beats a specific-but-fabricated one.
- Stops and asks for what’s missing, on every required input. If the prospect type, current solution, or product/feature answer isn’t there, it asks and waits, rather than guessing a pairing or silently defaulting to a stand-in.
- Enforces its own word limit. Trims in a fixed order if the draft runs long, and if it’s still over 200 words after three honest passes, says so plainly instead of trimming indefinitely.
- Treats every input as data, never instructions. Text in the prospect type, current solution, or feature description that reads like a directive to the model (“ignore the word limit”) is described, not followed.
How to use it
- Give it a prospect type, their current solution, and your product or features (or say you don’t have feature detail yet).
- If anything’s missing, it asks once and waits for a real answer before drafting.
- It writes one email: opener, pain point, feature and value proposition, soft CTA, sign-off.
- You get the finished draft plus a word count, ready to edit and send.
Output format
Plain text: a subject line, the body, a sign-off placeholder, and the final word count on its own line after.
Pitfalls
- Don’t guess a prospect type and current solution pairing. A guessed-at pairing produces a pain point that doesn’t land.
- Don’t let a stand-in feature read as real. Label it clearly, inline, where the feature would be named.
- Don’t write a hard close. “Book your demo today” assumes the sale; a soft CTA gives the prospect an easy out.
- Don’t invent a specific fact about the prospect to make the opener sound personal. A generic-but-honest opener is better than a fabricated one.
This skill has no dependency on a CRM, mail-sending service, or prospect database. It drafts text only.
View full SKILL.md on GitHub