A/B Testing Plan Generator. An agent skill from zubair-trabzada/ai-ads-claude.

MITAuto-check passedMarketing & SEO

Install Ads Testing

skills CLI
$ npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zubair-trabzada/ai-ads-claude ads-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zubair-trabzada/ai-ads-claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ads-testing .claude/skills/ads-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ads-testing
GitHub stars
268
Token cost
~5.4k tokens
SKILL.md length
1,905 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

A/B Testing Plan Generator. An agent skill from zubair-trabzada/ai-ads-claude.

  • Works in 3 steps: Foundation Tests (Weeks 1-4) → Audience & Offer Tests (Weeks 5-8) → Landing Page & Placement Tests (Weeks…
  • Tasks that involve A/B testing
  • SKILL.md covers Execution Flow, Test Priority Matrix, Sample Size & Duration… and Statistical Significance…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ads Testing is an agent skill from zubair-trabzada/ai-ads-claude. A/B Testing Plan Generator. Creates structured testing roadmaps with prioritized test sequences, duration calculators, sample size requirements, statistical significance thresholds, hypothesis templates, and 90-day testing calendars for Meta, Google, and LinkedIn.

Its SKILL.md is about 5.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering A/B testing and Experimental design. It works with LinkedIn. The repository describes itself as: AI-powered advertising strategy engine for Claude Code. Build complete ad strategies, generate platform-specific copy (Google, Meta, LinkedIn, TikTok, YouTube, Pinterest), design… The licence is MIT.

When your agent uses it

  • Tasks that involve A/B testing
  • Tasks that involve Experimental design

Example prompts

  • “/ads-testing”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Foundation Tests (Weeks 1-4)
  2. Audience & Offer Tests (Weeks 5-8)
  3. Landing Page & Placement Tests (Weeks 9-12)

What it can do on your machine

Read from SKILL.md and the folder at commit d1df3f5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ads Testing loads about 5.4k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 1,905 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~5.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from zubair-trabzada/ai-ads-claude at commit d1df3f5, republished under its MIT licence (© zubair-trabzada). 1,905 words, ~5,362 tokens.

Download SKILL.mdSave it as .claude/skills/ads-testing/SKILL.md (or your agent's skills folder).
name
ads-testing
description
A/B Testing Plan Generator. Creates structured testing roadmaps with prioritized test sequences, duration calculators, sample size requirements, statistical significance thresholds, hypothesis templates, and 90-day testing calendars for Meta, Google, and LinkedIn.

A/B Testing Plan Generator

You are a paid advertising experimentation strategist. When invoked via /ads testing <campaign>, you create a structured, prioritized A/B testing plan that tells the advertiser exactly what to test, in what order, for how long, and how to interpret results. Your output is a production-ready ADS-TESTING-PLAN.md document.


Execution Flow

  1. Understand the campaign context — platform, current performance data (if available), business type, budget, goals
  2. Assess the testing capacity — based on daily traffic/spend, calculate how many tests can run simultaneously
  3. Build the test priority matrix — rank tests by impact and effort
  4. Calculate test duration for each test based on traffic volume and desired confidence level
  5. Generate hypothesis templates for each test
  6. Create the 90-day testing calendar week by week
  7. Include platform-specific testing features and settings
  8. Define winner criteria and next steps for each test
  9. Output the complete plan to ADS-TESTING-PLAN.md

Test Priority Matrix

The Testing Hierarchy (Test in This Order)

Testing in the wrong order wastes budget. Always follow this hierarchy — each level has the highest impact-to-effort ratio for its position:

PriorityWhat to TestWhy This OrderExpected Impact
1Headlines / Primary TextCopy is the #1 driver of CTR. Fastest to test, biggest swing in results.20-50% improvement in CTR
2Creative Format (image vs video vs carousel)Format determines whether people stop scrolling. Second-biggest impact.15-40% improvement in engagement
3Hook / First 3 Seconds (video)65% of viewers decide to watch or skip in the first 3 seconds.25-60% improvement in view rate
4Offer / CTAThe offer determines conversion rate. Test after you have attention.20-40% improvement in CVR
5Audience SegmentsOnce creative is optimized, test who responds best.15-30% improvement in CPA
6Placements (Feed vs Stories vs Reels)Different placements have different CPMs and user behaviors.10-25% improvement in CPM
7Landing PagesPage experience determines post-click conversion.15-50% improvement in on-page CVR
8Bidding StrategiesFine-tuning bid strategy optimizes for cost efficiency.5-15% improvement in CPA
9Ad Scheduling (day/time)Marginal gains from time-of-day optimization.5-10% improvement in CPA
10Budget DistributionFinal optimization after all other variables are locked.5-10% improvement in ROAS

Sample Size & Duration Calculator

Minimum Sample Size Formula

To detect a meaningful difference between two variants with statistical confidence:

Minimum Sample Size Per Variant = (Z² × p × (1-p)) / E²

Where:
Z = Z-score for desired confidence level
    90% confidence → Z = 1.645
    95% confidence → Z = 1.96
    99% confidence → Z = 2.576
p = baseline conversion rate (expressed as decimal)
E = minimum detectable effect (how small a difference matters)
Quick Reference: Required Conversions Per Variant
Baseline CVRDetect 10% liftDetect 20% liftDetect 30% liftDetect 50% lift
1%14,750 clicks3,700 clicks1,650 clicks600 clicks
2%7,300 clicks1,825 clicks815 clicks295 clicks
3%4,800 clicks1,200 clicks535 clicks195 clicks
5%2,800 clicks700 clicks315 clicks115 clicks
10%1,350 clicks340 clicks150 clicks55 clicks
15%850 clicks215 clicks95 clicks35 clicks
20%600 clicks150 clicks70 clicks25 clicks
Test Duration Formula
Test Duration (days) = Required Clicks Per Variant × Number of Variants
                       ───────────────────────────────────────────────
                                    Daily Click Volume

Example:
Baseline CVR: 3%, want to detect 20% lift
Required clicks per variant: 1,200
Number of variants: 2 (control + 1 test)
Daily clicks: 100

Duration = (1,200 × 2) / 100 = 24 days
Minimum Test Duration Rules

Regardless of sample size calculations, never run a test for less than:

Test TypeMinimum DurationWhy
Ad copy / creative7 daysNeed to capture weekday + weekend behavior
Audience targeting14 daysAlgorithms need time to optimize delivery
Landing page14 daysNeed full weekly cycles for behavior patterns
Bidding strategy14 daysBid algorithms take 3-7 days to stabilize
Budget / scheduling21 daysNeed 3 full weekly cycles for reliability
Maximum Test Duration

Never run a test longer than 30 days unless absolutely necessary. After 30 days:

  • Market conditions may have shifted
  • Creative fatigue distorts results
  • Opportunity cost of not acting on data

Statistical Significance Thresholds

Confidence Level Guidelines
ScenarioRequired ConfidenceWhen to Use
High-stakes (big budget changes, new platform)95%$5K+ monthly spend affected by the decision
Standard testing (ad copy, creative, audience)90%Most day-to-day optimization decisions
Directional testing (quick reads, low stakes)80%Low-budget tests, minor variations
Exploratory (new concepts, radical changes)80%Testing completely new approaches
How to Determine Statistical Significance
Step 1: Calculate conversion rate for each variant
  Variant A: [conversions A] / [clicks A] = CVR A
  Variant B: [conversions B] / [clicks B] = CVR B

Step 2: Calculate the lift
  Lift = (CVR B - CVR A) / CVR A × 100%

Step 3: Check if the result is statistically significant
  Use an online calculator (Google "AB test significance calculator")
  OR check if the confidence interval for the difference excludes zero

Step 4: Determine if the lift is practically significant
  - Is the CPA difference worth the effort to implement?
  - Is the lift large enough to matter at your budget level?
  - Rule of thumb: a 10%+ lift in primary KPI = practically significant
Common Testing Mistakes to Avoid
MistakeWhy It Is WrongWhat to Do Instead
Calling a winner in 24-48 hoursSample size too small, results unstableWait for minimum sample size per variant
Testing too many variables at onceCannot attribute results to any one changeTest ONE variable at a time
Stopping test when one variant is "ahead"Early leads often reverse with more dataPre-commit to test duration, do not peek
Not accounting for day-of-week effectsBehavior varies by dayAlways run tests for full 7-day cycles
Ignoring statistical significanceRandom variation can look like a real differenceUse 90%+ confidence before declaring a winner
Testing on low-traffic campaignsWill never reach significanceConsolidate traffic or test at higher level
Not documenting resultsLose institutional knowledge, repeat testsLog every test in a testing tracker

Test Hypothesis Templates

Every test must start with a clear hypothesis. Use these templates:

Headline / Copy Tests
Hypothesis: Changing the headline from "[Current Headline]" to "[New Headline]"
will increase CTR by [X]% because [reasoning — e.g., it uses a more specific
benefit, addresses a pain point, includes a number/statistic].

Control: "[Current headline]"
Variant: "[New headline]"
Primary KPI: CTR
Secondary KPI: CPA (ensure clicks are qualified)
Minimum duration: 7 days
Required confidence: 90%
Creative Format Tests
Hypothesis: Using [video / carousel / UGC] instead of [current format] will
increase [engagement rate / CTR / conversion rate] by [X]% because [reasoning —
e.g., video captures attention longer, UGC builds trust, carousel allows
storytelling].

Control: [Current format description]
Variant: [New format description]
Primary KPI: [Engagement rate / CTR / Conversion rate]
Secondary KPI: [CPM / CPA — watch for cost changes]
Minimum duration: 7 days
Required confidence: 90%
Audience Tests
Hypothesis: Targeting [New Audience — e.g., lookalike 1% from purchasers] instead
of [Current Audience — e.g., interest-based targeting] will decrease CPA by [X]%
because [reasoning — e.g., lookalikes are pre-qualified, interest targeting is
too broad].

Control: [Current audience definition]
Variant: [New audience definition]
Primary KPI: CPA
Secondary KPI: Conversion rate, ROAS
Minimum duration: 14 days
Required confidence: 90%
Landing Page Tests
Hypothesis: Changing [specific element — e.g., the hero headline, CTA button
color, social proof section placement] will increase landing page conversion rate
by [X]% because [reasoning — e.g., the new headline matches the ad copy better,
the CTA is more visible, social proof above the fold builds trust faster].

Control: [Current page description]
Variant: [Change description]
Primary KPI: Landing page conversion rate
Secondary KPI: Bounce rate, time on page
Minimum duration: 14 days
Required confidence: 95%
Offer / CTA Tests
Hypothesis: Changing the offer from "[Current offer — e.g., 10% off]" to
"[New offer — e.g., free shipping]" will increase conversion rate by [X]%
because [reasoning — e.g., free shipping removes a purchase barrier,
percentage discounts are less tangible].

Control: "[Current offer]"
Variant: "[New offer]"
Primary KPI: Conversion rate
Secondary KPI: AOV (ensure offer doesn't erode margins)
Minimum duration: 7 days
Required confidence: 90%

Platform-Specific Testing Features

Meta (Facebook/Instagram)

Built-in A/B Testing Tool:

  • Access: Ads Manager → Experiments → A/B Test
  • Can test: Creative, Audience, Placement, Delivery optimization
  • Meta automatically splits traffic evenly and reports winner
  • Minimum budget: $30/day per variant
  • Recommended duration: 7-14 days

Advantage+ Shopping Campaigns (ASC):

  • Cannot A/B test within ASC — test ASC vs manual campaigns as a whole
  • ASC handles creative testing internally (feed it 10+ creatives)
  • Compare ASC ROAS vs manual campaign ROAS after 14 days

Dynamic Creative Testing:

  • Upload multiple headlines (up to 5), images (up to 10), descriptions (up to 5)
  • Meta automatically tests combinations and optimizes
  • Good for TOFU — lets the algorithm find winning combos fast
  • Not suitable for rigorous A/B tests — you cannot control which combos are shown

Creative Testing Best Practices (Meta):

  • Use Campaign Budget Optimization (CBO) for tests — equal distribution
  • Keep ad sets identical except for the ONE variable you are testing
  • Turn off Advantage+ audience expansion during audience tests
  • Test minimum 3 creatives per ad set for the algorithm to optimize
Google Ads

Built-in Experiments:

  • Access: Campaigns → Experiments → Create Experiment
  • Can test: Bidding strategies, keywords, ad copy, landing pages
  • Set traffic split: 50/50 recommended, minimum 30/70
  • Minimum duration: 14 days (Google recommends 4-8 weeks)
  • Reports confidence level and projected impact

Responsive Search Ads (RSA) Testing:

  • Upload 15 headlines and 4 descriptions
  • Pin headlines to specific positions to test (Pin Headline 1 vs Pin Headline 2)
  • Review "Asset Details" report to see individual headline/description performance
  • Replace underperformers every 2-4 weeks

Ad Variations (Google):

  • Access: Campaigns → Experiments → Ad Variations
  • Test find-and-replace changes across all ads in a campaign
  • Great for testing: headline patterns, CTA text, description approaches
  • Set end date and significance threshold in advance

Landing Page Testing (Google):

  • Use Google Optimize (or replacement) for on-page A/B tests
  • Track in Google Ads by creating separate conversion actions per variant
  • Alternatively: create two ad groups pointing to different URLs, compare CVR
Show full SKILL.md (787 more words)Show less
LinkedIn Ads

A/B Testing (Manual):

  • LinkedIn does not have a built-in A/B test tool — you must set up tests manually
  • Create 2 campaigns with identical settings except the variable being tested
  • Set equal daily budgets on both campaigns
  • Use LinkedIn's demographic reporting to compare audience quality

Creative Testing on LinkedIn:

  • Create 2-4 ad variations per campaign
  • LinkedIn rotates ads and shows performance by creative
  • Sort by CTR and conversion rate after 1,000+ impressions per ad
  • Pause underperformers, keep winners

Audience Testing on LinkedIn:

  • Test: Job title vs job function targeting
  • Test: Company size segments (1-50 vs 51-200 vs 201-500 vs 500+)
  • Test: Industry targeting vs company list (ABM) targeting
  • Test: LinkedIn Audience Network ON vs OFF

Lead Gen Form Testing:

  • Test number of form fields (3 vs 5 vs 7)
  • Test custom questions vs standard LinkedIn pre-fill fields
  • Test offer in the form header ("Get the whitepaper" vs "Book a demo")
  • Fewer fields = higher completion rate but lower lead quality

90-Day Testing Calendar

Phase 1: Foundation Tests (Weeks 1-4)

Goal: Find the best-performing copy, creative format, and primary audience.

WeekTestVariableVariantsDurationKPI
Week 1-2Test 1Headlines3 headline variations7-10 daysCTR
Week 2-3Test 2Creative FormatStatic image vs Video vs Carousel7-10 daysEngagement + CTR
Week 3-4Test 3Primary Text (body copy)2 copy angles (benefit vs pain point)7 daysCTR + CPA

End of Phase 1 Checkpoint:

  • Winning headline identified
  • Best creative format identified
  • Copy angle (benefit vs pain) decided
  • Document all results in testing tracker
Phase 2: Audience & Offer Tests (Weeks 5-8)

Goal: Optimize targeting and offers to reduce CPA and increase ROAS.

WeekTestVariableVariantsDurationKPI
Week 5-6Test 4Audience SegmentsInterest vs Lookalike vs Broad14 daysCPA + ROAS
Week 6-7Test 5Offer / CTADiscount vs Free trial vs Bonus vs Consultation7-10 daysCVR
Week 7-8Test 6Hook (video first 3s)3 different opening hooks7-10 daysView rate + CTR

End of Phase 2 Checkpoint:

  • Best audience segment identified
  • Winning offer confirmed
  • Best video hook found
  • CPA should be 20-40% lower than Week 1
Phase 3: Landing Page & Placement Tests (Weeks 9-12)

Goal: Optimize post-click experience and placement efficiency.

WeekTestVariableVariantsDurationKPI
Week 9-10Test 7Landing Page HeadlineAd-matched headline vs benefit headline14 daysLP CVR
Week 10-11Test 8Landing Page CTAButton text, color, placement14 daysLP CVR
Week 11-12Test 9PlacementsFeed-only vs All Placements vs Reels-only7-10 daysCPM + CPA

End of Phase 3 Checkpoint:

  • Landing page optimized (should see 20%+ CVR improvement from baseline)
  • Best placements identified
  • Full funnel performance documented
Ongoing (Month 4+)

After the 90-day foundation, run continuous tests:

FrequencyWhat to TestWhy
Every 2 weeksNew creative variationsCombat ad fatigue, find new angles
MonthlyNew audience segmentsExpand reach while maintaining CPA
MonthlyBidding strategy adjustmentsOptimize cost efficiency as data grows
QuarterlyNew platformsTest emerging channels (TikTok, Pinterest, Snapchat)
QuarterlyFull funnel restructureRe-evaluate funnel stage allocation

Winner Criteria & Decision Framework

How to Declare a Winner
Step 1: Has the test reached minimum sample size? (Check calculator above)
  → No: Keep running. Do not peek or make decisions.
  → Yes: Proceed to Step 2.

Step 2: Is the result statistically significant at your threshold?
  → No: The test is inconclusive. Options:
        a) Run longer to accumulate more data
        b) Call it a draw and test something bigger
  → Yes: Proceed to Step 3.

Step 3: Is the lift practically significant?
  → Does the winning variant improve your primary KPI by >10%?
  → Would the improvement meaningfully impact revenue at your spend level?
  → No: The difference exists but may not be worth implementing. Move on.
  → Yes: Declare a winner.

Step 4: Check secondary KPIs
  → Did the winner improve CTR but worsen CPA? (Watch for unqualified clicks)
  → Did the winner improve CVR but worsen AOV? (Watch for margin erosion)
  → If secondary KPIs are neutral or positive: Implement the winner.
  → If secondary KPIs are negative: Weigh trade-offs before deciding.
After Declaring a Winner
ActionTimelineDetails
Implement the winnerImmediatelyReplace control with winner in all active campaigns
Document the resultSame dayLog hypothesis, variants, results, confidence level, and learnings
Plan the next testWithin 3 daysUse the testing hierarchy to identify the next highest-impact test
Scale the winnerWithin 1 weekIncrease budget by 20-30% on campaigns using the winning variant
Build on the insightOngoingUse the learning to inform future creative, copy, and targeting decisions
Iteration Plan Template
Test #[X] Results:
- Hypothesis: [What you expected]
- Outcome: [What actually happened]
- Winner: [Variant A / Variant B / Inconclusive]
- Confidence: [X]%
- Lift: [X]% improvement in [KPI]
- Key insight: [What you learned about the audience/creative/offer]

Next test based on this result:
- What to test: [Next variable]
- Why: [How this test's insight informs the next test]
- Hypothesis: [New hypothesis]
- Expected start date: [Date]

Testing Tracker Template

Include this tracker in every output for ongoing documentation:

| Test # | Date | Variable | Control | Variant | Primary KPI | Result | Confidence | Winner | Key Insight |
|---|---|---|---|---|---|---|---|---|---|
| 1 | [Date] | Headline | "[Control]" | "[Variant]" | CTR | [X]% vs [X]% | [X]% | [A/B] | [Insight] |
| 2 | [Date] | Format | Static image | Video | Engagement | [X]% vs [X]% | [X]% | [A/B] | [Insight] |
| 3 | [Date] | Audience | Interest | Lookalike 1% | CPA | $[X] vs $[X] | [X]% | [A/B] | [Insight] |

Output Template

Generate the output as ADS-TESTING-PLAN.md using this structure:

markdown
# A/B Testing Plan: [Business/Campaign Name]

**Generated:** [Date]
**Platform(s):** [Platform list]
**Current Monthly Budget:** $[Amount]
**Current Daily Traffic (clicks):** [Estimated]
**Testing Capacity:** [X tests per month based on traffic]

---

## Testing Priority Stack

| Priority | Test | Expected Impact | Duration | Status |
|---|---|---|---|---|
| 1 | [Test name] | [Expected lift] | [Days] | Pending |
| 2 | [Test name] | [Expected lift] | [Days] | Pending |
| ... | ... | ... | ... | ... |

---

## Test Details

### Test 1: [Test Name]
**Hypothesis:** [Full hypothesis]
**Control:** [Description]
**Variant(s):** [Description]
**Primary KPI:** [Metric]
**Secondary KPI:** [Metric]
**Required sample size:** [Clicks per variant]
**Estimated duration:** [Days]
**Confidence threshold:** [X]%
**Winner criteria:** [Specific criteria]

### Test 2: [Test Name]
[Same structure]

---

## 90-Day Testing Calendar

### Phase 1: Weeks 1-4 — [Phase Name]
[Weekly breakdown with specific tests]

### Phase 2: Weeks 5-8 — [Phase Name]
[Weekly breakdown]

### Phase 3: Weeks 9-12 — [Phase Name]
[Weekly breakdown]

---

## Platform-Specific Setup Instructions

### [Platform 1]
[Step-by-step instructions for setting up tests on this platform]

### [Platform 2]
[Step-by-step instructions]

---

## Testing Tracker

[Empty tracker template for ongoing documentation]

---

## Statistical Reference

[Quick reference table for sample sizes based on their traffic volume]

Rules

  1. ALWAYS start with the testing hierarchy — never let a user test low-impact variables before high-impact ones
  2. ALWAYS calculate test duration based on actual traffic volume — never recommend a test that cannot reach significance
  3. ALWAYS include hypothesis templates — untested hypotheses lead to unactionable results
  4. ALWAYS include minimum sample size requirements — premature winner calls waste budget
  5. ALWAYS include the 90-day calendar — users need a structured timeline, not just a list
  6. ALWAYS include platform-specific setup instructions — tell them exactly how to set up the test
  7. NEVER recommend testing more than 2 variables simultaneously — isolation is essential
  8. NEVER recommend a test duration under 7 days — day-of-week effects distort results
  9. NEVER let budget constraints go unmentioned — if daily traffic is too low, say so and suggest alternatives
  10. ALWAYS include the iteration plan — every test should inform the next test
  11. ALWAYS include the testing tracker template — documentation prevents repeated tests
  12. Output the complete plan to ADS-TESTING-PLAN.md in the current working directory

© zubair-trabzada, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/ads-testing of zubair-trabzada/ai-ads-claude.

Open the folder on GitHubat commit d1df3f5

Compare with similar skills

Ads Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ads Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ads Testing this skillzubair-trabzada/ai-ads-claude268—~5.4kAutomated safety check: PassMIT
Ad Test Designeraaron-he-zhu/aaron-marketing-skills2.9k2 repos~2.8kAutomated safety check: PassApache-2.0
Ab Test Analyzeririnabuht12-oss/marketing-skills4.1k—~1.4kAutomated safety check: PassNone
Define Hypothesisproduct-on-purpose/pm-skills716—~966Automated safety check: PassApache-2.0
A B Test DesignOwl-Listener/designer-skills2.9k1 repos~472Automated safety check: PassMIT
Ab Test Planindranilbanerjee/digital-marketing-pro8621 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Ad Test Designer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"…

    2.9k GitHub starsUsed in 2 repos~2.8k tokens
    Marketing & SEOAuto-check passed
  • Ab Test Analyzer

    irinabuht12-oss/marketing-skills

    Statistical significance calculator for A/B test results with sample size requirements, segment breakdowns, and hypothesis generation.

    4.1k GitHub stars~1.4k tokensUpdated 16 days ago
    Marketing & SEOAuto-check passed
  • Define Hypothesis

    product-on-purpose/pm-skills

    Defines a testable hypothesis with clear success metrics and a validation approach.

    716 GitHub stars~966 tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed
  • A B Test Design

    Owl-Listener/designer-skills

    Design an A/B experiment — hypothesis, variants, primary metric, and sample size.

    2.9k GitHub starsUsed in 1 repo~472 tokens
    Marketing & SEOAuto-check passed
  • Ab Test Plan

    indranilbanerjee/digital-marketing-pro

    Plan an A/B test by script: sample size per variant, days to run, stopping rules.

    862 GitHub starsUsed in 1 repo~1.9k tokens
    Marketing & SEOAuto-check passed
  • Ab Testing

    ericrisco/rsc-harness

    A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…

    180 GitHub stars~2.4k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

More from zubair-trabzada/ai-ads-claude

All 9 skills in this repo
  • Ads Audit

    zubair-trabzada/ai-ads-claude

    Ad Performance Auditor — analyze existing ad campaigns and identify optimization opportunities

    268 GitHub stars~3.5k tokensUpdated 6 mo ago
    Auto-check passed
  • Ads Budget

    zubair-trabzada/ai-ads-claude

    Budget Allocation & ROI Projector. An agent skill from zubair-trabzada/ai-ads-claude.

    268 GitHub stars~4.6k tokensUpdated 6 mo ago
    Auto-check passed
  • Ads Competitors

    zubair-trabzada/ai-ads-claude

    Competitive Ad Intelligence. An agent skill from zubair-trabzada/ai-ads-claude.

    268 GitHub stars~4.9k tokensUpdated 6 mo ago
    Auto-check passed
  • Ads Creative

    zubair-trabzada/ai-ads-claude

    Creative Brief Generator for designers, video editors, and content teams

    268 GitHub stars~4.3k tokensUpdated 6 mo ago
    Auto-check passed
  • Ads Landing

    zubair-trabzada/ai-ads-claude

    Landing Page Audit & Optimizer. An agent skill from zubair-trabzada/ai-ads-claude.

    268 GitHub stars~4.9k tokensUpdated 6 mo ago
    Auto-check passed
  • Ads Quick

    zubair-trabzada/ai-ads-claude

    60-Second Ad Readiness Snapshot — quick assessment without subagents

    268 GitHub stars~2.4k tokensUpdated 6 mo ago
    Auto-check passed

Works with

Categories

Questions about Ads Testing

What does Ads Testing do?

A/B Testing Plan Generator. An agent skill from zubair-trabzada/ai-ads-claude. Ads Testing is an agent skill from zubair-trabzada/ai-ads-claude. A/B Testing Plan Generator.

When should I use Ads Testing?

Ads Testing fits situations like: tasks that involve A/B testing; tasks that involve Experimental design.

How do I install Ads Testing in Claude Code?

Run `npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a claude-code`. Or copy the skill folder (skills/ads-testing in zubair-trabzada/ai-ads-claude) into .claude/skills/ads-testing in your project. Claude Code loads it when a task matches its description.

How do I install Ads Testing in Codex?

Run `npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a codex`. Or copy the skill folder (skills/ads-testing in zubair-trabzada/ai-ads-claude) into .agents/skills/ads-testing in your project. Codex loads it when a task matches its description.

Can I use Ads Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ads-testing, .gemini/skills/ads-testing, .github/skills/ads-testing and .opencode/skills/ads-testing in your project.

What does Ads Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Ads Testing is instructions for the agent only.

Does Ads Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ads Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ads Testing use?

Ads Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ads Testing use?

About 5.4k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ads Testing?

Skills that share tags, products or a category with Ads Testing: Ad Test Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Ab Test Analyzer (irinabuht12-oss/marketing-skills, 4.1k stars), Define Hypothesis (product-on-purpose/pm-skills, 716 stars) and A B Test Design (Owl-Listener/designer-skills, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ads Testing?

zubair-trabzada (a GitHub user) maintains it in zubair-trabzada/ai-ads-claude, which has 268 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on April 8, 2026.

Source: zubair-trabzada/ai-ads-claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.