creative-test-readout

$npx mdskill add Significant-Gravitas/skills-catalog/creative-test-readout

Use this for one test between two or more ad variants.

SKILL.md

.github/skills/creative-test-readoutView on GitHub ↗
---
name: "creative-test-readout"
description: "Read an ad test by sample size and spread, and say whether there is a winner yet."
triggers: ["ad test results", "A/B test ads", "creative test", "which ad won", "test readout"]
version: "1"
---

# Creative test readout

Use this for one test between two or more ad variants.

## Check the setup

State what was tested, the one idea that differs, the dates, the audience,
and the measure agreed before the test began. Check that variants got a fair
share of spend, ran over the same days, and pointed to the same page. If the
setup was uneven, say so first. For more than two variants, name the one
comparison set before the test, or choose a method that accounts for all
comparisons.

## Read the result

For each variant show impressions, clicks, conversions, spend, and the rate
being judged. Give the gap between variants and whether it is larger than
the noise at this sample size. Use a stated method and show it. Before calling
a winner, state the baseline rate, minimum effect worth detecting, power, and
confidence level used to estimate the required sample.
For more than two variants, call a winner only for the comparison set before
the test, or after using and showing a test that accounts for all comparisons.

Say one of:

- **clear winner**, with the margin and sample;
- **leaning**, not yet safe to act on;
- **not enough data**, with the sample still needed and how many days that
  takes at current spend.

## Decision and next test

Recommend keep running, stop, or roll out, and the next idea worth testing.

Do not pause, scale, or edit ads yourself; recommend for approval. Never call
a winner early or invent figures to fill a thin test.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.