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". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
ASO & App Marketing Skills
AI agent skills for App Store Optimization (ASO) and mobile app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent Skills-compatible AI assistant to help with keyword research, metadata optimization, competitor analysis, market intelligence, and app growth. Powered by real App Store data via the Appeeky API.
Appeeky Spec: App growth, run by your coding agent
Appeeky Spec puts your app's whole growth loop in one folder of your repo: the store listing and the searches it should win, reviews and competitors, what AI assistants say about the app, ads, experiments, and what every past change did. Your coding agent (Claude Code, Codex, Cursor, Gemini CLI and others) reads it and proposes the next change as a pull request. You merge it. The change is checked against the store rules, pushed to App Store Connect and Google Play, and measured on day 7 and day 14, and the result goes into a playbook the next change starts from.
Our other open-source skills and local app growth
For agent skills for mobile app user acquisition — TikTok ads, Meta ads, Apple Search Ads, ad creatives, and ROAS - see ua-skills.
Local App Growth
A native macOS app — a local-first for app growth. App Store Connect, Google Play, Apple Search Ads, Meta/TikTok ads, and RevenueCat sync into a cache on your Mac: full history, no CSV exports, credentials in the Keychain. Reviews, ads intelligence, and keyword data stay fast (and work offline). A built-in terminal pairs with MCP, so the same agents that use these skills can talk to your local data. Download from Appeeky.
Why This Exists
Most ASO knowledge lives in blog posts, courses, and expensive consultants. We packaged it into skills that any AI agent can use — so you get expert-level ASO guidance directly in your IDE.
Each skill contains battle-tested frameworks, scoring rubrics, and output templates. The agent reads the skill, pulls real data from the App Store (via Appeeky), and gives you actionable recommendations — not generic advice.
Quick Start
Cursor — npx skills add appeeky/aso-skills -a cursor
Claude Code — npx skills add appeeky/aso-skills
Manual — git clone https://github.com/appeeky/aso-skills.git && cp -r aso-skills/skills/* .cursor/skills/
Then ask your agent:
"Run an ASO audit for my app (id: 1617391485)"
"Find the best keywords for a meditation app"
"Optimize my App Store title and subtitle"
"How many downloads do I need to reach top 10 in Health & Fitness?"
"What apps are rising in the charts right now?"
"Give me a market briefing for the Games category"
"How are my downloads and revenue trending this month?"
"Help me plan a Christmas In-App Event"
"What seasonal keywords should I add in December?"
"Optimize my Google Play listing"
"My app rating dropped — how do I recover it?"
"Set up a weekly competitor monitoring routine for apps X, Y, Z"
"Help me pitch TechCrunch for my app launch"
"Build an Apple Search Ads campaign structure for my fitness app"
"My app has a crash affecting 2% of sessions — help me triage it"
Don't want to remember 30 skill names? Just use the router:
/aso-router → routes your request to the right specialist skill automatically
Or invoke directly: /aso-audit, /keyword-research, /metadata-optimization, /market-movers, /market-pulse, /asc-metrics, /in-app-events, /seasonal-aso, /android-aso, /apple-search-ads, /competitor-tracking
Skills
ASO Core
| Skill | What it does |
|---|---|
aso-audit | Scores your listing across 10 factors (0-100), flags problems, gives a prioritized fix list |
keyword-research | Finds keywords by volume × difficulty × relevance, groups them into primary/secondary/long-tail |
metadata-optimization | Writes title, subtitle, keyword field, description — with 3 variants and character counts |
competitor-analysis | Keyword gaps, creative teardown, positioning map, and specific opportunities to exploit |
seasonal-aso | Seasonal keyword calendar, metadata swap strategy, timing checklist, and trending-moment tactics |
android-aso | Google Play-specific ASO — indexed description strategy, short description, Play Experiments, rating recovery |
Creative & International
| Skill | What it does |
|---|---|
screenshot-optimization | 10-slot screenshot strategy with design briefs, text overlay copy, and competitor audit |
app-preview-video | Up to 3 App Preview videos per locale — script template, beat-by-beat structure, Apple/Play specs, rejection avoidance |
app-icon-optimization | Icon design principles, A/B testing via PPO/Play Experiments, category differentiation, and icon briefs |
custom-product-pages | Apple CPPs — variant strategy by audience/channel, ASA + CPP unlock, measurement floor, common mistakes |
review-management | Sentiment analysis, response templates (HEAR framework), rating improvement tactics |
localization | Market prioritization matrix, per-country keyword research, cultural adaptation checklist |
Growth
| Skill | What it does |
|---|---|
app-launch | 8-week launch timeline with daily checklists, channel strategy, and press outreach templates |
ua-campaign | Apple Search Ads, Meta, Google UAC — campaign structure, bidding, creative specs, budget allocation |
apple-search-ads | Deep-dive ASA — campaign structure, match types, CPP routing, bid strategy, weekly optimization checklist |
creator-ugc-marketing | TikTok / IG / YouTube creator program — briefs, sourcing, hook angles, Spark Ads / Partnership Ads, measurement |
referral-program | In-app referral / invite mechanics — reward sizing, K-factor math, fraud prevention, deep link flow |
web-to-app-funnel | Web → app install funnels (incl. quiz + Stripe + deferred deep link) to bypass App Store fees on subs |
app-store-featured | Featuring readiness scor |
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/ab-test-store-listing/SKILL.md7.2 KBupstream ↗
--- name: 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 1. Check for `app-marketing-context.md` — read it for context 2. Ask for the **App ID** 3. Ask for **current conversion rate** (if known from App Store Connect) 4. Ask for **daily impressions** (determines test duration) 5. 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:** 1. Go to Product Page Optimization 2. Create a new test 3. Upload variant assets 4. Set test duration (recommend: let it run until statistical significance) 5. 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: 1. Is it statistically significant? (confidence level) 2. What's the actual lift? (with confidence interval) 3. Are there segment differences? 4. What's the next test to run? 5. 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 variants - `metadata-optimization` — Optimize non-testable elements - `app-analytics` — Track conversion metrics - `aso-audit` — Identify what to test firstREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/appeeky-aso-skills-skills-ab-test-store-listing.md