When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
ASO Audit
Analyze App Store and Google Play listings against ASO best practices. Fetches
live listing data, scores metadata, visuals, and ratings, then produces a
prioritized action plan.
When to Use
User shares an App Store or Google Play URL
User asks to audit or optimize an app listing
User wants to compare their app against competitors
User asks about app store ranking, visibility, or download conversion
Before Auditing
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
If the user gives an app name instead of a URL, search the web for:
site:apps.apple.com "{app name}" or site:play.google.com "{app name}"
Fetch the listing
Use WebFetch to retrieve the listing page. Extract every available field:
Apple App Store fields:
App name (title) — 30 char limit
Subtitle — 30 char limit
Description (long) — not indexed for search, but matters for conversion
Promotional text — 170 chars, updatable without new release
Category (primary + secondary)
Screenshots (count, order, caption text)
Preview video (presence, duration)
Rating (average + count)
Recent reviews (visible ones)
Price / in-app purchases
Developer name
Last updated date
Version history notes
Age rating
Size
Languages / localizations listed
In-app events (if any visible)
Google Play fields:
App name (title) — 30 char limit
Short description — 80 char limit
Full description — 4,000 char limit, IS indexed for search
Category + tags
Feature graphic (presence)
Screenshots (count, order)
Preview video (presence)
Rating (average + count)
Recent reviews (visible ones)
Price / in-app purchases
Developer name
Last updated date
What's new text
Downloads range
Content rating
Data safety section
Languages listed
If WebFetch returns incomplete data (stores render client-side), note gaps and
work with what's available. Ask the user to paste missing fields if critical.
Visual asset assessment
WebFetch cannot extract screenshot images or caption text. Take a screenshot
of the listing page to get visual data:
Navigate to the listing URL and capture a full-page screenshot
Assess the screenshot for: icon quality, screenshot count, caption text,
messaging quality, preview video presence, feature graphic (Google Play)
If browser tools are unavailable, ask the user to share a screenshot of the
listing page
Promotional text (Apple): This 170-char field appears above the description
but is often indistinguishable from it in scraped HTML. If you cannot confirm
its presence, note this and recommend the user check App Store Connect.
Phase 1.5 — Assess Brand Maturity
Before scoring, classify the app into one of three tiers. This determines how
you interpret "textbook ASO" deviations — a deliberate brand choice by a
household name is not the same as a missed opportunity by an unknown app.
Tier definitions
Tier
Signals
Examples
Dominant
Household name, 1M+ ratings, top-10 in category, near-universal brand recognition. Users search by brand name, not generic keywords.
Instagram, Uber, Spotify, WhatsApp, Netflix
Established
Well-known in their category, 100K+ ratings, strong organic installs, recognized brand but not universally known.
Strava, Notion, Duolingo, Cash App, Calm
Challenger
Building awareness, <100K ratings, needs discovery through keywords and ASO tactics. Most apps fall here.
Your app, most indie/startup apps
How tier affects scoring
Dominant apps get adjusted scoring in these areas:
Title: Brand-only or brand-first titles are valid (score 8+ if brand is the keyword). These apps don't need generic keyword discovery.
Description: Score purely on conversion quality, not keyword presence. If the app is a household name, a well-crafted brand description beats a keyword-stuffed one.
Visual Assets: Lifestyle/brand photography instead of UI demos is a legitimate conversion strategy. No video is acceptable if the product is hard to demo in 30s or brand awareness is near-universal.
What's New: Generic release notes at weekly+ cadence are acceptable (score 8+). At scale, detailed changelogs have minimal ROI and risk backlash.
In-app events: Missing events for utility apps with massive install bases (Uber, WhatsApp) is not a penalty. These apps don't need discovery help.
Localization: Score relative to actual market, not absolute count. A US-only fintech with 2 languages (English + Spanish) is appropriately localized.
Established apps get partial adjustment:
Brand-first titles are fine but should still include 1-2 keywords
Strategic description choices get benefit of the doubt
Other dimensions scored normally
Challenger apps are scored strictly against textbook ASO best practices — every character, screenshot, and keyword matters.
Key principle: Before docking points, ask: "Is this a mistake or a deliberate
choice by a team that has data I don't?" If the app has 1M+ ratings and a
dedicated ASO team, assume their choices are data-informed unless clearly wrong.
Phase 2 — Score Each Dimension
Score each dimension 0-10 using the criteria in references/scoring-criteria.md.
Apply the brand maturity tier adjustments from Phase 1.5.
Reference files for platform specs and benchmarks:
references/apple-specs.md — Official Apple character limits, screenshot/video specs, CPP/PPO rules, rejection triggers
references/google-play-specs.md — Official Google Play limits, screenshot specs, Android Vitals thresholds, policies
Promotional Content: submit 14 days early for featuring. Apps see 2x explore acquisitions
Custom Store Listings: up to 50 (can target churned users, specific countries, ad campaigns)
Store Listing Experiments: test up to 3 variants, run 7+ days, 1 experiment at a time
See references/google-play-specs.md for full specs and policy details
What Apple Indexes vs What Google Indexes
Field
Apple Indexed?
Google Indexed?
Title
Yes
Yes (strongest signal)
Subtitle / Short desc
Yes
Yes
Keyword field
Yes (hidden)
Does not exist
Long description
No
Yes (heavily)
Screenshot captions
Yes (since 2025)
No
In-app events
Yes
N/A (LiveOps instead)
Developer name
No
Partial
IAP names
Yes
Yes
Common Issues Checklist
Flag these if found. Items marked (tier-dependent) should be evaluated against
the app's brand maturity tier — they may be deliberate choices for Dominant apps.
Always flag (all tiers):
Rating below 4.0
Last update > 3 months ago
Google Play description has no keyword strategy (under 1% density)
Google Play missing feature graphic
Apple keyword field likely has repeated words (inferred from title+subtitle)
Category mismatch — app would face less competition in a different category
Fewer than 5 screenshots
Flag for Challenger/Established only(not mistakes for Dominant apps):
Title wastes characters on brand name only (no keywords) (Dominant: brand IS the keyword)
Subtitle/short description duplicates title keywords
Description first 3 lines are generic (Dominant: may be brand-voice choice)
No preview video (Dominant: may be rational if product is hard to demo)
Screenshots are just UI dumps with no messaging/captions (Dominant: lifestyle/brand shots may convert better)
Only 1-2 localizations (score relative to actual market, not absolute count)
No in-app events or promotional content (Dominant utility apps may not need discovery help)
Flag for all tiers but note context:
No developer responses to negative reviews (note volume — responding at 10M+ reviews is a different challenge than at 1K)
Generic "What's New" text (acceptable at weekly+ release cadence for Established/Dominant)
Task-Specific Questions
What is the App Store or Google Play URL?
Is this your app or a competitor's?
What category does the app compete in?
Do you have competitor URLs to compare against?
Are you focused on search visibility, conversion rate, or both?
Do you have access to App Store Connect or Google Play Console data?
Related Skills
cro: For optimizing the conversion of web-based landing pages that drive app installs
ad-creative: For creating App Store and Google Play ad creatives
analytics: For setting up install attribution and in-app event tracking
customer-research: For understanding user needs and language to inform listing copy
Credits & Attribution
This skill is based on the excellent work by
Corey Haines.
Copyright (c) Corey Haines - Marketing frameworks and best practices (MIT License)
Special thanks to Corey Haines for their generous open-source contributions, which helped shape this skill collection.
Adapted by webconsulting.at for this skill collection
