You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionemail-sequenceExecute the skills CLI command in your project's root directory to begin installation:
Fetches email-sequence from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate email-sequence. Access via /email-sequence in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.
Before creating a sequence, understand:
Sequence Type
Audience Context
Goals
Depends on:
Consider:
Patterns that work:
Email 1: Welcome (Immediate)
Email 2: Quick Win (Day 1-2)
Email 3: Story/Why (Day 3-4)
Email 4: Social Proof (Day 5-6)
Email 5: Overcome Objection (Day 7-8)
Email 6: Core Feature (Day 9-11)
Email 7: Conversion (Day 12-14)
Email 1: Deliver + Introduce (Immediate)
Email 2: Expand on Topic (Day 2-3)
Email 3: Problem Deep-Dive (Day 4-5)
Email 4: Solution Framework (Day 6-8)
Email 5: Case Study (Day 9-11)
Email 6: Differentiation (Day 12-14)
Email 7: Objection Handler (Day 15-18)
Email 8: Direct Offer (Day 19-21)
Email 1: Check-In (Day 30-60 of inactivity)
Email 2: Value Reminder (Day 2-3 after)
Email 3: Incentive (Day 5-7 after)
Email 4: Last Chance (Day 10-14 after)
Coordinate with in-app onboarding. Email supports, doesn't duplicate.
Email 1: Welcome + First Step (Immediate)
Email 2: Getting Started Help (Day 1)
Email 3: Feature Highlight (Day 2-3)
Email 4: Success Story (Day 4-5)
Email 5: Check-In (Day 7)
Email 6: Advanced Tip (Day 10-12)
Email 7: Upgrade/Expand (Day 14+)
A comprehensive guide to lifecycle and campaign emails. Use this as an audit checklist and implementation reference.
Trigger: User signs up (free or trial) Goal: Activate user, drive to aha moment Typical sequence: 5-7 emails over 14 days
Key metrics: Activation rate, feature adoption
Trigger: User converts to paid Goal: Reinforce purchase decision, drive adoption, reduce early churn Typical sequence: 3-5 emails over 14 days
Key point: Different from new user series—they've committed. Focus on reinforcement and expansion, not conversion.
Trigger: User hasn't completed critical setup step after X time Goal: Nudge completion of high-value action Format: Single email or 2-3 email mini-sequence
Example triggers:
Copy approach:
Trigger: Existing user invites teammate Goal: Activate the invited user Recipient: The person being invited
Copy approach:
Trigger: Free user shows engagement, or trial ending Goal: Convert free to paid Typical sequence: 3-5 emails
Trigger options:
Sequence structure:
Trigger: User approaching plan limits or using features available on higher tier Goal: Upsell to next tier Format: Single email or 2-3 email sequence
Trigger examples:
Copy approach:
Trigger: Customer milestone (30/60/90 days, key achievement, support resolution) Goal: Generate social proof on G2, Capterra, app stores Format: Single email
Best timing:
Copy approach:
Trigger: Signs of struggle (drop in usage, failed actions, error encounters) Goal: Save at-risk user, improve experience Format: Single email
Trigger examples:
Copy approach:
Trigger: Time-based (weekly, monthly, quarterly) Goal: Demonstrate value, drive engagement, reduce churn Format: Single email, recurring
What to include:
Examples:
Key point: Make them feel good and remind them of value delivered.
Trigger: Time-based (quarterly) or event-based (post-milestone) Goal: Measure satisfaction, identify promoters and detractors Format: Single email
Best practices:
Follow-up based on score:
Trigger: Customer milestone, promoter NPS score, or campaign Goal: Generate referrals Format: Single email or periodic reminders
Good timing:
Copy approach:
Trigger: Monthly subscriber at renewal time or campaign Goal: Convert monthly to annual (improve LTV, reduce churn) Format: Single email or 2-email sequence
Value proposition:
Best timing:
Trigger: Payment fails Goal: Recover revenue, retain customer Typical sequence: 3-4 emails over 7-14 days
Sequence structure:
Copy approach:
Key metrics: Recovery rate, time to recovery
Trigger: User cancels subscription Goal: Learn why, opportunity to save Format: Single email (immediate)
Options:
Questions to ask:
Winback opportunity: Based on reason, offer targeted save (discount, pause, downgrade, training).
Trigger: X days before renewal (14 or 30 days typical) Goal: No surprise charges, opportunity to expand Format: Single email
What to include:
Required for: Annual subscriptions, high-value contracts
Trigger: Time-based Goal: Drive engagement, demonstrate value Format: Single email, recurring
Content by frequency:
Structure:
Personalization: Must be relevant to their actual usage. Empty reports are worse than no report.
Trigger: Specific achievement or event Goal: Celebrate, drive continued engagement Format: Single email per event
Milestone examples:
Copy approach:
Trigger: Trial ended without conversion Goal: Convert or re-engage Typical sequence: 3-4 emails over 30 days
Sequence structure:
Segmentation: Different approach based on trial engagement level:
Trigger: Time after cancellation (30, 60, 90 days) Goal: Win back churned customers Typical sequence: 2-3 emails spread over 90 days
Sequence structure:
Copy approach:
Key point: They're more likely to return if their reason was addressed.
Trigger: Time-based (monthly) Goal: Engagement, brand presence, content distribution Format: Single email, recurring
Content mix:
Best practices:
Trigger: Calendar events (Black Friday, New Year, etc.) Goal: Drive conversions with timely offer Format: Campaign burst (2-4 emails)
Common opportunities:
Sequence structure:
Trigger: New feature release Goal: Adoption, engagement, demonstrate momentum Format: Single email per major release
What to include:
Segmentation: Consider targeting based on relevance:
Trigger: Time-based (weekly or monthly) Goal: Thought leadership, engagement, brand value Format: Curated newsletter
Content:
Best for: B2B products where customers care about industry trends.
Trigger: Price change annou
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
email-sequence has been reliable in day-to-day use. Documentation quality is above average for community skills.
email-sequence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
email-sequence is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
email-sequence reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added email-sequence from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: email-sequence is focused, and the summary matches what you get after install.
I recommend email-sequence for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in email-sequence — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
email-sequence fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: email-sequence is focused, and the summary matches what you get after install.
showing 1-10 of 62