emails
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill emails --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Email Sequence Design 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. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before creating a sequence, understand: 1. **Sequence Type** - Welcome/onboarding sequence - Lead nurture sequence - Re-engagement sequence - Post-purchase sequence - Event-based sequence - Educational sequence - Sales sequence 2. **Audience Context** - Who are they? - What triggered them into this sequence? - What do they already know/believe? - What's their current relationship with you? 3. **Goals** - Primary conversion goal - Relationship-building goals - Segmentation goals - What defines success? --- ## Core Principles ### 1. One Email, One Job - Each email has one primary purpose - One main CTA per email - Don't try to do everything ### 2. Value Bef
- Initial Assessment
- Core Principles
- 1. One Email, One Job
- 2. Value Before Ask
- 3. Relevance Over Volume
- 4. Clear Path Forward
- Email Sequence Strategy
- Sequence Length
- Timing/Delays
- Subject Line Strategy
- Preview Text
- Sequence Types Overview
- Welcome Sequence (Post-Signup)
- Lead Nurture Sequence (Pre-Sale)
What does the emails skill do?
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill emails --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.