aaron-he-zhu/aaron-marketing-skills / email/engage/email-creative-builder
email-creative-builder
VerifiedUse when the user asks to "write the email", "draft subject lines", or "build email creative"; produces the pre-click unit — subject-line variants + preheader, body copy, one clear CTA, and a plain-text alt — message-matched to the destination page and claims-ledger-aware. Not for pre-scoring or ranking subject-line variants (spam/truncation/render pre-score) — use subject-line-lab; not for scoring the email or computing EQS — use email-quality-auditor; not for the multi-step flow — use email-sequence-designer; not for the A/B test plan — use send-experiment-designer. 邮件文案/主题行/邮件创意
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.3 KB |
| references/email-creative-modes.md | markdown | 2.9 KB |
| references/subject-line-specs.md | markdown | 1.9 KB |
references/email-creative-modes.md
View on GitHub# Email Creative Modes (SEND-E/D)
Three use-case pattern sets for `email-creative-builder`. Pick the mode that matches the program; the skill stays use-case-agnostic and the mode only changes the pattern, not the contract. All three end at the same **message-match map** so [email-quality-auditor](../../../deliver/email-quality-auditor/SKILL.md) can score the E/D unit and run the D1 claim veto.
## Mode A — Promotional / lifecycle (B2C)
- **Goal**: one action (buy, redeem, book). Single dominant CTA.
- **Structure**: hook → value/offer → proof (review, stat, guarantee) → CTA → urgency (honest deadline/stock only).
- **Offer**: pull terms + promo code + expiry from the live-offers table ([offer-claims-registry](../../../../protocol/offer-claims-registry/SKILL.md), `memory/claims/offers.md`) — never invent them.
- **Claims**: every product/benefit claim traces to an approved row in `memory/claims/claims-ledger.md`; unregistered → `[needs source]` → `memory/events/claims.ndjson` via an authorized `operation: propose` request to `registry-events.py`.
## Mode B — Cold outbound (B2B)
- **Goal**: a reply, not a click. One low-friction ask (interest-check / soft CTA).
- **Structure**: relevance line (why them, now) → one concrete value point → light social proof → single soft ask. Keep it short; plain-text feel.
- **Personalization**: one genuine, verifiable personalization token per message; no fabricated "I saw you…" specifics.
- **Compliance**: physical mailing address + a functioning opt-out honored within 10 business days (CAN-SPAM); the one-click `List-Unsubscribe` header is a Gmail/Yahoo bulk-sender rule (RFC 8058), not a CAN-SPAM statute. Consent/lawful-basis per recipient from [consent-registry](../../../../protocol/consent-registry/SKILL.md). Spintax/variants must not degrade into misleading claims.
## Mode C — Newsletter / creator
- **Goal**: sustained engagement + (where relevant) monetization. CTA may be read/forward/refer, not buy.
- **Structure**: subject promise → lead → 1–3 sections → clearly-labeled sponsorship (if any) → forward/refer ask.
- **Sponsorship = ad**: any paid placement gets an explicit disclosure; the offer/claim still routes through the claims ledger (D1). Monetization economics belong to [newsletter-monetization-planner](../../../nurture/newsletter-monetization-planner/SKILL.md).
## Message-match map (all modes — required output)
For each CTA, record the row so the auditor can verify email↔landing consistency:
| Email element | Says | Landing page must show | Match? |
|---|---|---|---|
| Subject/hook | <promise> | <same promise above the fold> | ✓ / ✗ |
| Offer | <terms/code> | <identical terms/code> | ✓ / ✗ |
| CTA label | <verb + object> | <same next step> | ✓ / ✗ |
A mismatch is a message-match failure (SEND-`D` sub-item) — flag it; the post-click fix is [landing-optimizer](../../../../influencer/report/landing-optimizer/SKILL.md).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |