aiskillstore/marketplace / skills/aaron-he-zhu/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 | 11.5 KB |
| references/email-creative-modes.md | markdown | 2.9 KB |
| references/subject-line-specs.md | markdown | 1.9 KB |
| skill-report.json | config | 44.7 KB |
references/subject-line-specs.md
View on GitHub# Subject Line & Preheader Specs
Render limits and variant-labeling for `email-creative-builder`, so the subjects it drafts carry cleanly into [send-experiment-designer](../../../deliver/send-experiment-designer/SKILL.md). Numbers are practical inbox-render limits, not hard protocol limits — treat them as guidance labeled Estimated.
## Render limits (characters before truncation)
| Surface | Desktop | Mobile | Guidance |
|---|---|---|---|
| **Subject line** | ~60 | ~30–40 | Front-load the promise in the first ~30 chars; mobile truncates hardest |
| **Preheader** | ~90–110 | ~40–50 | Extends (never repeats) the subject; set it explicitly or the client pulls body text |
| **From name** | ~20 | ~20 | Recognizable sender; consistency drives opens |
## Variant set (draft 3–5, one angle each)
Label each variant so it maps to a test cell:
| Angle | Pattern | Example shape |
|---|---|---|
| Curiosity | open loop, withhold | "The one thing we changed…" |
| Benefit | lead with outcome | "Cut your setup time in half" |
| Offer | lead with the deal (promo mode) | "24 hours: 20% off everything" |
| Personalization | genuine, verifiable token | "{first_name}, your {plan} renews soon" |
| Question | provoke a mental yes | "Still exporting reports by hand?" |
## Rules
- **One variable per test cell** — if testing subjects, hold preheader/creative/send-time constant (isolation is enforced by [send-experiment-designer](../../../deliver/send-experiment-designer/SKILL.md)).
- No spam-trigger patterns: no ALL-CAPS, no `!!!`, no misleading "RE:"/"FWD:" fakery, no false scarcity. These also fail the [deliverability-qa](../../../setup/deliverability-qa/SKILL.md) spam-content scan.
- Emoji: at most one, only if on-brand; never in cold-outbound (B2B) subjects.
- Label the output so each subject+preheader pair carries a stable variant id (`SUBJ-A`, `SUBJ-B`, …) into the test.
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 |