send-experiment-designer
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测试设计/多变量测试/发送时间测试/留出组/显著性判定
aaron-he-zhu · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add aaron-he-zhu/aaron-marketing-skills --skill send-experiment-designer技能说明
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: "20.1.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": "20.1.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.
I have a 2×2 subject × CTA multivariate idea and a hold-out. Build the variant matrix, sample size per cell, and run duration. Baseline click 2.1%.
Here's my finished test export (variant, delivered, opens, clicks, conversions). Is the winner significant — promote or kill?
Output: a test-design doc (mode, hypothesis, variant matrix, primary/secondary/guardrail metrics, sample size + MDE + duration + power) and/or a read-out (effect/interval, statistical and practical flags, guardrails, and either an owner-governed recommendation or decision: UNDECIDED).
Skill Contract
- Reads: the mode, what the user wants to test, SEND profile (
promotional|retention|cold-outbound|newsletter), baseline outcome rate, list size/send volume, alpha, power, MDE, multiplicity/sequential rule, guardrails, decision owner/rule, the segment-definition and variant creative/HTML versions/hashes, and any finished ESP results export with matching send-receipt refs when available. - Writes: a user-facing test-design or read-out doc plus a
### Handoff Summary. - Promotes: the chosen mode, hypothesis, design parameters, calculated read-out, and any explicitly owner-approved action (ask before writing memory).
- Done when: mode/unit/profile and design parameters are stated; the matrix isolates one variable per cell and keeps a control; the measurement contract binds the segment-definition version and exact variant hashes; and a read-out binds results to send receipts or explicitly reports the receipt gap, then reports effect/interval/statistical/practical flags with
Calculatedprovenance. Without a precommitted action rule and owner, returndecision: UNDECIDED. - Primary next skill: email-quality-auditor — gate the receipt-bound program before scaling any owner-approved direction.
Handoff Summary
Emit the standard shape from skill-contract.md §Handoff Summary Format: Status / Objective / Key Findings / Evidence (label each Measured / User-provided / Estimated) / Assumptions / Open Loops / Recommended Next Skill.
Data Sources
阅读完整来源 ↗See CONNECTORS.md for tool category placeholders. Every input is the user's **own data