Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
agricidaniel avatar

Ads Test

  • 2.3k installs
  • 7.6k repo stars
  • Updated July 13, 2026
  • agricidaniel/claude-ads

ads-test is a Claude Code skill that designs statistically valid A/B tests for paid advertising creatives, audiences, bidding, and landing pages before developers or marketers spend campaign budget.

About

ads-test is a Claude Code skill (v1.5, tested with Claude Code v2.x on 2026-05-17) from agricidaniel/claude-ads for paid-advertising experiment planning. It provides a structured hypothesis framework plus sample size, statistical significance, and test-duration calculators. Platform guides cover Meta Experiments, Google Experiments, and LinkedIn A/B setups for creatives, audiences, bidding strategies, and landing pages. Developers and growth engineers reach for ads-test when defining split tests, estimating required traffic, or documenting experiment design before enabling paid campaigns.

  • Structured hypothesis framework using IF-THEN-BECAUSE format
  • Built-in statistical significance calculator, sample size calculator, and test duration estimator
  • Platform-specific experiment setup guides for Meta Experiments, Google Experiments, and LinkedIn A/B
  • 5-step process covering hypothesis, calculations, setup, success criteria, and measurement plan
  • Hypothesis Quality Checklist that enforces single-variable isolation

Ads Test by the numbers

  • 2,296 all-time installs (skills.sh)
  • +503 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #221 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/agricidaniel/claude-ads --skill ads-test

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.3k
repo stars7.6k
Security audit3 / 3 scanners passed
Last updatedJuly 13, 2026
Repositoryagricidaniel/claude-ads

How do you design a statistically valid paid ad A/B test?

Design statistically valid A/B tests for ad creatives, audiences, bidding strategies, and landing pages before spending on paid campaigns.

Who is it for?

Developers or growth engineers planning paid-ad experiments on Meta, Google, or LinkedIn before spending budget.

Skip if: Teams needing live campaign management, creative production, or post-hoc analytics dashboards without upfront experiment design.

When should I use this skill?

The user mentions A/B test, split test, experiment design, statistical significance, sample size, or test duration for ads.

What you get

Experiment hypothesis document, sample-size calculation, duration estimate, and platform-specific test setup plan.

  • Experiment hypothesis doc
  • Sample-size calculation
  • Platform test setup plan

By the numbers

  • Skill version v1.5 with experiment planning workflow
  • Tested with Claude Code v2.x on 2026-05-17
  • Covers Meta, Google, and LinkedIn A/B experiment platforms

Files

SKILL.mdMarkdownGitHub ↗

A/B Test Design & Experiment Planning

<!-- Created: 2026-04-13 | v1.5 --> <!-- Source: OpenClaudia/openclaudia-skills (ab-test-setup concept) -->

Process

1. Understand what the user wants to test (creative, audience, bidding, landing page) 2. Build structured hypothesis using the framework below 3. Calculate required sample size and estimated duration 4. Recommend platform-specific test setup 5. Define success criteria and measurement plan

Hypothesis Framework

Every test must start with a structured hypothesis:

IF we [change/action]
THEN [metric] will [increase/decrease] by [estimated %]
BECAUSE [reasoning based on data or insight]

Example:
IF we replace polished product shots with UGC creator videos
THEN Meta CTR will increase by 25-40%
BECAUSE Andromeda prioritizes diverse creative formats and UGC consistently outperforms polished in 2025-2026 benchmarks

Hypothesis Quality Checklist

  • [ ] Single variable being tested (isolate the change)
  • [ ] Specific metric defined (not "performance")
  • [ ] Estimated effect size stated (needed for sample size calculation)
  • [ ] Timeframe defined
  • [ ] Success/failure criteria clear before launch

Statistical Significance Calculator

Required Sample Size (per variant):

n = (Z_alpha + Z_beta)^2 × 2 × p × (1-p) / MDE^2

Where:
- Z_alpha = 1.96 (for 95% confidence)
- Z_beta = 0.84 (for 80% power)
- p = baseline conversion rate
- MDE = minimum detectable effect (relative %)

Simplified lookup:
Baseline CVR5% MDE10% MDE20% MDE30% MDE
1%612,000153,00038,30017,000
2%302,40075,60018,9008,400
5%116,80029,2007,3003,200
10%55,20013,8003,4501,530
20%24,6006,1501,540680

Per variant, 95% confidence, 80% power

Test Duration Estimator

Duration = Required Sample Size / Daily Traffic per Variant

Minimum duration: 7 days (capture weekly patterns)
Maximum recommended: 28 days (avoid seasonal drift)
Learning phase: Google 7-14 days, Meta 3-7 days, LinkedIn 7-14 days

Inputs needed:
- Daily impressions or clicks
- Number of variants (2 = A/B, 3+ = multivariate)
- Baseline conversion rate
- Minimum detectable effect desired

Duration Quick Estimates

Daily Clicks2% CVR, 20% MDE5% CVR, 20% MDE10% CVR, 20% MDE
100189 days73 days35 days
50038 days15 days7 days
1,00019 days7 days4 days*
5,0004 days*2 days*1 day*

*Minimum 7 days recommended regardless of sample sufficiency

Platform-Specific Test Setup

Meta Experiments

  • Use Ads Manager > Experiments tab (not manual ad set duplication)
  • Automatic audience splitting ensures no overlap
  • Supported test types: A/B (creative, audience, placement), Holdout, Brand Survey
  • Meta's Incremental Attribution (April 2025) provides AI-powered holdout testing for measuring real causal impact
  • Budget: split evenly across variants; minimum $100/day per variant recommended
  • Duration: 7-14 days typical; Meta auto-determines winner at 95% confidence

Google Experiments

  • Campaign Experiments (custom experiments) or Ad Variations
  • Create experiment from existing campaign > select experiment type
  • Traffic split: 50/50 recommended for fastest results
  • Supported: bidding strategy, ad copy, landing page, audience
  • Metrics: choose primary metric (conversions, CPA, ROAS) before launch
  • Duration: 14-30 days recommended; minimum 2 weeks for bidding tests

LinkedIn A/B Testing

  • Built into Campaign Manager for Sponsored Content
  • Duplicate ad set with single variable change
  • Target: same audience segment with automatic rotation
  • Minimum budget: $50/day per variant
  • Key metrics: CTR (>0.44% benchmark), CPL, Lead Form CVR (13% benchmark)
  • Duration: 14-21 days (LinkedIn's smaller daily volumes require longer tests)

TikTok Split Testing

  • Available in TikTok Ads Manager > Create A/B Test
  • Test types: targeting, bidding, creative
  • Auto-splits audience to avoid contamination
  • Minimum 7 days, recommended 14 days
  • Budget: minimum $20/day per ad group
  • Creative tests: isolate hook (first 2-3 seconds) as the primary variable
  • TikTok's enhanced split testing supports modular test variables (targeting, creative, budget, placement) via Smart+ since 2025

What to Test (Priority Order)

High Impact (test first)

1. Creative concept (different messaging angles, not just color changes) 2. Hook/first 3 seconds (video opening on Meta, TikTok, YouTube) 3. Offer structure (pricing, discount type, free trial length) 4. Landing page (headline, CTA, form length) 5. Bidding strategy (tCPA vs tROAS vs Maximize Conversions)

Medium Impact

6. Audience targeting (interest vs lookalike vs broad) 7. Ad format (static vs video vs carousel) 8. CTA button (Learn More vs Sign Up vs Shop Now) 9. Campaign structure (CBO vs ABO, consolidated vs segmented)

Low Impact (test last)

10. Ad scheduling (time of day, day of week) 11. Device targeting (mobile vs desktop) 12. Minor copy variations (word substitutions without concept change)

Common Testing Mistakes to Avoid

  • Testing too many variables at once (no clear winner attribution)
  • Ending tests too early (before statistical significance)
  • Testing during atypical periods (holidays, launches, incidents)
  • Comparing unequal time periods
  • Not documenting learnings (build institutional knowledge)
  • Testing small changes when big changes are needed (optimize vs innovate)
  • Ignoring learning phase on automated platforms

Output Format

## A/B Test Plan

### Hypothesis
IF [change]
THEN [metric] will [direction] by [amount]
BECAUSE [reasoning]

### Test Design
| Parameter | Value |
|-----------|-------|
| Platform | [platform] |
| Test Type | [A/B / Multivariate] |
| Variable | [what's being changed] |
| Control | [current state] |
| Variant | [proposed change] |
| Primary Metric | [KPI] |
| Traffic Split | [50/50 / other] |

### Sample Size & Duration
| Metric | Value |
|--------|-------|
| Baseline CVR | [X%] |
| MDE | [X%] |
| Required Sample | [N per variant] |
| Daily Traffic | [N clicks/day] |
| Est. Duration | [X days] |
| Min Duration | 7 days |

### Success Criteria
- Winner declared at 95% confidence
- [Primary metric] improvement of [X%]+ sustained over [Y] days
- No negative impact on [secondary metric]

### Setup Instructions
[Platform-specific step-by-step]

Related skills

How it compares

Use ads-test for pre-launch experiment design and sample-size math; use analytics skills after campaigns run for performance reporting.

FAQ

Which ad platforms does ads-test support?

ads-test includes experiment setup guidance for Meta Experiments, Google Experiments, and LinkedIn A/B tests. It covers creatives, audiences, bidding strategies, and landing-page split tests.

What calculators does ads-test provide?

ads-test provides sample size, statistical significance, and test duration calculators alongside a structured hypothesis framework. Use it before launching paid campaigns to validate experiment scope.

Is Ads Test safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.