Install
$ agentstack add skill-felixgraeber-claude-aso-audit-skill-aso-ab-testing ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
ASO A/B Testing — Experimentation
Capabilities
- Test hypothesis generation from audit findings
- Platform-specific experiment design
- Variant recommendations (control vs treatment)
- Statistical significance and duration guidance
- Results interpretation framework
- Sequential test roadmap planning
Platform Capabilities
iOS: Product Page Optimization (PPO)
| Aspect | Specification | |--------|--------------| | Testable elements | App icon, screenshots, app preview video | | NOT testable | Title, subtitle, keywords, description | | Max treatments | 3 (plus original) | | Traffic split | Apple-controlled | | Min duration | 7 days recommended | | Max duration | 90 days | | Audience | All users or specific locales | | Active tests | 1 at a time (on default product page) |
Android: Store Listing Experiments
| Aspect | Specification | |--------|--------------| | Testable elements | Icon, feature graphic, screenshots, short description, full description, promo video | | Max experiments | 5 localized + 1 main simultaneously | | Traffic split | Configurable | | Min duration | 7 days recommended | | Audience | Default or country-specific listings |
Test Design Framework
1. Hypothesis
State: "Changing [element] from [current] to [proposed] will [increase/decrease] [metric] because [reason]."
2. Element Selection (priority order)
- Screenshots (highest conversion impact, testable on both platforms)
- App icon (affects browse + search impressions)
- Short description / feature graphic (Android only for text)
- Preview video (presence vs absence)
3. Variant Design
- Change ONE element per test (isolate variable)
- Make the change meaningful (not subtle)
- Have clear visual/copy difference between control and treatment
4. Duration & Sample Size
- Minimum 7 days (capture weekday + weekend patterns)
- Need 90%+ confidence level
- Rule of thumb: ~1000 page views per variant for meaningful results
- Account for seasonal effects
5. Success Metrics
- Primary: Install conversion rate (page view → install)
- Secondary: First-time installers, 1-day retention (Android)
Output Format
# A/B Test Plan: [App Name]
## Test 1: [Element Being Tested]
- Hypothesis: [statement]
- Platform: iOS PPO / Android Experiment
- Control: [current element description]
- Treatment: [proposed change]
- Expected impact: [conversion increase estimate]
- Duration: [recommended days]
- Success criteria: [metric + threshold]
## Test Roadmap (Sequential)
1. [highest impact test first]
2. [second test]
3. [third test]
Available Tools
Read, Bash, Write, Glob, Grep
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: FelixGraeber
- Source: FelixGraeber/claude-aso-audit-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.