Skip to main content
ClaudeWave
ES, Spanish
Slash Command906 estrellas del repoactualizado 16d ago

email-sequence

The email-sequence Claude Code command generates complete email marketing workflows including subject line A/B variants, preview text, body copy, send timing with cadence rules, audience segmentation criteria, branching logic, and personalization tokens. Use this command when designing welcome series, nurture campaigns, cart abandonment flows, re-engagement sequences, onboarding programs, post-purchase follow-ups, event-triggered campaigns, or promotional series ready for deployment in email service platforms like Klaviyo, HubSpot, or Mailchimp.

Instalar en Claude Code
Copiar
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/indranilbanerjee/digital-marketing-pro/HEAD/commands/email-sequence.md -o ~/.claude/commands/email-sequence.md
Después abre una sesión nueva de Claude Code; el slash command carga automáticamente.

email-sequence.md

# Email Sequence

> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md).

Design a complete email sequence ready for implementation in any ESP. Includes subject lines with A/B variants, preview text, full body copy, send timing with cadence logic, segmentation rules, branching conditions, personalization tokens, and deliverability best practices.

## Trigger

User runs `/digital-marketing-pro:email-sequence` or asks to create an email drip, email flow, nurture sequence, welcome series, re-engagement campaign, or cart abandonment flow.

## Inputs

Gather the following from the user. If not provided, ask before proceeding:

1. **Sequence type** — one of:
   - Welcome series (new subscriber/user)
   - Nurture sequence (move leads down funnel)
   - Onboarding (activate new users/customers)
   - Re-engagement (win back inactive subscribers)
   - Cart abandonment (recover lost purchases)
   - Post-purchase (retention, upsell, review request)
   - Event-based (webinar, product launch, seasonal)
   - Promotional (sale, offer, limited-time)

2. **Goal** — what the sequence should achieve (activate, convert, retain, upsell, educate, re-engage)

3. **Audience segment** — who receives this sequence and what triggers entry (signup, purchase, inactivity period, cart event, etc.)

4. **Number of emails** — desired count, or let the system recommend based on sequence type

5. **Key messages or offers** — core value propositions, promotions, or content to include

6. **ESP** (optional) — platform in use (Klaviyo, Mailchimp, HubSpot, SendGrid, Customer.io) for format and feature guidance

## Brand Voice

- If a brand profile exists, apply voice settings automatically
- Load email-specific tone overrides from guidelines if available
- Apply compliance rules (CAN-SPAM, GDPR, CASL) based on brand's target markets

## Sequence Design

### Sequence Architecture
- Map the sequence to the customer journey stage
- Define the narrative arc (introduction → value → proof → conversion)
- Determine optimal email count based on sequence type:
  - Welcome: 3-5 emails over 7-14 days
  - Nurture: 5-8 emails over 3-6 weeks
  - Onboarding: 4-7 emails over 14-30 days
  - Re-engagement: 3-4 emails over 7-14 days
  - Cart abandonment: 3 emails over 3 days
  - Post-purchase: 3-5 emails over 30-60 days
- Define send cadence and timing logic

### Per-Email Blueprint

For each email in the sequence:

**Subject Lines:**
- 2-3 subject line options per email
- Character counts (aim for 30-50 characters for mobile)
- Preview text that complements (not repeats) the subject
- A/B testing recommendations

**Body Copy:**
- Opening hook tied to the sequence narrative
- Body content with clear hierarchy and scannable formatting
- Single primary CTA (button text + destination)
- Secondary CTA (optional, text link)
- Personalization tokens (first name, company, product, behavior-based)
- Dynamic content blocks (based on segment attributes)

**Timing:**
- Send delay from trigger or previous email
- Best send time recommendation (day of week, time of day)
- Timezone handling notes

### Segmentation and Branching Logic
- Entry trigger conditions
- Branching rules based on engagement (opened, clicked, converted)
- Exit conditions (converted, unsubscribed, completed sequence)
- Suppression rules (already purchased, already in another sequence)

### Deliverability Checklist

For each email, verify:
- No spam trigger words in subject or body
- Link density appropriate (not too many links)
- Image-to-text ratio balanced
- Unsubscribe link present and functional
- Physical address included (CAN-SPAM)
- Authentication reminders (SPF, DKIM, DMARC)
- List hygiene recommendations

## Output Format

### Sequence Overview
- Sequence name, type, and goal
- Target audience and entry trigger
- Email count and total duration
- Expected performance benchmarks for the sequence type

### Email-by-Email Breakdown

| Email # | Subject Line | Send Timing | Goal | Primary CTA |
|---------|-------------|-------------|------|-------------|

Followed by full copy for each email.

### Flow Diagram
- Visual representation of the sequence flow with branching logic
- Entry → Email 1 → Wait → Email 2 → Branch (opened/not opened) → etc.

### Performance Benchmarks

| Metric | Industry Average | Target |
|--------|-----------------|--------|

Include: open rate, click rate, conversion rate, unsubscribe rate per email.

## After the Sequence

Ask: "Would you like me to:
- Set up this sequence in your ESP? (`/digital-marketing-pro:send-email-campaign`)
- Create A/B test variants for the subject lines? (`/digital-marketing-pro:prompt-test`)
- Design a complementary re-engagement flow for non-openers?
- Build landing pages for the CTA destinations? (`/digital-marketing-pro:content-engine`)
- Add SMS touchpoints alongside the emails? (`/digital-marketing-pro:send-sms`)
- Review deliverability setup for your domain? (`/digital-marketing-pro:email-sequence` with deliverability focus)"
ab-test-planSkill

Design a statistically rigorous A/B or multivariate test plan — If/Then/Because hypothesis, control and variant specs, required sample size per variant (absolute vs relative MDE via sample-size-calculator.py), test duration, guardrail metrics, stopping rules, and go/no-go decision criteria. Triggers on \"/digital-marketing-pro:ab-test-plan\", \"set up an A/B test\", \"how long should my test run\", \"calculate sample size for an experiment\", \"is this test result significant\". Reads the brand profile and past campaign-tracker results to avoid re-testing validated hypotheses; finished tests are evaluated with significance-tester.py by the cro-specialist agent.

ad-creativeSkill

Generate 3-5 ad copy variations per platform — headlines, descriptions, and CTAs formatted to Google, Meta, LinkedIn, TikTok, X, and Pinterest specs — each scored 1-10 with policy-compliance flags, A/B testing groupings, and a message-match check against the landing page. Triggers on \"/digital-marketing-pro:ad-creative\", \"write ad copy for Meta\", \"give me RSA headline variations\", \"we need LinkedIn ad copy\", \"draft TikTok ad creative\". Reads the brand profile, guidelines, and compliance rules; routes video ad scripts to /digital-marketing-pro:video-script and gates AI-generated visuals for EU campaigns through /digital-marketing-pro:c2pa-metadata and /digital-marketing-pro:check.

add-integrationSkill

Walk through adding a custom MCP server integration to the plugin — searches npm for an existing MCP package (or scaffolds a custom server from the plugin's guide), generates the exact .mcp.json entry, sets up environment-variable credentials, tests connectivity, and documents the tools the new server exposes. Triggers on \"/digital-marketing-pro:add-integration\", \"connect Ahrefs to the plugin\", \"add a new MCP server\", \"integrate our internal API\", \"hook up Stripe data\". Reads the brand profile and agency credential profiles at ~/.claude-marketing/credentials/ to map client-specific keys; custom builds follow skills/context-engine/custom-mcp-guide.md.

aeo-auditSkill

Audit how a brand appears across the 6 canonical AI answer surfaces — ChatGPT, Perplexity, Google AI Mode, AI Overviews, Gemini, Copilot — probing 10-25 queries into a numbered output bundle with per-platform visibility scorecards, citation-accuracy checks, a competitor matrix, content gaps, and an optimization playbook behind a four-gate quality scorecard. Triggers on \"/digital-marketing-pro:aeo-audit\", \"does ChatGPT know about our brand\", \"check our AI search visibility\", \"how does Perplexity describe us\", \"are we showing up in AI Overviews\". Reads the brand profile; reconciles probes against GSC actuals via /digital-marketing-pro:gsc-ai-performance and defines the AI-visibility scoring standard reused by geo-monitor and share-of-voice.

aeo-geoSkill

Strategy module for Answer Engine / Generative Engine Optimization — audits AI visibility, restructures content for citation, runs entity-consistency checks across Knowledge Graph, Wikidata, Wikipedia, Crunchbase, and LinkedIn, and produces JSON-LD schema specs, monitoring frameworks, and a 90-day LLM content strategy. Triggers on \"/digital-marketing-pro:aeo-geo\", \"how do we get cited by AI\", \"optimize for AI Overviews\", \"fix our entity consistency\", \"do we need llms.txt\". Reads the brand profile, compliance rules, and industry benchmarks; its measurement counterpart is /digital-marketing-pro:aeo-audit, with GSC actuals via /digital-marketing-pro:gsc-ai-performance.

agency-dashboardSkill

Generate a portfolio-level dashboard across ALL client brands — per-client RAG health scores, campaign activity, budget pacing, aggregate KPIs, team utilization, pending approvals, upcoming deadlines, and an alerts panel — built for agency standups and weekly reviews. Triggers on \"/digital-marketing-pro:agency-dashboard\", \"how are all our clients doing\", \"portfolio health check\", \"budget pacing across accounts\", \"which accounts are at risk\". Enumerates every brand under ~/.claude-marketing/brands/ and pulls data via campaign-tracker.py, execution-tracker.py, and team-manager.py; drill into a single client with /digital-marketing-pro:performance-report or /digital-marketing-pro:client-report.

agency-operationsSubagent

Invoke when the user needs to manage multiple client brands, view portfolio-level dashboards, generate client reports, manage SOPs, switch credential profiles, assign team tasks, configure regions, or generate executive summaries. Triggers on requests involving multi-client management, agency workflows, client onboarding, or portfolio oversight.

analytics-analystSubagent

Invoke when the user needs help with marketing measurement, KPI definition, dashboard design, attribution reporting, performance analysis, competitive benchmarking, or translating data into marketing decisions. Triggers on requests involving metrics, reporting, analytics setup, or data interpretation.