Corey Haines
30f9b9a729
* feat: v2.0 skill renames and CRO consolidation BREAKING CHANGE: Users must reinstall skills after this update. ## Skill Renames (16) - ab-test-setup → ab-testing - analytics-tracking → analytics - aso-audit → aso - competitor-alternatives → competitors - email-sequence → emails - free-tool-strategy → free-tools - launch-strategy → launch - onboarding-cro → onboarding - paywall-upgrade-cro → paywalls - popup-cro → popups - pricing-strategy → pricing - product-marketing-context → product-marketing - referral-program → referrals - schema-markup → schema - signup-flow-cro → signup - social-content → social ## Consolidations (1) - page-cro + form-cro → cro (form content in references/form.md) ## Why 2.0? - Shorter, cleaner skill names - Consistent naming (no -strategy, -setup, -cro suffixes) - All cross-references updated across 100+ files Total skills: 40 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(v2.0): update evals for renamed skills, fix validate script, clear warnings - Update 32 evals.json files to reference new skill names (page-cro → cro, product-marketing-context → product-marketing, etc.) — these were missed in the initial v2.0 rename pass since only SKILL.md and marketplace.json were updated. - Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk so frontmatter extraction works on macOS. - Move Copy Editing Checklist (56 lines) to references/checklist.md to bring copy-editing SKILL.md under the 500-line limit (508 → 457). - Add "see X" pointers to marketing-psychology description for skill discovery (cro, pricing, copywriting). - Update skill-request.yml issue template placeholder (page-cro → cro). All 40 skills now pass validation with zero warnings. * fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md Adds 48 new eval cases (6 per skill) for skills that previously had no evals: aso, co-marketing, community-marketing, competitor-profiling, directory-submissions, image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases). Strips leftover frontmatter from skills/cro/references/form.md — it was inherited from the old form-cro SKILL.md before consolidation. Reference files don't need frontmatter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): rename paid-ads → ads One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates the skill directory, SKILL.md frontmatter, evals.json, README skill table, the v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in related skills (ad-creative, aso, competitor-profiling, customer-research, lead-magnets, marketing-ideas) plus the tools/integrations guides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside each SKILL.md was still on 1.x. That mismatch would have caused the update-check flow to perpetually report 'update available' since it compares VERSIONS.md against local SKILL.md metadata versions. Caught by codex review (P1). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): add legacy product-marketing-context.md filename fallback Before this fix, users upgrading from v1.x who had a `product-marketing-context.md` file would lose automatic context loading — every skill only checked the new `product-marketing.md` filename. Now all 40 skills also accept the legacy filename (in either `.agents/` or `.claude/`), and the README migration command covers both legacy and current filenames. Caught by codex review (P1 + P2). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): re-sort README skills table alphabetically, fix ads box width The skills table had a few entries out of alphabetical order from the renames (co-marketing was after cold-email, ads was at the renamed position). Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the ASCII flow diagram to keep the box width consistent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array README upgrade guide now includes: - A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so users don't end up with both old and new folders side-by-side after upgrading - The full v1 to v2 rename map for reference - Existing product-marketing-context.md migration steps (preserved) sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json -- Claude Code's plugin schema discovers skills via the `skills/` directory, and the explicit array was failing validation. The script now refreshes the description count and strips the stale array if present. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
169 lines
3.8 KiB
Markdown
169 lines
3.8 KiB
Markdown
# Email Sequence Templates
|
|
|
|
Detailed templates for common email sequences.
|
|
|
|
## Contents
|
|
- Welcome Sequence (Post-Signup)
|
|
- Lead Nurture Sequence (Pre-Sale)
|
|
- Re-Engagement Sequence
|
|
- Onboarding Sequence (Product Users)
|
|
|
|
## Welcome Sequence (Post-Signup)
|
|
|
|
**Email 1: Welcome (Immediate)**
|
|
- Subject: Welcome to [Product] — here's your first step
|
|
- Deliver what was promised (lead magnet, access, etc.)
|
|
- Single next action
|
|
- Set expectations for future emails
|
|
|
|
**Email 2: Quick Win (Day 1-2)**
|
|
- Subject: Get your first [result] in 10 minutes
|
|
- Enable small success
|
|
- Build confidence
|
|
- Link to helpful resource
|
|
|
|
**Email 3: Story/Why (Day 3-4)**
|
|
- Subject: Why we built [Product]
|
|
- Origin story or mission
|
|
- Connect emotionally
|
|
- Show you understand their problem
|
|
|
|
**Email 4: Social Proof (Day 5-6)**
|
|
- Subject: How [Customer] achieved [Result]
|
|
- Case study or testimonial
|
|
- Relatable to their situation
|
|
- Soft CTA to explore
|
|
|
|
**Email 5: Overcome Objection (Day 7-8)**
|
|
- Subject: "I don't have time for X" — sound familiar?
|
|
- Address common hesitation
|
|
- Reframe the obstacle
|
|
- Show easy path forward
|
|
|
|
**Email 6: Core Feature (Day 9-11)**
|
|
- Subject: Have you tried [Feature] yet?
|
|
- Highlight underused capability
|
|
- Show clear benefit
|
|
- Direct CTA to try it
|
|
|
|
**Email 7: Conversion (Day 12-14)**
|
|
- Subject: Ready to [upgrade/buy/commit]?
|
|
- Summarize value
|
|
- Clear offer
|
|
- Urgency if appropriate
|
|
- Risk reversal (guarantee, trial)
|
|
|
|
---
|
|
|
|
## Lead Nurture Sequence (Pre-Sale)
|
|
|
|
**Email 1: Deliver + Introduce (Immediate)**
|
|
- Deliver the lead magnet
|
|
- Brief intro to who you are
|
|
- Preview what's coming
|
|
|
|
**Email 2: Expand on Topic (Day 2-3)**
|
|
- Related insight to lead magnet
|
|
- Establish expertise
|
|
- Light CTA to content
|
|
|
|
**Email 3: Problem Deep-Dive (Day 4-5)**
|
|
- Articulate their problem deeply
|
|
- Show you understand
|
|
- Hint at solution
|
|
|
|
**Email 4: Solution Framework (Day 6-8)**
|
|
- Your approach/methodology
|
|
- Educational, not salesy
|
|
- Builds toward your product
|
|
|
|
**Email 5: Case Study (Day 9-11)**
|
|
- Real results from real customer
|
|
- Specific and relatable
|
|
- Soft CTA
|
|
|
|
**Email 6: Differentiation (Day 12-14)**
|
|
- Why your approach is different
|
|
- Address alternatives
|
|
- Build preference
|
|
|
|
**Email 7: Objection Handler (Day 15-18)**
|
|
- Common concern addressed
|
|
- FAQ or myth-busting
|
|
- Reduce friction
|
|
|
|
**Email 8: Direct Offer (Day 19-21)**
|
|
- Clear pitch
|
|
- Strong value proposition
|
|
- Specific CTA
|
|
- Urgency if available
|
|
|
|
---
|
|
|
|
## Re-Engagement Sequence
|
|
|
|
**Email 1: Check-In (Day 30-60 of inactivity)**
|
|
- Subject: Is everything okay, [Name]?
|
|
- Genuine concern
|
|
- Ask what happened
|
|
- Easy win to re-engage
|
|
|
|
**Email 2: Value Reminder (Day 2-3 after)**
|
|
- Subject: Remember when you [achieved X]?
|
|
- Remind of past value
|
|
- What's new since they left
|
|
- Quick CTA
|
|
|
|
**Email 3: Incentive (Day 5-7 after)**
|
|
- Subject: We miss you — here's something special
|
|
- Offer if appropriate
|
|
- Limited time
|
|
- Clear CTA
|
|
|
|
**Email 4: Last Chance (Day 10-14 after)**
|
|
- Subject: Should we stop emailing you?
|
|
- Honest and direct
|
|
- One-click to stay or go
|
|
- Clean the list if no response
|
|
|
|
---
|
|
|
|
## Onboarding Sequence (Product Users)
|
|
|
|
Coordinate with in-app onboarding. Email supports, doesn't duplicate.
|
|
|
|
**Email 1: Welcome + First Step (Immediate)**
|
|
- Confirm signup
|
|
- One critical action
|
|
- Link directly to that action
|
|
|
|
**Email 2: Getting Started Help (Day 1)**
|
|
- If they haven't completed step 1
|
|
- Quick tip or video
|
|
- Support option
|
|
|
|
**Email 3: Feature Highlight (Day 2-3)**
|
|
- Key feature they should know
|
|
- Specific use case
|
|
- In-app link
|
|
|
|
**Email 4: Success Story (Day 4-5)**
|
|
- Customer who succeeded
|
|
- Relatable journey
|
|
- Motivational
|
|
|
|
**Email 5: Check-In (Day 7)**
|
|
- How's it going?
|
|
- Ask for feedback
|
|
- Offer help
|
|
|
|
**Email 6: Advanced Tip (Day 10-12)**
|
|
- Power feature
|
|
- For engaged users
|
|
- Level-up content
|
|
|
|
**Email 7: Upgrade/Expand (Day 14+)**
|
|
- For trial users: conversion push
|
|
- For free users: upgrade prompt
|
|
- For paid: expansion opportunity
|