email-creative-builder

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: email-creative-builder
slug: aaron-email-creative-builder
displayName: "Email Creative Builder · 邮件文案"
summary: "邮件文案/主题行/邮件创意"
description: 'Use 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. 邮件文案/主题行/邮件创意'
version: "19.2.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 drafting or iterating a single email creative: subject-line variants and preheader, body copy, one primary CTA, and a plain-text alternate, kept message-matched to a destination landing page and traced to approved claim wording. Covers B2C promo/lifecycle, B2B cold-outbound personalization, and newsletter modes."
argument-hint: "<offer/topic> <destination URL> [mode: promo|cold|newsletter]"
metadata: {"author": "aaron-he-zhu", "version": "19.2.0", "discipline": "email", "phase": "engage", "geo-relevance": "low", "hermes": {"tags": ["marketing", "email", "engage"], "category": "email"}, "openclaw": {"emoji": "✉️", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
---

# Email Creative Builder

Writes and iterates a single email creative — subject-line variants + preheader, body copy, one clear CTA, and a plain-text alternate — each message-matched to the destination landing page and traced to approved claim wording. This is the build skill that produces the SEND **E/D** unit (the email analog of paid's ad-creative-builder). It does not score the email, run the D1 veto, or compute the EQS — that is `email-quality-auditor` — and it does not design the multi-step flow (`email-sequence-designer`) or the test (`send-experiment-designer`).

**Scope guard**: this skill builds the creative unit + message-match + claim flags only. It drafts subject-line variants for the creative but does **not** pre-score or rank them (spam-trigger flags, length/truncation, emoji-count, inbox-preview render) — that is [subject-line-lab](../subject-line-lab/SKILL.md). It scores no SEND dimension, runs no veto, and does not compute the profile-weighted EQS — [email-quality-auditor](../../deliver/email-quality-auditor/SKILL.md) owns all four vetoes (S1/S2/N1/D1) and the EQS rollup.

## Quick Start

```
Write 5 subject lines + preheader + body + CTA for [offer], destination [URL], promo mode
```

```
Draft a cold-outbound email to [persona] for [offer]; personalize on [signal]; destination [URL]
```

```
Iterate these losing subject lines: [paste]. Keep the winners, replace the rest, hold message-match to [URL].
```

## Skill Contract

**Expected output**: one ready-to-send email creative — 3-5 subject-line variants, a preheader, structured body copy, a single primary CTA, and a plain-text alternate — with a per-claim message-match note to the destination URL and any `[needs source]` flags, plus the standard handoff summary for `memory/email/email-creative-builder/`.

- **Reads**: the offer/topic, destination, email mode, audience/lifecycle stage, existing copy, `memory/projections/narrative.json`, `memory/projections/claims.json`, and the live consent/suppression state required by the selected flow.
- **Writes**: a user-facing email creative and, with permission, a WARM artifact; unresolved claims become authorized proposal events, never direct ledger edits.
- **Done when**: subject/preheader fit declared render limits, the body has one primary CTA, plain text exists, claims/disclosures are accepted and context-valid or v