| name | list-segment-builder |
| slug | aaron-list-segment-builder |
| displayName | List Segment Builder · 邮件列表分群 |
| summary | 邮件列表分群/生命周期分群/抑制名单/流失召回 |
| description | Use when the user asks to "build email segments from my list", "make engaged / lapsed / RFM segments", "set up cart-abandoner or lifecycle-stage audiences", or "build a suppression list of unsubscribes and bounces"; turns the user's OWN list/CRM/GA4/ecommerce export into behavioral, attribute, and lifecycle-stage segments plus a suppression list, with per-segment sizes labeled Measured/Estimated, informing the SEND E (Engagement/targeting) dimension. Not for scoring EQS or running vetoes — use email-quality-auditor; not for authentication or spam-content checks — use deliverability-qa. 邮件列表分群/生命周期分群/抑制名单/流失召回 |
| version | 19.0.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when preparing WHO to email before any send is designed: segmenting an exported list/CRM/GA4/ecommerce export into behavioral segments (engaged-90d, cart-abandoners), RFM tiers, and lifecycle stages (new, active, lapsed, win-back), and building the suppression list (unsubscribed, hard-bounced, spam-complained, consent-withdrawn) by reading the consent-registry as the source of truth for consent and suppression facts. |
| argument-hint | <list/CRM CSV or GA4/ecommerce export> [goal: promo|retention|cold] [ESP] |
| metadata | {"author":"aaron-he-zhu","version":"19.0.0","discipline":"email","phase":"setup","geo-relevance":"low","hermes":{"tags":["marketing","email","setup"],"category":"email"},"openclaw":{"emoji":"✉️","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
List Segment Builder
Turns the user's own list/CRM/GA4/ecommerce export into behavioral segments (engaged-90d, cart-abandoners), attribute and RFM tiers, lifecycle-stage segments (new, active, lapsed, win-back), and a suppression list (unsubscribed, hard-bounced, spam-complained, consent-withdrawn). It defines who each segment is and who must never be mailed — email-creative-builder and email-sequence-designer then compose for those segments; this skill does not send, design flows, or score the program.
Quick Start
Build email segments from my list export: [path]. Goal is retention. ESP export attached.
Make engaged-90d, lapsed, and cart-abandoner segments from my ecommerce + ESP export, and give me the suppression list. [CSV]
Map my list to RFM tiers and lifecycle stages so I can reuse the same audiences across every campaign. [CRM export]
Skill Contract
Expected output: a segment map in four buckets — (1) behavioral segments grouped by activity (opened/clicked recency, cart-abandon, browse-abandon), (2) attribute + RFM tiers (recency/frequency/monetary from the user's own order data), (3) lifecycle-stage segments (new → active → at-risk → lapsed → win-back), and (4) a suppression list (unsubscribed, hard-bounced, spam-complained, consent-withdrawn) — each segment named with a size labeled Measured (counted from an exported column) or Estimated (inferred, method stated), informing the SEND E (Engagement/targeting) dimension, plus the standard handoff summary.
- Reads: the user's own list/CRM CSV (subscribe date, last-open/last-click date, opt-in status), ESP campaign export (opens/clicks per subscriber), GA4/ecommerce export (order recency, frequency, monetary value); the program goal (promo / retention / cold); and consent/suppression facts from the consent-registry (
memory/consent/).
- Writes: a user-facing segment map and reusable summary to
memory/email/list-segment-builder/.
- Promotes: the segment names, the lifecycle-stage map, the suppression-rule set, and any missing export to
memory/hot-cache.md and memory/open-loops.md; propose durable segment definitions as pending-decision items (never write consent records — the registry owns memory/consent/).
- Done when: each segment is named and grounded in an exported column; every size is labeled Measured or Estimated; RFM tiers use the user's own recency/frequency/monetary fields; the suppression list reconciles against the consent-registry (unsubscribed + hard-bounced + complained + consent-withdrawn) or flags NEEDS_INPUT where no consent record exists; and the SEND relevance of each bucket is noted.
