ecommerce-email-marketing-builder
E-commerce email marketing system builder. Creates complete email automation flows with full copywriting, subject lines, ESP setup instructions, segmentation rules, and annual campaign calendars. Generates copy-paste-ready email sequences for Klaviyo, Omnisend, Mailchimp, or any ESP. Covers welcome series, cart abandonment, browse abandonment, post-purchase, review requests, cross-sell, win-back, VIP/loyalty, replenishment, and sunset flows. Includes A/B test subject line variants, send timing, trigger conditions, branching logic, and seasonal campaign calendar. No API key required. Use when: (1) setting up email marketing for an e-commerce store, (2) writing email sequences and flows, (3) planning seasonal email campaigns.
What this skill does
# E-Commerce Email Marketing Builder ๐ง
Build a complete, copy-paste-ready email marketing system for any e-commerce business. Covers 10 core automation flows with full copywriting, ESP setup instructions, segmentation rules, and annual campaign calendars.
**Supported platforms:** Shopify, WooCommerce, BigCommerce, Squarespace, Etsy, TikTok Shop, Amazon, and any platform that connects to an ESP. For marketplace platforms (Amazon, TikTok Shop, Etsy) where buyer emails are restricted, this skill focuses on cross-channel strategies to capture emails via your own website or landing pages.
Built by [Nexscope](https://www.nexscope.ai/) โ your AI assistant for smarter e-commerce decisions.
## Install
```bash
npx skills add nexscope-ai/eCommerce-Skills --skill ecommerce-email-marketing-builder -g
```
## Usage
Once installed, just describe your business and ask for email marketing help. The skill activates automatically.
```
I'm launching a Shopify store selling premium dog treats at $24.99. Help me set up
my email marketing โ I'm using Klaviyo and have about 500 subscribers.
```
```
I sell handmade jewelry on Etsy and my own website. Price range $40-120. I have
2,000 email subscribers but no automated flows set up. What emails should I be sending?
```
```
Build me a complete email system for my sustainable fashion brand. We use Omnisend
and have 8,000 subscribers. I want welcome series, cart abandonment, and post-purchase flows.
```
## Capabilities
- Complete email automation flows for 10 core e-commerce journeys (welcome, cart abandonment, browse abandonment, post-purchase, review request, cross-sell, win-back, VIP/loyalty, replenishment, sunset)
- Full email copywriting for every email โ subject lines, preview text, body copy, CTA button text
- 3-5 A/B test subject line variants per email with different angles (curiosity, urgency, benefit, social proof, personal)
- ESP setup instructions generated for your specific platform โ trigger conditions, flow filters, delay timing, and branching logic using your ESP's exact terminology
- ESP recommendation if you don't have one yet โ based on list size and sales platform, with pricing
- Flow diagrams showing the full sequence: trigger โ delay โ conditional split โ email โ branch
- Segmentation strategy with 8 core segments and exact filter conditions for your ESP
- Annual seasonal campaign calendar customized to your product category
- List growth tactics โ pop-up strategy, checkout opt-in, social โ email conversion
---
## How This Skill Works
**Step 1: Collect information.** Extract from the user's initial message:
- Product / category
- Brand name
- Price range and target audience
- Any context about their business
**Step 2: Ask one follow-up with all remaining questions.** Use multiple-choice format:
```
Great โ [acknowledge what they told you]. To build your email system I need a few more details:
1. Business stage?
a) Pre-launch โ building a list before selling
b) Early โ selling, but under $10K/mo
c) Growing โ $10K-50K/mo
d) Established โ $50K+/mo
2. Which flows do you need? (pick all that apply, or "all")
a) Welcome series
b) Cart abandonment
c) Browse abandonment
d) Post-purchase / thank you
e) Review request
f) Cross-sell / upsell
g) Win-back (re-engage lapsed customers)
h) VIP / loyalty
i) Replenishment (consumable products)
j) Sunset (list cleanup)
k) All of the above
l) Not sure โ recommend for me
3. Brand voice?
a) Professional / corporate
b) Friendly / conversational
c) Playful / fun
d) Premium / luxury
e) Bold / edgy
f) Other: ___________
4. Email platform (ESP)?
a) Klaviyo
b) Omnisend
c) Mailchimp
d) Shopify Email
e) Other: ___________
f) Don't have one yet โ recommend one
5. Current email list size?
a) 0 โ starting from scratch
b) Under 1,000
c) 1,000-10,000
d) 10,000-50,000
e) 50,000+
6. Any active promotions or standard discounts? (e.g., "we always offer 10% for first order")
7. Competitors to reference? (names or URLs, or skip)
Reply like: "1b 2k 3b 4a 5b 6 yes 10% first order 7 skip"
```
**Step 3: If user chose (f) in Q4 โ "Don't have one yet"**, recommend an ESP based on their list size (Q5) and sales platform:
| List Size | Recommended ESP | Approx. Cost |
|-----------|-----------------|:------------:|
| 0-500 | Omnisend Free or Mailchimp Free | $0 |
| 500-2,500 | Omnisend (Shopify) or Mailchimp (other platforms) | $13-20/mo |
| 2,500-10K | Klaviyo | $35-100/mo |
| 10K+ | Klaviyo | $100-350/mo |
โ ๏ธ Prices are approximate (2026). Tell user to verify on each platform's website.
After recommending, continue building flows with setup instructions for the recommended ESP.
**Step 4: If user chose "l) Not sure โ recommend for me" in Q2**, recommend flows based on their business stage:
- **Pre-launch:** Welcome series only (build list first)
- **Early (<$10K/mo):** Welcome + Cart Abandonment + Post-Purchase (the 3 essentials)
- **Growing ($10K-50K):** All of the above + Browse Abandonment + Review Request + Cross-sell
- **Established ($50K+):** All 10 flows
**Step 5: Build each requested flow.** For EVERY flow, output:
1. **Flow overview** โ purpose, expected revenue impact, priority level
2. **Flow diagram** โ visual sequence with timing
3. **For each email in the flow:**
- Subject line (30-50 chars, mobile-friendly) + 3-5 A/B variants with different angles (curiosity, urgency, benefit, social proof, personal)
- Preview text (40-90 chars, complement the subject โ don't repeat it)
- Full email body copy (actual words: hook โ value โ proof โ CTA โ optional P.S.)
- CTA button text (action-oriented, one primary CTA per email) + link destination
4. **Branching logic** โ conditions that split the flow (purchased vs didn't, opened vs didn't)
5. **ESP setup instructions** โ generate trigger conditions, flow filters, delay timing, and branching logic specific to the user's chosen ESP (Q4). Use that ESP's exact terminology and menu paths. If user doesn't have an ESP yet, use Klaviyo terminology as default
**Step 6: Build segmentation strategy.** Define core segments with exact rules:
- New subscribers (no purchase)
- First-time buyers
- Repeat customers (2+ orders)
- VIP / high-value (top 10% by spend)
- At-risk (purchased before, no activity 60-90 days)
- Lapsed (no activity 90+ days)
- Discount-driven (only buys on sale)
**Step 7: Build annual campaign calendar.** Month-by-month with:
- Key dates and seasonal events relevant to the product category
- Campaign theme for each event
- Send schedule (pre-event teaser, launch day, last chance)
- Which segments to target
**Step 8: Provide list growth tactics.** Based on their platform and stage:
- Pop-up strategies (timing, offer, design)
- Landing page recommendations
- Social media โ email conversion tactics
- Checkout opt-in optimization
---
## The 10 Core E-Commerce Email Flows
### Flow 1: Welcome Series
**Priority:** ๐ด Critical โ set up first
**Expected impact:** Highest-opened emails, sets tone for entire relationship
**Emails:** 3-5 emails over 7-14 days
**Trigger:** Subscribes to email list (pop-up, footer signup, landing page)
**NOT triggered by:** Purchase (that's post-purchase flow)
**Sequence:**
```
[Subscribe] โ Email 1 (Immediately)
โ [Wait 2 days]
โ Email 2 (Brand Story)
โ [Wait 2 days]
โ Email 3 (Social Proof)
โ [Conditional Split: Has placed order?]
โ YES โ Exit (enter post-purchase flow)
โ NO โ [Wait 3 days]
โ Email 4 (Urgency / Last Chance)
```
**Email 1 โ Welcome + Deliver Promise**
- Goal: Deliver the signup incentive, make a strong first impression
- Timing: Send immediately (within minutes of signup)
- Content: Welcome message, deliver discount/freebie, introduce brand briefly, one clear CTA to shop
- Design: Clean, brand-forward, hero image, single CRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product โ visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".