xiaohongshu
xiaohongshu
marketing-email-automation
Email marketing automation for HubSpot/Klaviyo/Mailchimp (and similar ESPs): design trigger-based lifecycle workflows (welcome, onboarding, nurture, win-back, cart abandonment), define segmentation + suppression/frequency policies, troubleshoot deliverability (SPF/DKIM/DMARC, one-click unsubscrib...
Full skill instructions
Built as a no-fluff execution skill for designing and operating revenue-safe, deliverability-safe email automation across B2B and B2C.
Structure: Core workflows and segmentation in SKILL.md. Platform setup in references/. Revenue economics in references/email-economics.md. Templates in assets/.
Scope note: For outbound/cold email, see marketing-leads-generation. For email HTML/CSS implementation, use a coding-focused workflow (this skill is strategy + operations).
Operational reality in 2026:
References:
data/sources.jsonreferences/deliverability.mdreferences/accessibility.mdUse this to avoid "scheduled campaigns in disguise."
Organizational failure mode when automation is treated as scheduled campaigns:
Lifecycle stages are not CRM labels. A lifecycle stage is a set of constraints that implies:
Define stages by:
Stage transitions should be driven by observable behavior and system events (product, billing, support, sales), not time.
Examples (event-level, platform-agnostic):
Strategically wrong signal that looks correct:
Branch only when the best next action materially changes due to:
Collapse logic when differences are cosmetic and can be handled by:
Automation complexity is harming performance when:
Early warning sign of unmaintainable automation:
Platform-agnostic decisions (must be stable even if you switch tools):
Legitimately platform-dependent decisions:
Common mistake from over-trusting platform "best practices":
| Workflow Type | Trigger | Purpose | Timeline |
|---|---|---|---|
| New subscriber / opt-in | Consent captured | Set expectations, route to intent path | Day 0-7 |
| New customer / start | First purchase / start | Drive first value loop | Day 0-30 |
| Decision support | Intent signal | Reduce decision risk, progress to commitment | Weeks 1-8 |
| Abandoned Cart | Cart created, no purchase | Recover revenue | Hours 1-72 |
| Re-engagement | Inactive subscriber | Win back or clean list | Day 30-90 |
| Upsell/Cross-sell | Purchase complete | Increase LTV | Day 7-30 post-purchase |
| Renewal/Retention | Subscription nearing end | Prevent churn | Day -30 to -1 |
WORKFLOW: [Name]
TRIGGER: [Event that starts flow]
GOAL: [Primary conversion action]
DURATION: [Total time span]
ENTRY → STEP 1 → WAIT → BRANCH (state A/state B) → STEP 2 → ... → EXIT
Exit when: Goal met | Unsubscribe | Time limit reached
See assets/workflow-blueprint.md for full template.
What nurture is actually optimizing for:
Why most nurture fails even with good content:
How nurture changes once product or sales signals exist:
Optional scaffolds (if you need examples, not copy guidance):
| Segment | Definition | Use For |
|---|---|---|
| Engaged | Clicked (or took downstream action) in last 30 days | Primary campaigns |
| Active | Logged in / used product recently | Onboarding, upsell |
| At-risk | No engagement 31-60 days | Re-engagement |
| Dormant | No engagement 61-90 days | Win-back |
| Churned | No engagement 90+ days | Sunset or remove |
| Segment | Recency | Frequency | Monetary | Strategy |
|---|---|---|---|---|
| Champions | Recent | Often | High | Reward, refer |
| Loyal | Recent | Often | Medium | Upsell |
| Potential | Recent | Rare | Low | Nurture |
| At Risk | Old | Often | High | Win back |
| Hibernating | Old | Rare | Low | Re-engage or remove |
Zero-party data = information users explicitly and voluntarily provide (preferences, intentions, feedback). Unlike behavioral data, this comes directly from the user's stated intent.
Why it matters (2026):
Collection methods:
| Method | Example | Best For |
|---|---|---|
| Preference centers | Content frequency, topic interests, channel preferences | List health, relevance |
| Progressive profiling | Ask 1-2 questions per touchpoint over time | Low friction, high completion |
| Surveys/quizzes | Gamified "find your style" or product match | Engagement + data capture |
| Onboarding questions | Role, company size, goals during signup | B2B segmentation |
| Post-purchase feedback | "How did you hear about us?" | Attribution clarity |
Implementation principles:
Dynamic content from zero-party data:
Deliverability is three coupled systems:
One action that improves short-term performance but harms long-term deliverability:
AI capabilities are mainstream. Treat them as accelerators, not substitutes for measurement, consent, and deliverability hygiene.
Production-ready AI capabilities:
| Capability | What It Does | When to Use |
|---|---|---|
| Send time optimization | Predicts best send time per recipient | High-volume campaigns, engagement optimization |
| Subject line generation | AI-generated variants for testing | A/B testing, creative scaling |
| Content personalization | Dynamic blocks based on behavior + preferences | Nurture sequences, product recommendations |
| Predictive segmentation | Identifies churn risk, purchase likelihood | Retention, upsell targeting |
| Copy generation | Full email drafts from prompts | Campaign scaling, first drafts |
Guardrails (non-negotiable):
Autonomous campaigns (emerging):
Warning: AI can optimize for surface metrics (opens, clicks) while degrading system outcomes (deliverability, retention, margin). Always validate with downstream outcomes.
AVOID Over-automation without controls: Complex flows without monitoring and suppression eventually damage reputation. Review automation performance monthly and retire stale logic.
Use references/deliverability.md for the full compliance checklist (including BIMI and enforcement status). Use assets/email-audit.md for audits.
Why last-touch attribution fails for automation:
How experts estimate email contribution without overclaiming:
Attribution signal to trust more than dashboards:
Use references/email-economics.md for attribution models, RPE framework, segment economics, churn reduction ROI, and channel mix decisions.
How automation contributes:
Use metrics to detect system health, not to "win the dashboard":
Retention-related email metric that can look positive while the business degrades:
See references/email-economics.md for definitions and calculations.
| Template | Purpose |
|---|---|
| workflow-blueprint.md | Design any workflow |
| welcome-sequence.md | New subscriber welcome |
| nurture-sequence.md | Lead nurturing |
| cart-abandonment.md | E-commerce recovery |
| email-audit.md | Health check template |
| email-roi-calculator.md | ROI calculation |
AMP for Email enables in-email actions without leaving the inbox. Users can complete forms, browse carousels, submit reviews, and update preferences directly in the message.
Adoption status (2026):
Interactive elements and use cases:
| Element | Use Case |
|---|---|
| Forms | Surveys, reviews, preference updates |
| Carousels | Product browsing, feature highlights |
| Accordions | FAQ, detailed specs, terms |
| Live data | Inventory counts, pricing, appointment slots |
| Checkout | One-click purchase, cart updates |
Implementation requirements:
When to use AMP:
When NOT to use AMP:
Fallback requirement: Always provide HTML fallback. AMP is progressive enhancement, not replacement.
Testing: Use Litmus, Email on Acid, or Gmail's AMP Playground to validate rendering across clients.
Email automation supports CRO when it:
Email automation conflicts with CRO when it:
Optimization mistake that improves email metrics but reduces funnel efficiency:
Three statements that signal non-expert operation:
Complaints rising (or inbox placement dropping)?
├─ Suppress unengaged; tighten eligibility
├─ Reduce frequency; add global caps
└─ Audit list sources + consent + auth alignment
Bounces rising?
├─ Remove hard bounces immediately
├─ Fix list acquisition hygiene (double opt-in where appropriate)
└─ Verify infrastructure and authentication
Clicks/actions down but deliverability stable?
├─ Stage mismatch: rebuild lifecycle entry/exit rules
├─ Route mismatch: coordinate with product/sales/support signals
└─ Validate impact with holdouts; do not "add more emails" first
Revenue up but retention/margin down?
└─ Incentive training or low-LTV acquisition: tighten segmentation and protect pricing integrity
| Anti-Pattern | Instead |
|---|---|
| Batch-and-blast | Segment and trigger |
| No segmentation | Behavioral segments |
| Multiple competing goals | One primary outcome per message |
| Ignoring mobile constraints | Mobile constraints first (tap targets, load, readability) |
| Buying lists | Build organically |
| Set-and-forget automations | Monthly performance reviews |
| Relying on open rates | Use click rate, conversions, revenue |
This skill uses US/UK market defaults. For international email marketing:
| Need | See Skill |
|---|---|
| Regional compliance (CASL, LGPD, PIPL) | marketing-geo-localization |
| Regional send time optimization | marketing-geo-localization |
| Cultural messaging adaptation | marketing-geo-localization |
| Alternative channels (WhatsApp, LINE, WeChat) | marketing-geo-localization |
Auto-triggers: When your query mentions a specific country, region, or compliance framework, both skills load automatically.
references/email-economics.mdxiaohongshu
technical spec
product ux expert
database patterns
Conduct multi-agent task orchestration and workflow coordination.
Initialize project with Conductor artifacts (product definition,
Expert in web animations, transitions, and motion design using Framer Motion and CSS
Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...
PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.
Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...
Display project status, active tracks, and next actions
Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience