| name | send-experiment-designer |
| slug | aaron-send-experiment-designer |
| displayName | Send Experiment Designer · 邮件AB测试设计 |
| summary | 邮件AB测试设计/多变量测试/发送时间测试/留出组/显著性判定 |
| description | Use when the user asks to "design an email A/B test", "set up a multivariate subject/CTA test", "run a send-time test", "build a hold-out group", or "is this email result statistically and practically material?"; produces a falsifiable hypothesis, one-variable-per-cell matrix, sample-size/MDE/duration/power plan, and an effect/uncertainty read from own ESP data. Applies only a precommitted owner-approved action rule; the helper never chooses a business action. Not for EQS/vetoes or writing the email. 邮件AB测试设计/多变量测试/发送时间测试/留出组/显著性判定 |
| 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 designing an email A/B, multivariate, send-time, or hold-out experiment, or when reading effect size, uncertainty, and guardrails from a finished ESP export. Apply an action only under a precommitted rule with a named owner; otherwise return decision UNDECIDED. Not for EQS/vetoes or writing the email. |
| argument-hint | <what to test / results export> [mode: a-b|multivariate|send-time|hold-out] [profile: promotional|retention|cold-outbound|newsletter] [baseline] [alpha/power/MDE] |
| metadata | {"author":"aaron-he-zhu","version":"19.2.0","discipline":"email","phase":"deliver","geo-relevance":"low","hermes":{"tags":["marketing","email","deliver"],"category":"email"},"openclaw":{"emoji":"✉️","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Send Experiment Designer
Designs email experiments across four modes and reads them out: a falsifiable hypothesis, a variant matrix that isolates one variable per cell, a sample-size / minimum-detectable-effect / run-duration / power plan, and a documented effect/uncertainty read. It may apply an owner-approved precommitted action rule, but statistical output alone never chooses a business action.
Mode set (pick one):
| Mode | Isolated variable | Primary metric |
|---|
a-b | one change — subject or preheader or CTA or creative | open (subject) / click / CTOR (CTA/creative) |
multivariate | 2+ factors crossed (e.g. subject × CTA), one variable per cell | the goal metric, powered per cell |
send-time | deploy hour/day; subject, segment, creative held constant | same-window engagement (open/click) |
hold-out | send vs no-send (randomized control receives nothing / current default) | conversion or revenue-per-recipient (incremental lift) |
Default the mode from the request when it is unambiguous (e.g. "test two subject lines" → a-b, "best hour to send" → send-time, "measure incremental revenue" → hold-out); state the picked mode back and proceed.
Scope guard: this skill owns email experiment design + the significance read only. It scores the SEND E (Engagement) lever as a test signal — it does not compute the profile-weighted EQS or run the S1/S2/N1/D1 vetoes (email-quality-auditor does), and it does not write the subject/preheader/body/CTA under test (email-creative-builder does). Design here, produce there, gate there.
Quick Start
Design an A/B subject-line test. Baseline open rate is 38%, I want to detect a 3-point lift. Goal is retention, list is 12,000.
Send-time test: what's the best hour to deploy my weekly newsletter? Baseline open 40%, list 20,000.
