Aso Audit
Run a live App Store or Google Play listing audit and get a prioritized plan to improve rankings, visibility, and install conversion.
Overview
ASO Audit is an agent skill for the Launch phase that audits App Store and Google Play listings from live data and returns scored findings with a prioritized optimization plan.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill aso-auditWhat is this skill?
- Detects Apple vs Google Play URLs and fetches live listing data for scoring
- Scores metadata, visuals, and ratings against ASO best practices
- Supports competitor comparison when you want positioning gaps surfaced
- Structured multi-phase workflow ending in a prioritized action plan
- Reads `.agents/product-marketing-context.md` first to avoid redundant questions
- Structured multi-phase ASO audit workflow (identify store, fetch live listing, score, plan)
Adoption & trust: 17.9k installs on skills.sh; 32.4k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your app is live but installs and conversion lag and you cannot tell whether metadata, creatives, ratings, or competitors are the bottleneck.
Who is it for?
Indie iOS or Android developers with a public store URL who want a structured audit before the next listing revision or competitor repositioning.
Skip if: Web-only products, pre-launch apps without a store listing, or teams that need guaranteed ranking outcomes without implementing listing changes.
When should I use this skill?
User shares an App Store or Google Play URL, asks for an ASO audit, listing optimization, ranking or conversion help, or competitor comparison for a mobile app.
What do I get? / Deliverables
You get scored listing diagnostics across metadata, visuals, and ratings plus a prioritized action plan to improve visibility and download conversion on the correct store.
- Scored audit across metadata, visuals, and ratings
- Prioritized ASO action plan for the identified store
Recommended Skills
Journey fit
App store optimization is a launch-phase discipline: you improve metadata and creatives where users discover and decide to download. ASO subphase is the exact facet for store listing audits, keyword work, and conversion fixes on Apple and Google marketplaces.
How it compares
Use for a phased, live-data ASO audit instead of ad-hoc screenshot or keyword tweaks without scoring or prioritization.
Common Questions / FAQ
Who is aso-audit for?
Solo and indie mobile builders shipping on the App Store or Google Play who want agent-guided listing analysis tied to ASO best practices and real store URLs.
When should I use aso-audit?
Use it in Launch (ASO) when you share an Apple or Play URL, ask to optimize a listing, compare against competitors, or diagnose low downloads and poor conversion on an existing app page.
Is aso-audit safe to install?
Treat it like any third-party skill: review the Security Audits panel on this Prism page and confirm what network or fetch behavior your agent allows before running audits on production listings.
SKILL.md
READMESKILL.md - Aso Audit
# 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-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. ## Phase 1 — Identify Store & Fetch ### Detect store type from URL ``` Apple: apps.apple.com/{country}/app/{name}/id{digits} Google: play.google.com/store/apps/details?id={package} ``` 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: 1. Navigate to the listing URL and capture a full-page screenshot 2. Assess the screenshot for: icon quality, screenshot count, caption text, messaging quality, preview video presence, feature graphic (Google Play) 3. 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