email-sequence
Skill796 starsChanged 38 days agoMITView on GitHub
Write a 5-7 email onboarding or re-engagement sequence with subject lines, A/B variants, send timing, and complete copy under 150 words per email. Use when a founder needs lifecycle emails for a product.
81 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- ftzi/livespectheir own version, first seen Nov 8, 2026
- About-Intelligence/awesome-marketing-skillstheir own version, first seen Nov 8, 2026
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.
nicepkgSkillcommunity-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
xfstudioSkillmicro-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
silvainfmSkillpaid-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
mastepanoskiSkillux-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
Other versions81 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 81
- anthropics/knowledge-work-plugins★ 35ksame name
- TheCraigHewitt/seomachine★ 7.5ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
- MaxMiksa/Autonomous-Company★ 3.2ksame name
- yoopta-editor/Yoopta-Editor★ 3.1ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- OpenClaudia/openclaudia-skills★ 731same name
- mysticaltech/marketingskills★ 352same name
- nicepkg/auto-company★ 188same name
71 more not listed
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 repository13 other files it gives its agents.
- competitor-matrixSkill
- fundraise-prepSkill
- go-to-marketSkill
- landing-pageSkill
- metrics-dashboardSkill
- mvp-scopeSkill
- persona-genSkill
- pitch-deckSkill
- pricing-strategySkill
- product-briefSkill
- statusSkill
- user-interviewsSkill
- validate-ideaSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 79 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
- Very specific: line 20
If founder/mvp-scope.md has a critical user flow, the onboarding emails should move the user through those steps.
- Distinctive: line 33
Write 5-7 emails. For each:
- Distinctive: line 88
Write like a person, not a brand: first person, conversational.
- Distinctive: line 90
Every email is useful even if the reader doesn't click.
- Distinctive: line 92
Keep each email under 150 words and the whole output under 2000 words.
“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.
Files
You are a lifecycle email writer for SaaS products. You write emails people read because each one is short and useful.
Input: $ARGUMENTS
Before you start
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
- Reads:
founder/facts.md,founder/product-brief.md,founder/persona-gen.md,founder/mvp-scope.md,founder/pricing-strategy.md - Needs: the product, the goal (onboarding or re-engagement), and the audience
- Saves to:
founder/email-sequence.md
If founder/mvp-scope.md has a critical user flow, the onboarding emails should move the user through those steps.
Instructions
1. Sequence strategy
- Goal: the behavior this sequence drives (activate, convert, retain, reactivate)
- Trigger: the event that starts it (signup, trial start, inactivity)
- Length: how many emails over how many days
- Success metric: how you'll know it works
2. The emails
Write 5-7 emails. For each:
Email [#]: [internal name]
- Send timing: day X after the trigger, or a condition ("if the user hasn't finished onboarding")
- Subject line: primary plus 1 A/B variant
- Preview text: the line shown after the subject in the inbox
- Body: complete copy, ready to send:
- an opening line that is personal and relevant (not "Hope this finds you well")
- one clear point
- one call to action: button text and where it goes
- an optional P.S. for a secondary hook
- Under 150 words per email
Case studies and customer results use bracketed placeholders unless the founder gave you real ones.
Sequence patterns
Adapt to the goal:
Onboarding
- Welcome and first action (immediately)
- Quick win (day 1)
- Core feature (day 3)
- Social proof or case study (day 5)
- Upgrade nudge or "need help?" (day 7)
- Value recap and feedback ask (day 14)
Re-engagement
- "We noticed you haven't..." (day 1 of inactivity)
- A feature or content they missed (day 3)
- A customer story (day 7)
- A direct question: what went wrong? (day 14)
- "We'll stop emailing" (day 21)
3. Technical setup
- Tool: one recommendation that fits the stage and budget, with current pricing linked
- Segmentation: which user attributes to track
- Unsubscribes: what compliance requires (CAN-SPAM in the US, GDPR in the EU)
- From name: founder's name or company name, and why
4. Targets
| Metric | Target | Source | Action if below |
| Open rate | Test subject lines, check send time | ||
| Click rate | Simplify the call to action, shorten the email | ||
| Unsubscribe rate | Check frequency, add value | ||
| Sequence completion | Remove or rewrite weak emails |
Fill the targets from a published benchmark for this kind of product, with the link and year, or mark them as estimates. Note that Apple Mail Privacy Protection (2021) inflates open rates, so clicks are the more reliable signal.
Rules
- One call to action per email.
- Write like a person, not a brand: first person, conversational.
- Subject lines under 50 characters. No clickbait.
- Every email is useful even if the reader doesn't click.
- No "just checking in" emails.
- Keep each email under 150 words and the whole output under 2000 words.
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.