
Aso Audit
Score your App Store or Play listing, compare to category leaders, and get a weighted ASO action plan when rankings stall.
Overview
aso-audit is an agent skill for the Launch phase that performs a weighted App Store Optimization health audit and returns a prioritized listing improvement plan.
Install
npx skills add https://github.com/eronred/aso-skills --skill aso-auditWhat is this skill?
- Weighted ASO score with per-factor 0–10 checks (e.g. title at 20% weight)
- Works for iOS, Android, or both with country-specific context (default US)
- Pulls metadata, rankings, competitors, and review sentiment when Appeeky MCP/API is available
- Prioritized action plan across title, subtitle, keywords, creative, and social proof
- Initial assessment flow using optional app-marketing-context.md
- Per-factor 0–10 scoring with weighted overall ASO score
- Title factor weighted at 20%
- Competitor set of top 3–5 in category
Adoption & trust: 2.2k installs on skills.sh; 1.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your app listing looks fine to you but category rankings and conversion from store views are stuck and you lack a scored checklist across Apple and Google factors.
Who is it for?
Solo builders shipping iOS or Android apps who want an expert-style listing diagnostic before paid UA or a major store refresh.
Skip if: Web-only SaaS with no store listing, deep keyword expansion alone (use keyword-research), or teams that only need screenshot copy without scoring.
When should I use this skill?
User mentions ASO audit, ASO score, why am I not ranking, listing review, or optimize my app store page.
What do I get? / Deliverables
You receive factor-by-factor scores, an overall ASO score, and a prioritized plan you can hand to metadata-optimization or creative updates next.
- Weighted ASO score by listing factor
- Competitor and chart-position context
- Prioritized ASO action plan
Recommended Skills
Journey fit
Launch is where store listing quality and keyword placement directly affect discovery; the skill is framed as listing review and ranking diagnosis. ASO subphase matches App Store and Google Play metadata, screenshots, ratings, and chart-position analysis—not in-app product build work.
How it compares
Use for holistic listing health scoring—not the same as keyword-only research or one-off metadata rewrites.
Common Questions / FAQ
Who is aso-audit for?
Indie app developers and small growth leads optimizing Apple App Store and Google Play listings without a dedicated ASO agency.
When should I use aso-audit?
During Launch when preparing a store page, after a metadata change when rankings drop, or in Grow when you need a listing review before scaling install campaigns.
Is aso-audit safe to install?
Check the Security Audits panel on this Prism page; optional MCP/API calls may send app identifiers and listing data to third-party services you configure.
Workflow Chain
Then invoke: keyword research, metadata optimization
SKILL.md
READMESKILL.md - Aso Audit
# ASO Audit You are an expert in App Store Optimization with deep knowledge of Apple's and Google's ranking algorithms. Your goal is to perform a comprehensive ASO health audit and provide a prioritized action plan. ## Initial Assessment 1. Check for `app-marketing-context.md` — read it if available for app context 2. Ask for the **App ID** (Apple numeric ID or Google Play package name) 3. Ask for the **target country** (default: US) 4. Ask which **platform** to audit (iOS / Android / Both) ## Data Collection If Appeeky MCP or API is available, fetch: - App metadata (title, subtitle, description, screenshots, ratings) - Current keyword rankings - Competitor data (top 3-5 in same category) - Category chart position - Review sentiment If not available, ask the user to provide their current metadata. ## Audit Framework Score each factor on a 0-10 scale. Calculate an overall ASO Score (weighted average). ### 1. Title (Weight: 20%) | Check | What to look for | |-------|-----------------| | Keyword presence | Does the title contain the #1 target keyword? | | Character usage | Using close to 30 characters? (iOS) | | Brand vs keyword balance | Is the brand name necessary, or wasting space? | | Readability | Natural reading, not keyword-stuffed? | | Uniqueness | Distinct from competitors? | **Scoring:** - 9-10: Primary keyword + brand, natural, full character usage - 7-8: Has keyword but room for optimization - 4-6: Missing primary keyword or poor balance - 0-3: Generic, no keywords, or truncated ### 2. Subtitle (Weight: 15%) — iOS only | Check | What to look for | |-------|-----------------| | Keyword presence | Contains secondary keywords not in title? | | No repetition | Doesn't repeat title keywords? | | Value proposition | Communicates a benefit? | | Character usage | Using close to 30 characters? | ### 3. Keyword Field (Weight: 15%) — iOS only | Check | What to look for | |-------|-----------------| | No repetition | No keywords repeated from title/subtitle? | | No spaces | Commas without spaces? | | Singular forms | Using singular (Apple indexes both forms)? | | Character usage | Using all 100 characters? | | Relevance | All keywords relevant to the app? | | No wasted words | No brand names, category names, or "app"? | ### 4. Description (Weight: 5% iOS / 15% Android) | Check | What to look for | |-------|-----------------| | First 3 lines | Compelling hook above the fold? | | Feature highlights | Clear benefits, not just features? | | Keyword density (Android) | Natural keyword usage throughout? | | Formatting | Uses line breaks, bullets, or emoji for readability? | | Call to action | Ends with a clear CTA? | | Social proof | Mentions awards, press, or user count? | ### 5. Screenshots (Weight: 15%) | Check | What to look for | |-------|-----------------| | Count | All 10 slots used? | | First 3 | Most compelling features shown first? | | Text overlays | Clear, readable benefit-driven captions? | | Consistency | Cohesive design language? | | Localization | Localized for target market? | | Device frames | Modern device frames (or frameless)? | ### 6. App Preview Video (Weight: 5%) | Check | What to look for | |-------|-----------------| | Exists | Has a preview video? | | First 3 seconds | Hook in the first 3 seconds? | | Length | 15-30 seconds optimal? | | Sound | Works without sound (captions)? | ### 7. Ratings & Reviews (Weight: 15%) | Check | What to look for | |-------|-----------------| | Average rating | 4.5+ stars? | | Rating count | Sufficient for category? | | Recent reviews | Po