agentleFS
styfinitystyfinity/claude-marketing-department/skills/email-sequence/SKILL.md

email-sequence

Skill6 starsChanged 4 months agoMITView on GitHub

Writes a complete email sequence (welcome, nurture, launch, or win-back) where every email has one job — subject lines, full body copy, and send timing included. Use when a sequence needs to be ready to load into the email tool, not outlined.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • silvainfmSkill

    paid-ads

    When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.

    Also in 39 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • silvainfmSkill

    competitor-alternatives

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.

    Also in 34 projects that use this

  • +6 more from nicepkg

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 79 edited versions we read keep these.

  • 1

    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:

    Write like one person emailing another.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 79 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 Sequence — one job per email

A sequence fails when every email tries to do everything — teach, pitch, build trust — and does none of it. A good sequence is a relay: each email moves the reader one belief forward and hands off to the next. This skill writes the relay, not a pile of emails.

Inputs

  • Sequence type (welcome / nurture / launch / win-back), the audience, and the offer or goal it serves: $ARGUMENTS
  • From marketing-brief.md if present: the offer and its proof, the language bank (voice-of-customer), top pains and desired outcomes, objections & beliefs, and the banned-phrases list. Never re-ask what the brief already answers.

Do this

  1. Name the sequence's one commercial job — the action it exists to cause, in one sentence:
    • Welcome — deliver the first value fast, set expectations, get a first small yes.
    • Nurture — build the beliefs the offer needs, one per email.
    • Launch — open and close a real window with honest urgency.
    • Win-back — re-earn attention with a reason to return, not a discount reflex.
  2. Map the belief journey. List what the reader must believe before the final CTA can land, in order. One belief per email — that sets the email count (usually 4–7), not a preset template length.
  3. Spec each email before writing it: its single job, the belief it installs, the proof it uses (from the brief only — flag gaps rather than inventing), and its CTA. Early emails ask for small commitments — a reply, a click; only later emails sell.
  4. Write every email in full. Three subject lines (pick one, keep two alternates for testing), preview text, body of 80–200 words in plain-text human register — one idea, short paragraphs, nothing that depends on images. Phrase from the language bank; strip anything on the banned-phrases list.
  5. Set the timing. Day offset from the trigger for each send, with reasoning — welcome email one lands within minutes while intent is hot; a win-back respects the silence that came before it.
  6. Read the whole sequence as the recipient. Kill or merge any email repeating an earlier email's job, and check the escalation — each email should assume the beliefs the previous ones installed.

Output

The full sequence: per email — number, job, send timing, chosen subject plus two alternates, preview text, complete body, CTA. Close with a three-line loading note: the trigger, the exit condition (what removes someone mid-sequence), and the one proof gap that would most strengthen the sequence if filled. For a launch sequence, cross-check the dates against the campaign plan before loading.

Rules

  • Subject lines may exaggerate curiosity, never facts. If the body cannot cash the subject's cheque, rewrite the subject.
  • Evidence over invention: no fabricated results, customers, or numbers in any email. Flag the gap and write around it.
  • One job per email. An email doing two jobs becomes two emails or loses one.
  • Write like one person emailing another. The moment it reads like a brand broadcasting, start again.
  • Timing is part of the copy. The right email on the wrong day is the wrong email.

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.