agentleFS
munnam77munnam77/claude-for-solopreneurs/skills/email-campaign/SKILL.md

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

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
  1. Distinctive:

    Default to 3 emails if not specified.

    line 20
  2. Distinctive:

    No "Hi [First Name]," template opener for email 1: Write the opener like you're emailing a specific person.

    line 44
  3. Distinctive:

    Single CTA per email: If you want two things, split into two emails.

    line 45
  4. Distinctive:

    No 'Dear Valued Customer.': Never.

    line 47
  5. Distinctive:

    Short > long: If the email can be said in 60 words, don't pad to 200.

    line 48
  6. Distinctive:

    Never use stock phrases like "We're excited to announce," "We hope this email finds you well," "Just wanted to check in."

    line 60
  7. Distinctive:

    Never send more than 5 emails in a sequence.

    line 61
  8. Distinctive:

    Never write fake urgency ("only 24 hours left!") unless the urgency is real.

    line 62
  9. Distinctive:

    Never write a P.S. that's marketing fluff.

    line 63

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.