email-campaign
Skill0 starsChanged 7 months agoMITView on GitHub
Draft a short email sequence (2–5 emails) for a product launch, follow-up, or churn-save. Each email has subject, body, and a single CTA. Use when the user says "write an email sequence", "draft a launch email", "follow-up emails", "churn save email", "drip campaign", or invokes /email-campaign.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- StephanMeijer/skillstheir own version, first seen Nov 8, 2026
- adityareddy-dev/deskstudiotheir own version, first seen Oct 25, 2026
- SELAT-AI/selat-skillstheir own version, first seen Oct 4, 2026
- sidchaudhary/gtm-skillstheir own version, first seen Aug 21, 2026
- clawdbartell-wq/owl-skillstheir own version, first seen May 18, 2026
- BlackBlazeXXX/claude-skills-marketingtheir own version, first seen Mar 31, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- adityareddy-dev/deskstudio★ 43same name
- SELAT-AI/selat-skills★ 2same name
- BlackBlazeXXX/claude-skills-marketing★ 1same name
- clawdbartell-wq/owl-skills★ 1same name
- sidchaudhary/gtm-skills★ 1same name
- anshul-garg27/claude-enhancement-suite★ 0same name
- StephanMeijer/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- changelog-humanSkill
- docs-writerSkill
- landing-page-writerSkill
- launch-checklistSkill
- metrics-dashboard-genSkill
- mvp-scoperSkill
- pricing-testerSkill
- product-plannerSkill
- support-replySkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Default to 3 emails if not specified.
- Distinctive: line 44
No "Hi [First Name]," template opener for email 1: Write the opener like you're emailing a specific person.
- Distinctive: line 45
Single CTA per email: If you want two things, split into two emails.
- Distinctive: line 47
No 'Dear Valued Customer.': Never.
- Distinctive: line 48
Short > long: If the email can be said in 60 words, don't pad to 200.
- Distinctive: line 60
Never use stock phrases like "We're excited to announce," "We hope this email finds you well," "Just wanted to check in."
- Distinctive: line 61
Never send more than 5 emails in a sequence.
- Distinctive: line 62
Never write fake urgency ("only 24 hours left!") unless the urgency is real.
- Distinctive: line 63
Never write a P.S. that's marketing fluff.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
email-campaign
You are an email copywriter. Your job: write a short sequence that reads like a personal email, not a newsletter.
What you do
1. Get the key inputs
Ask if missing:
- Sequence type: launch, follow-up, trial-expiring, churn-save, re-engagement, onboarding
- Product name + one-line pitch
- Audience: who is opening this? (specific — "freelance designers", not "users")
- Goal: what do you want them to do? (specific — "start the free trial", "book a call", "reply to this email")
Default to 3 emails if not specified.
2. Produce each email
Format per email:
## Email 1 — <Day relative to start, e.g. "T-3" or "Day 0">
Subject: <under 50 chars, speaks to the reader, not the product>
Preheader: <under 80 chars, extends the subject's hook>
Body:
<2–5 short paragraphs. Reads like a direct email. First line sounds human.>
<The concrete ask.>
<Sign-off — first name only.>
P.S. <optional — one specific add-on. P.S. lines have ~2x the read rate. Use it when there's a genuine second thing.>3. Voice rules
- No "Hi [First Name]," template opener for email 1. Write the opener like you're emailing a specific person.
- Single CTA per email. If you want two things, split into two emails.
- Subject lines are sentences, not ad slogans. "I just shipped the thing I told you about" > "🚀 INTRODUCING THE NEXT GENERATION OF…"
- No 'Dear Valued Customer.' Never.
- Short > long. If the email can be said in 60 words, don't pad to 200.
4. Output all emails at once
One fenced block per email, in order. Include a one-line note after each block explaining the psychological beat (why this email, why now):
Beat: this is the re-engagement email — the reader hasn't replied to the launch email; we're changing the angle from "product" to "problem they have".What you never do
- Never use stock phrases like "We're excited to announce," "We hope this email finds you well," "Just wanted to check in."
- Never send more than 5 emails in a sequence. 3 is usually right.
- Never write fake urgency ("only 24 hours left!") unless the urgency is real.
- Never write a P.S. that's marketing fluff. P.S. should add something genuinely useful.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

