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?"…
A/B Testing Plan Generator. An agent skill from zubair-trabzada/ai-ads-claude.
$ npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zubair-trabzada/ai-ads-claude ads-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "ads-testing" agent skill from https://github.com/zubair-trabzada/ai-ads-claude/tree/main/skills/ads-testing into .claude/skills/ads-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ads-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zubair-trabzada/ai-ads-claude/tree/main/skills/ads-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zubair-trabzada/ai-ads-claude ads-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zubair-trabzada/ai-ads-claude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ads-testing .agents/skills/ads-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ads-testing" agent skill from https://github.com/zubair-trabzada/ai-ads-claude/tree/main/skills/ads-testing into .agents/skills/ads-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ads-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zubair-trabzada/ai-ads-claude ads-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zubair-trabzada/ai-ads-claude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ads-testing .cursor/skills/ads-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ads-testing" agent skill from https://github.com/zubair-trabzada/ai-ads-claude/tree/main/skills/ads-testing into .cursor/skills/ads-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ads-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zubair-trabzada/ai-ads-claude.git --path skills/ads-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zubair-trabzada/ai-ads-claude ads-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zubair-trabzada/ai-ads-claude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ads-testing .gemini/skills/ads-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ads-testing" agent skill from https://github.com/zubair-trabzada/ai-ads-claude/tree/main/skills/ads-testing into .gemini/skills/ads-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ads-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zubair-trabzada/ai-ads-claude ads-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zubair-trabzada/ai-ads-claude.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ads-testing .github/skills/ads-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ads-testing" agent skill from https://github.com/zubair-trabzada/ai-ads-claude/tree/main/skills/ads-testing into .github/skills/ads-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ads-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zubair-trabzada/ai-ads-claude --skill ads-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zubair-trabzada/ai-ads-claude ads-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zubair-trabzada/ai-ads-claude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ads-testing .opencode/skills/ads-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ads-testing" agent skill from https://github.com/zubair-trabzada/ai-ads-claude/tree/main/skills/ads-testing into .opencode/skills/ads-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ads-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ads-testingA/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. 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.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d1df3f5. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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.
.claude/skills/ads-testing/SKILL.md (or your agent's skills folder).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.
ADS-TESTING-PLAN.mdTesting in the wrong order wastes budget. Always follow this hierarchy — each level has the highest impact-to-effort ratio for its position:
| Priority | What to Test | Why This Order | Expected Impact |
|---|---|---|---|
| 1 | Headlines / Primary Text | Copy is the #1 driver of CTR. Fastest to test, biggest swing in results. | 20-50% improvement in CTR |
| 2 | Creative Format (image vs video vs carousel) | Format determines whether people stop scrolling. Second-biggest impact. | 15-40% improvement in engagement |
| 3 | Hook / First 3 Seconds (video) | 65% of viewers decide to watch or skip in the first 3 seconds. | 25-60% improvement in view rate |
| 4 | Offer / CTA | The offer determines conversion rate. Test after you have attention. | 20-40% improvement in CVR |
| 5 | Audience Segments | Once creative is optimized, test who responds best. | 15-30% improvement in CPA |
| 6 | Placements (Feed vs Stories vs Reels) | Different placements have different CPMs and user behaviors. | 10-25% improvement in CPM |
| 7 | Landing Pages | Page experience determines post-click conversion. | 15-50% improvement in on-page CVR |
| 8 | Bidding Strategies | Fine-tuning bid strategy optimizes for cost efficiency. | 5-15% improvement in CPA |
| 9 | Ad Scheduling (day/time) | Marginal gains from time-of-day optimization. | 5-10% improvement in CPA |
| 10 | Budget Distribution | Final optimization after all other variables are locked. | 5-10% improvement in ROAS |
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)| Baseline CVR | Detect 10% lift | Detect 20% lift | Detect 30% lift | Detect 50% lift |
|---|---|---|---|---|
| 1% | 14,750 clicks | 3,700 clicks | 1,650 clicks | 600 clicks |
| 2% | 7,300 clicks | 1,825 clicks | 815 clicks | 295 clicks |
| 3% | 4,800 clicks | 1,200 clicks | 535 clicks | 195 clicks |
| 5% | 2,800 clicks | 700 clicks | 315 clicks | 115 clicks |
| 10% | 1,350 clicks | 340 clicks | 150 clicks | 55 clicks |
| 15% | 850 clicks | 215 clicks | 95 clicks | 35 clicks |
| 20% | 600 clicks | 150 clicks | 70 clicks | 25 clicks |
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 daysRegardless of sample size calculations, never run a test for less than:
| Test Type | Minimum Duration | Why |
|---|---|---|
| Ad copy / creative | 7 days | Need to capture weekday + weekend behavior |
| Audience targeting | 14 days | Algorithms need time to optimize delivery |
| Landing page | 14 days | Need full weekly cycles for behavior patterns |
| Bidding strategy | 14 days | Bid algorithms take 3-7 days to stabilize |
| Budget / scheduling | 21 days | Need 3 full weekly cycles for reliability |
Never run a test longer than 30 days unless absolutely necessary. After 30 days:
| Scenario | Required Confidence | When 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 |
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| Mistake | Why It Is Wrong | What to Do Instead |
|---|---|---|
| Calling a winner in 24-48 hours | Sample size too small, results unstable | Wait for minimum sample size per variant |
| Testing too many variables at once | Cannot attribute results to any one change | Test ONE variable at a time |
| Stopping test when one variant is "ahead" | Early leads often reverse with more data | Pre-commit to test duration, do not peek |
| Not accounting for day-of-week effects | Behavior varies by day | Always run tests for full 7-day cycles |
| Ignoring statistical significance | Random variation can look like a real difference | Use 90%+ confidence before declaring a winner |
| Testing on low-traffic campaigns | Will never reach significance | Consolidate traffic or test at higher level |
| Not documenting results | Lose institutional knowledge, repeat tests | Log every test in a testing tracker |
Every test must start with a clear hypothesis. Use these templates:
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%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%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%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%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%Built-in A/B Testing Tool:
Advantage+ Shopping Campaigns (ASC):
Dynamic Creative Testing:
Creative Testing Best Practices (Meta):
Built-in Experiments:
Responsive Search Ads (RSA) Testing:
Ad Variations (Google):
Landing Page Testing (Google):
A/B Testing (Manual):
Creative Testing on LinkedIn:
Audience Testing on LinkedIn:
Lead Gen Form Testing:
Goal: Find the best-performing copy, creative format, and primary audience.
| Week | Test | Variable | Variants | Duration | KPI |
|---|---|---|---|---|---|
| Week 1-2 | Test 1 | Headlines | 3 headline variations | 7-10 days | CTR |
| Week 2-3 | Test 2 | Creative Format | Static image vs Video vs Carousel | 7-10 days | Engagement + CTR |
| Week 3-4 | Test 3 | Primary Text (body copy) | 2 copy angles (benefit vs pain point) | 7 days | CTR + CPA |
End of Phase 1 Checkpoint:
Goal: Optimize targeting and offers to reduce CPA and increase ROAS.
| Week | Test | Variable | Variants | Duration | KPI |
|---|---|---|---|---|---|
| Week 5-6 | Test 4 | Audience Segments | Interest vs Lookalike vs Broad | 14 days | CPA + ROAS |
| Week 6-7 | Test 5 | Offer / CTA | Discount vs Free trial vs Bonus vs Consultation | 7-10 days | CVR |
| Week 7-8 | Test 6 | Hook (video first 3s) | 3 different opening hooks | 7-10 days | View rate + CTR |
End of Phase 2 Checkpoint:
Goal: Optimize post-click experience and placement efficiency.
| Week | Test | Variable | Variants | Duration | KPI |
|---|---|---|---|---|---|
| Week 9-10 | Test 7 | Landing Page Headline | Ad-matched headline vs benefit headline | 14 days | LP CVR |
| Week 10-11 | Test 8 | Landing Page CTA | Button text, color, placement | 14 days | LP CVR |
| Week 11-12 | Test 9 | Placements | Feed-only vs All Placements vs Reels-only | 7-10 days | CPM + CPA |
End of Phase 3 Checkpoint:
After the 90-day foundation, run continuous tests:
| Frequency | What to Test | Why |
|---|---|---|
| Every 2 weeks | New creative variations | Combat ad fatigue, find new angles |
| Monthly | New audience segments | Expand reach while maintaining CPA |
| Monthly | Bidding strategy adjustments | Optimize cost efficiency as data grows |
| Quarterly | New platforms | Test emerging channels (TikTok, Pinterest, Snapchat) |
| Quarterly | Full funnel restructure | Re-evaluate funnel stage allocation |
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.| Action | Timeline | Details |
|---|---|---|
| Implement the winner | Immediately | Replace control with winner in all active campaigns |
| Document the result | Same day | Log hypothesis, variants, results, confidence level, and learnings |
| Plan the next test | Within 3 days | Use the testing hierarchy to identify the next highest-impact test |
| Scale the winner | Within 1 week | Increase budget by 20-30% on campaigns using the winning variant |
| Build on the insight | Ongoing | Use the learning to inform future creative, copy, and targeting decisions |
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]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] |Generate the output as ADS-TESTING-PLAN.md using this structure:
# 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]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
Just SKILL.md in skills/ads-testing of zubair-trabzada/ai-ads-claude.
Open the folder on GitHubat commit d1df3f5
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ads Testing this skillzubair-trabzada/ai-ads-claude | 268 | — | ~5.4k | Automated safety check: Pass | MIT | |
| Ad Test Designeraaron-he-zhu/aaron-marketing-skills | 2.9k | 2 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Ab Test Analyzeririnabuht12-oss/marketing-skills | 4.1k | — | ~1.4k | Automated safety check: Pass | None | |
| Define Hypothesisproduct-on-purpose/pm-skills | 716 | — | ~966 | Automated safety check: Pass | Apache-2.0 | |
| A B Test DesignOwl-Listener/designer-skills | 2.9k | 1 repos | ~472 | Automated safety check: Pass | MIT | |
| Ab Test Planindranilbanerjee/digital-marketing-pro | 862 | 1 repos | ~1.9k | Automated safety check: Pass | MIT |
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?"…
irinabuht12-oss/marketing-skills
Statistical significance calculator for A/B test results with sample size requirements, segment breakdowns, and hypothesis generation.
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
indranilbanerjee/digital-marketing-pro
Plan an A/B test by script: sample size per variant, days to run, stopping rules.
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…
zubair-trabzada/ai-ads-claude
Ad Performance Auditor — analyze existing ad campaigns and identify optimization opportunities
zubair-trabzada/ai-ads-claude
Budget Allocation & ROI Projector. An agent skill from zubair-trabzada/ai-ads-claude.
zubair-trabzada/ai-ads-claude
Competitive Ad Intelligence. An agent skill from zubair-trabzada/ai-ads-claude.
zubair-trabzada/ai-ads-claude
Creative Brief Generator for designers, video editors, and content teams
zubair-trabzada/ai-ads-claude
Landing Page Audit & Optimizer. An agent skill from zubair-trabzada/ai-ads-claude.
zubair-trabzada/ai-ads-claude
60-Second Ad Readiness Snapshot — quick assessment without subagents
Works with
Categories
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.
Ads Testing fits situations like: tasks that involve A/B testing; tasks that involve Experimental design.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Ads Testing is instructions for the agent only.
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.
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.
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.
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.
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.
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.