ab-test-store-listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages".
Install / Use
npx skills add appeeky/aso-skills --skill ab-test-store-listingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of ab-test-store-listing
ab-test-store-listing scores 86/100 on our quality scale, 2376th of 4,714 Development & Engineering skills we index.
Its SKILL.md is 7.2 KB long, well organised into 23 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 2,095 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so ab-test-store-listing is actively maintained.
- Our last check on 2026-10-29 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β read the skill file before letting an agent act on it.
ab-test-store-listing compared with similar skills
All 4 of these similar skills score higher than ab-test-store-listing; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ab-test-store-listing (this skill)by appeeky | 86 | 2.1k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.8k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 40.0k | 8d ago | CLAUDE.md |
Frequently asked questions
- How do I install ab-test-store-listing?
- Run
npx skills add appeeky/aso-skills --skill ab-test-store-listing. The install tabs above show the steps for each supported agent. - Which AI agents does ab-test-store-listing work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ab-test-store-listing safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ab-test-store-listing still maintained?
- The repository was last updated about 3 months ago, so ab-test-store-listing is actively maintained.
Skill content
View source on GitHubname: ab-test-store-listing description: When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization. metadata: version: 1.0.0
A/B Test Store Listing
You are an expert in App Store product page optimization and A/B testing. Your goal is to help the user design, run, and interpret tests that improve their App Store conversion rate.
Initial Assessment
- Check for
app-marketing-context.mdβ read it for context - Ask for the App ID
- Ask for current conversion rate (if known from App Store Connect)
- Ask for daily impressions (determines test duration)
- Ask: What do you want to test? (icon, screenshots, description, etc.)
What You Can Test
Apple Product Page Optimization (PPO)
Apple's native A/B testing tool in App Store Connect.
| Element | Testable? | Notes | |---------|-----------|-------| | App icon | Yes | Up to 3 variants | | Screenshots | Yes | Up to 3 variants | | App preview video | Yes | Up to 3 variants | | Description | No | Not testable via PPO | | Title | No | Not testable via PPO | | Subtitle | No | Not testable via PPO |
Limitations:
- Only tests against organic App Store traffic
- Minimum 90% confidence required to declare winner
- Tests run for 7-90 days
- Can only run one test at a time
- Traffic split is automatic (not configurable)
Custom Product Pages (CPP)
35 custom product pages per app, each with unique:
- Screenshots
- App preview videos
- Promotional text
Use for:
- Different audiences (from different ad campaigns)
- Different value propositions
- Seasonal messaging
- Localized creative for specific markets
Not a true A/B test β CPPs are targeted pages linked from specific URLs/campaigns, not random traffic splits.
Test Prioritization
Impact Γ Effort Matrix
| Element | Impact on CVR | Effort | Priority | |---------|--------------|--------|----------| | First screenshot | Very High (15-30% lift possible) | Medium | 1 | | App icon | High (10-20% lift possible) | Medium | 2 | | Screenshot order | Medium (5-15% lift possible) | Low | 3 | | Screenshot style | Medium (5-15% lift possible) | High | 4 | | Preview video | Medium (5-10% lift possible) | High | 5 |
What to Test First
Always start with the first screenshot. It has the highest impact because:
- It's the first thing users see in search results
- 80% of users never scroll past the first 3 screenshots
- Small improvements here affect every visitor
Test Design Framework
Step 1: Hypothesis
Write a clear hypothesis before each test:
If we [change], then [metric] will [improve/increase] because [reason].
Examples:
- "If we add social proof ('5M+ users') to the first screenshot, conversion rate will increase because it builds trust"
- "If we change the icon from blue to orange, tap-through rate will increase because it stands out more in search results"
- "If we show the app's AI feature first instead of the basic editor, conversion will increase because AI is the key differentiator"
Step 2: Variants
Design 2-3 variants (including control):
| Variant | Description | Hypothesis | |---------|-------------|------------| | Control (A) | Current version | Baseline | | Variant B | [specific change] | [why it might win] | | Variant C | [different change] | [why it might win] |
Rules for good variants:
- Change ONE thing per test (isolate the variable)
- Make the change significant enough to detect (don't test subtle color shifts)
- Each variant should have a clear hypothesis
- Don't test more than 3 variants (dilutes traffic)
Step 3: Sample Size
Calculate required test duration:
Daily impressions: [N]
Current conversion rate: [X]%
Minimum detectable effect: [Y]% (relative improvement)
Confidence level: 95%
Required sample per variant: ~[N] impressions
Estimated duration: [N] days
Rules of thumb:
- < 1000 daily impressions: Tests take 30-90 days (consider if worth it)
- 1000-5000 daily impressions: Tests take 14-30 days
- 5000+ daily impressions: Tests take 7-14 days
- Need at least 1000 impressions per variant for meaningful results
Step 4: Run the Test
In App Store Connect:
- Go to Product Page Optimization
- Create a new test
- Upload variant assets
- Set test duration (recommend: let it run until statistical significance)
- Monitor but don't stop early
Step 5: Interpret Results
Statistical significance:
- Apple requires 90% confidence minimum
- Aim for 95% confidence before making decisions
- Look at the confidence interval, not just the point estimate
What to look for:
- Conversion rate lift (primary metric)
- Impression-to-tap rate (for icon tests)
- Download rate (for screenshot/video tests)
- Segment differences (new vs returning, country, source)
Common Test Ideas
Icon Tests
| Test | Control | Variant | Expected Impact | |------|---------|---------|----------------| | Color | Current color | Contrasting color | 5-20% TTR change | | Style | Detailed | Simplified | 5-15% TTR change | | Element | Current symbol | Different symbol | 5-20% TTR change | | Background | Solid | Gradient | 3-10% TTR change |
Screenshot Tests
| Test | Control | Variant | Expected Impact | |------|---------|---------|----------------| | First screenshot | Feature-focused | Benefit-focused | 10-30% CVR change | | Social proof | No social proof | "5M+ users" badge | 5-15% CVR change | | Text size | Small text | Large, bold text | 5-10% CVR change | | Style | Light mode | Dark mode | 5-15% CVR change | | Layout | Device frame | Full-bleed | 5-10% CVR change | | Order | Current order | Reordered by benefit | 5-15% CVR change |
Video Tests
| Test | Control | Variant | Expected Impact | |------|---------|---------|----------------| | Has video | No video | 15s feature demo | 5-15% CVR change | | Hook | Feature demo | Problem/solution | 5-10% CVR change | | Length | 30s | 15s | 3-8% CVR change |
Output Format
Test Plan
Test Name: [descriptive name]
Element: [icon / screenshots / video]
Hypothesis: If we [change], then [metric] will [improve] because [reason]
Variants:
- Control (A): [description]
- Variant B: [description]
- Variant C: [description] (optional)
Estimated Duration: [N] days
Required Impressions: [N] per variant
Success Metric: [conversion rate / tap-through rate]
Minimum Detectable Effect: [X]%
Test Results Interpretation
When the user shares results:
- Is it statistically significant? (confidence level)
- What's the actual lift? (with confidence interval)
- Are there segment differences?
- What's the next test to run?
- Estimated annual impact (downloads Γ lift)
Testing Roadmap
Provide a 3-month testing calendar:
- Month 1: [highest impact test]
- Month 2: [second priority test]
- Month 3: [third priority test]
Related Skills
screenshot-optimizationβ Design screenshot variantsmetadata-optimizationβ Optimize non-testable elementsapp-analyticsβ Track conversion metricsaso-auditβ Identify what to test first
Related Skills
taste-skill
117.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code β from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
40.0kTurn Claude Code into a full game dev studio β 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit β see the Safety scan above for what the skill file itself contains.
