api-integration
Use this skill when the user says 'API integration', 'connect APIs', 'sync data', 'data mapping', 'rate limiting', or needs…
Use this skill when the user says 'write email sequence', 'email sequence', 'drip campaign', 'email series', 'nurture sequence', 'onboarding emails', 'launch emails', or is creating a multi-email automated campaign. Do NOT use for newsletters or single marketing emails.
$ npx -y skills add cwinvestments/memstack --skill email-sequence --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/email-sequenceContext preview
The summary Claude sees to decide when to auto-load this skill.
Use this skill when the user says 'write email sequence', 'email sequence', 'drip campaign', 'email series', 'nurture sequence', 'onboarding emails', 'launch emails', or is creating a multi-email automated campaign. Do NOT use for newsletters or single marketing emails.
name: memstack-content-email-sequence description: "Use this skill when the user says 'write email sequence', 'email sequence', 'drip campaign', 'email series', 'nurture sequence', 'onboarding emails', 'launch emails', or is creating a multi-email automated campaign. Do NOT use for newsletters or single marketing emails." version: 1.0.0 license: "Proprietary, MemStack™ Pro by CW Affiliate Investments LLC. See LICENSE.txt"
*Produces a complete multi-email sequence with subject lines, preview text, body copy, CTAs, and A/B test suggestions, ready to load into any email platform.*
When this skill activates, output:
`📧 Email Sequence: Designing email campaign structure...`
Then execute the protocol below.
| Context | Status | |---------|--------| | User says "write email sequence" or "email series" or "drip campaign" | ACTIVE | | User says "nurture sequence" or "onboarding emails" or "launch emails" | ACTIVE | | Creating a multi-email automated campaign | ACTIVE | | Writing a single one-off email | DORMANT, just write the email directly | | Writing newsletter content | DORMANT | | Writing email for support or personal communication | DORMANT |
| Trap | Reality Check | |------|---------------| | "Pitch in the first email" | Email 1 is for trust, not selling. Premature pitching gets unsubscribes, not conversions. | | "More emails = more sales" | Frequency breeds fatigue. 5 focused emails beat 12 filler emails. Quality per email matters more than quantity. | | "Long subject lines explain more" | Subject lines are read on mobile. After 50 characters, they're truncated. Short + curious wins. | | "The body copy needs to be short" | Length doesn't kill: boring does. A 500-word email that's engaging outperforms a 100-word email that's bland. | | "Everyone gets the same sequence" | Segmentation doubles conversion. At minimum, separate new subscribers from existing customers. |
If the user hasn't provided details, ask:
> I need a few details for the email sequence: > 1. **Product/service**: what are you promoting or onboarding for? > 2. **Target audience**: who receives these emails? (new signups, leads, customers, etc.) > 3. **Sequence goal**: what's the purpose? > - Nurture (build trust over time) > - Launch (build anticipation, sell on launch day) > - Onboarding (activate new users) > - Re-engagement (win back inactive users) > 4. **Entry trigger**: what puts someone into this sequence? (signup, purchase, abandoned cart, etc.) > 5. **Existing relationship**: do they already know you, or is this first contact?
Plan the sequence length and cadence based on the goal:
| Goal | Emails | Cadence | Arc | |------|--------|---------|-----| | **Nurture** | 5-7 | Every 2-3 days | Welcome → Story → Value → Value → Soft pitch → Hard pitch → Last chance | | **Launch** | 4-6 | Daily during launch week | Announcement → Behind-the-scenes → Early access → Launch day → Reminder → Last chance | | **Onboarding** | 3-5 | Day 0, 1, 3, 7, 14 | Welcome → Quick win → Key feature → Advanced tip → Check-in | | **Re-engagement** | 3-4 | Every 3-5 days | Miss you → What's new → Special offer → Goodbye (unsubscribe) |
**Sequence map:**
Email 1 (Day 0) → [Welcome/Hook]: Set expectations, deliver value
↓ 2 days
Email 2 (Day 2) → [Story/Credibility]: Build trust, share journey
↓ 2 days
Email 3 (Day 4) → [Value/Teaching]: Prove expertise, give actionable tip
↓ 3 days
Email 4 (Day 7) → [Soft Pitch]: Introduce offer naturally
↓ 3 days
Email 5 (Day 10) → [Hard Pitch]: Urgency, scarcity, direct CTAPresent the sequence map for user approval before writing emails.
The first email sets the tone for the entire relationship:
## Email 1: Welcome / Hook **Send:** Immediately upon trigger (Day 0) **Goal:** Set expectations, deliver promised value, make a first impression **Tone:** Warm, personal, not salesy --- **Subject line:** [50 chars max, deliver on signup promise] **Preview text:** [90 chars max, extends subject line, visible in inbox] --- Hey [First Name], [Opening: Thank them for signing up / downloading / purchasing. Be specific about what they signed up for.] [Deliver the promised value immediately, if they signed up for a guide, link it here. If they signed up for a tool, show them the first step. Never make them wait for what was promised.] Here's what to expect from me: - [Frequency]: You'll hear from me [every X days / weekly / etc.] - [Content type]: I'll share [tips, strategies, behind-the-scenes, etc.] - [Value promise]: Every email will [teach you something / save you time / etc.] [One quick win: give them something actionable they can do right now, in under 5 minutes, that gets a result.] Talk soon, [Name] P.S. [Curiosity hook for Email 2: "Tomorrow, I'll share the story of how [interesting teaser]..."] --- **CTA:** [Deliver the lead magnet / Start using the product / Reply to say hello]
**Email 1 rules:**
## Email 2: Story / Credibility **Send:** Day 2 **Goal:** Build personal connection, establish credibility through narrative **Tone:** Conversational, vulnerable, relatable --- **Subject line:** [50 chars max, hint at a story or revelation] **Preview text:** [90 chars max] --- Hey [First Name], [Opening: Bridge from Email 1: "Yesterday I shared [X]. Today I want to tell you why I built this / started this / care about this."] [Story: Share your
The structured skill framework for Claude Code: 131 professional skills for deployment, security, databases, content, marketing, and more. Skills activate automatically when you need them. Say "deploy this to Railway" and the right skill loads on demand.
Use this skill when the user says 'API integration', 'connect APIs', 'sync data', 'data mapping', 'rate limiting', or needs…
Use this skill when the user says 'content pipeline', 'content automation', 'auto-publish', 'repurpose content', 'multi-platform…
Use this skill when the user says 'cron job', 'scheduled task', 'run every', 'cron expression', 'recurring job', or needs…
Use when the user says 'what MCP servers', 'find an MCP for', 'hosted MCP', 'list MCP servers', 'MCP catalog', 'available MCP…
Use this skill when the user says 'n8n workflow', 'build a workflow', 'automation workflow', 'connect services', or needs visual…
Use this skill when the user says 'webhook', 'webhook handler', 'webhook endpoint', 'receive events', 'HMAC verification',…