跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
效率与协作

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-specialist; not for writing each email''s copy — use email-creative-builder; not for computing EQS or the N1 unsubscribe veto — use email-quality-auditor. 邮件自动化流程设计/购物车挽回/流失召回序列

aaron-he-zhu · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add aaron-he-zhu/aaron-marketing-skills --skill email-sequence-designer

技能说明


name: email-sequence-designer slug: aaron-email-sequence-designer displayName: "Email Sequence Designer · 邮件自动化流程设计" summary: "邮件自动化流程设计/购物车挽回/流失召回序列" description: '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-specialist; not for writing each email''s copy — use email-creative-builder; not for computing EQS or the N1 unsubscribe veto — use email-quality-auditor. 邮件自动化流程设计/购物车挽回/流失召回序列' version: "20.1.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 designing or restructuring general email lifecycle automation before writing the individual emails: a welcome onboarding series, an abandoned-cart or browse-abandon flow, a post-purchase / replenishment sequence, a light in-flow re-engagement branch, a B2B cold-outbound multi-step sequence, or the program's overall frequency governance and sunset policy. Activate when the user has a lifecycle stage, trigger event, or list-fatigue problem and wants the flow map, cadence, and branch/exit logic before creative or send-testing begins. Not for the closed-loop win-back / re-consent (re-permission) program on a defined lapsed cohort — that self-contained recovery-or-retire program is reactivation-specialist's." argument-hint: " [platform/ESP] [trigger event] [audience/segment]" metadata: {"author": "aaron-he-zhu", "version": "20.1.0", "discipline": "email", "phase": "nurture", "geo-relevance": "low", "hermes": {"tags": ["marketing", "email", "nurture"], "category": "email"}, "openclaw": {"emoji": "✉️", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}

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's, and the preference-center / frequency-options design is preference-frequency-manager'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 unengaged segment is [X]% of the list and complaints are rising. Design a win-back sequence and a sunset policy with send caps and quiet hours.

Skill Contract

Expected output: a set of lifecycle flow maps (trigger, per-step timing, branch/exit conditions, goal per flow), a frequency-governance block (global send cap, quiet hours, fatigue guardrail), a re-engagement/sunset path, a SEND N dimension score with sub-item notes and the typed profile named, and the standard handoff summary.

  • Reads: the flow type or lifecycle goal, the trigger event, a versioned segment definition (from the user or from list-segment-builder when present), current consent/suppression snapshot refs, the versioned creative/HTML bindings for each step when available, an ESP flow/automation export (own data) and current cadence/complaint signals, and one SEND profile (promotional|retention|cold-outbound|newsletter).
  • Writes: a user-facing flow map + cadence plan and a reusable handoff summary to memory/email/email-sequence-designer/YYYY-MM-DD-<flow-or-goal>.md.
  • Promotes: chosen flow set, cadence/quiet-hours policy, sunset thresholds, the N-dimension score, and missing exports to memory/hot-cache.md and memory/open-loops.md; propose durable cadence/flow decisions as pending-decision items — never write decisions.md directly.
  • Done when: every flow has a trigger, per-step timing, a goal, and explicit branch/exit conditions; each step names the segment-definition version and exact creative/HTML version when available; a global send cap + quiet hours + a fatigue guardrail are specified; a re-engagement/sunset path exists; the SEND N score is emitted; and the output distinguishes local plan, ESP create result, send intent, and real send receipt.
  • Primary next skill: email-creative-builder to write each step, or email-quality-auditor to score the program and enforce N1.

Handoff Summary

Emit the standard shape from skill-contract.md §Handoff Summary Format.

Data Sources

Tier 1 works from the user's own inputs: the flow type, trigger event, and target segment pasted directly, plus a manual ~~email platform (ESP) flow/automation export for current cadence, step timing, and complaint/unsubscribe signals when available. Reuse ~~web analytics (GA4) for on-site behavior that seeds triggers

阅读完整来源 ↗