email-sequence-designer
Use when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound sequence"; produces general lifecycle automation flows (welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound) with trigger, step timing, branch/exit conditions, goal, frequency governance (send caps, quiet hours, fatigue guardrail), a sunset path, and a SEND N-dimension score. Not for the closed-loop win-back / re-consent (re-permission) program on a lapsed cohort — use reactivation-speci
npx skills add aaron-he-zhu/aaron-marketing-skills --skill email-sequence-designer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Email Sequence Designer Designs email lifecycle and automation flows plus the program's frequency governance, and scores the SEND **N (Nurture / Lifecycle)** dimension. It maps each flow's trigger, step timing, branch/exit conditions, and goal, layers a global cadence policy (send caps, quiet hours, fatigue guardrail) and a re-engagement/sunset path over the top, then hands the flow map to the skill that writes each step and to the auditor that scores the full program. It covers general lifecycle flows and owns the engagement-decay/sunset sub-item; the closed-loop win-back / re-consent (re-permission) program on a defined lapsed cohort is [reactivation-specialist](../reactivation-specialist/SKILL.md)'s, and the preference-center / frequency-options design is [preference-frequency-manager](../preference-frequency-manager/SKILL.md)'s. It does not write the individual email or compute the final EQS. ## Quick Start ``` Design a welcome flow for [product/audience] on [ESP]. Trigger is [signup event]; here is my current list/segment export: [paste/path]. ``` ``` Build an abandoned-cart sequence: [N] steps, [timing], with a discount branch and an exit-on-purchase condition. ``` ``` My u
- Quick Start
- Skill Contract
- Handoff Summary
- Data Sources
- Instructions
- Decision Gates
- Save Results
- Reference Materials
- Next Best Skill
What does the email-sequence-designer skill do?
Use when the user asks to "design a welcome flow", "set up an abandoned-cart sequence", "build a light re-engagement branch inside a lifecycle flow", or "plan a cold-outbound sequence"; produces general lifecycle automation flows (welcome, cart, browse-abandon, post-purchase, in-flow re-engagement, B2B cold outbound) with trigger, step timing, branch/exit conditions, goal, frequency governance (send caps, quiet hours, fatigue guardrail), a sunset path, and a SEND N-dimension score. Not for the closed-loop win-back / re-consent (re-permission) program on a lapsed cohort — use reactivation-speci
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill email-sequence-designer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.