Email Lifecycle Flow Designer
Map lifecycle email flows, cadence, branching, exits, and sunset rules before writing the emails.
The skill treats exports as untrusted data, forbids enrollment of suppressed or non-consented subjects, and requires Resend mutations to be dry-run by default with an explicit user-approved --live escalation. These support least privilege, data-flow transparency, and external-effect control. Points are deducted because authorization boundaries for memory writes, rollback/recovery after failure, and third-party ESP data handling are not fully specified; publisher identity is also unverified.
The contract, done criteria, stop conditions, and abnormal-input guidance are fairly specific, with coherent trigger, branch, exit, and frequency-governance logic. Points are deducted because this is a static review with no skill-specific key-path tests, reproducible execution evidence, or comprehensive diagnostic error behavior; the static ceiling therefore prevents a score above 10.
Triggers, inputs, outputs, non-fit boundaries, routing, and bilingual descriptions are clear, and the Tier-1 path does not require paid tools or MCP services. Points are deducted because evidence for ESP-specific behavior, regional compliance, Chinese operational contexts, and mainland-China network reachability is limited, while some activation capability can depend on an external email platform.
The skill follows a consistent Quick Start, Contract, Data Sources, Instructions, and Next Best Skill structure, and declares Apache-2.0, version, compatible hosts, naming, and references. Points are deducted because it lacks a complete representative output, FAQ, changelog, or explicit maintenance owner; SECURITY.md still lists 17.x as supported while the skill and README state 18.0.0, indicating governance inconsistency.
The skill specifies lifecycle maps, timing, branching and exit logic, frequency controls, sunset handling, and a SEND N score, which should be directly useful for planning email automation. Points are deducted because the supplied files contain no actual skill output, end-to-end result, or comparative evidence; execution still requires user-supplied trigger, segment, ESP, and creative context, so static evidence supports only limited utility.
The source includes a structured contract, referenced materials, version metadata, and repository-level CI and validator tests, providing some auditability. Points are deducted because those tests mainly cover shared architecture and audit artifacts, not this skill's key flow-design, SEND N scoring, or Resend paths; there is no independent review or verifiable execution evidence.
- Do not treat the generated flow map or SEND N score as a validated sending plan; independently verify consent, suppression, unsubscribe, bounce handling, and ESP configuration before sending.
- Resend --live changes external email state; require review of the dry-run preview and an explicit cancellation or recovery plan before execution.
- Resolve the 17.x versus 18.0.0 support-version mismatch and add skill-specific tests, representative outputs, and an explicit maintenance owner.
What does this skill do, and when should you use it?
This skill designs general email lifecycle automation flows, including welcome, abandoned-cart, browse-abandon, post-purchase, light in-flow re-engagement, and B2B cold-outbound sequences. It defines triggers, step timing, goals, branch logic, exit conditions, global send caps, quiet hours, fatigue guardrails, and a sunset path. It also scores the SEND N dimension but does not calculate the final EQS. It fits teams that need a governed flow map before creative production or send testing.
Reads the requested flow or lifecycle goal, trigger event, audience segment, ESP exports, and available cadence or complaint signals; inventories core lifecycle flows; designs ordered steps with delays, goals, branches, and exits; defines global frequency governance, quiet hours, fatigue protection, and re-engagement/sunset rules; selects one SEND profile—promotional, retention, cold-outbound, or newsletter—and emits an N-dimension score, flow map, cadence plan, and handoff summary. Optional data paths include ESP, web analytics, ecommerce, and MCP sources. The Resend connector can schedule broadcasts with dry-run defaults.
- An ecommerce team needs a welcome series for new signups with clear triggers, delays, and purchase exits.
- A lifecycle marketer needs an abandoned-cart or browse-abandon flow with click branches and conversion exits.
- A subscription business sees rising disengagement and needs an in-flow re-engagement touch plus sunset policy.
- A B2B team needs a multi-step cold-outbound sequence with reply-based exits.
- An email owner needs global send caps, quiet hours, and fatigue controls across several automations.
What are this skill's strengths and limitations?
- Covers multiple general lifecycle flows with explicit triggers, timing, goals, branches, and exits.
- Includes cross-flow send caps, quiet hours, fatigue guardrails, and an engagement-decay sunset path.
- Uses four typed SEND profiles and emits an N-dimension score with handoff information.
- Works from user-provided Tier 1 data; connectors and MCP access are optional.
- Does not write individual email subject lines, bodies, or CTAs, and does not calculate final EQS or enforce audit vetoes.
- Closed-loop win-back/re-consent and preference-center design belong to separate skills.
- The documented Resend activation path depends on repository scripts, Python, and filesystem access; no detailed compatibility matrix for other ESPs is provided.
- The source provides no standalone test results for this individual skill.
How do you install this skill?
This skill is included in the aaron-he-zhu/aaron-marketing-skills collection. In Claude Code, run /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, then /plugin install aaron-marketing@aaron. On other Agent Skills-compatible hosts, run npx skills add aaron-he-zhu/aaron-marketing-skills, or clone the repository directly. The source does not document a standalone installation command for this individual skill.
How do you use this skill?
Provide a flow type or lifecycle goal, ESP, trigger event, and audience segment. Example: Design a welcome flow for [product/audience] on [ESP]. Trigger is [signup event]; here is my current list/segment export: [paste/path]. The skill confirms one SEND profile, then produces flow maps, frequency governance, a sunset path, and an N score. It proceeds without an ESP export, marking current-cadence findings N/A; it pauses only when the trigger or target segment cannot reasonably be determined.