aso-audit
Skill1 starsChanged 46 days agoMITView on GitHub
Audit an App Store or Google Play listing — title, subtitle or short description, description, keyword coverage, category, ratings, reviews and chart ranks — and return a checklist with prioritised fixes. Use when the user asks for an ASO audit, a listing review or how to rank better. Needs the ASOSpy MCP server.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- mia-ppp/PMM-Skillstheir own version, first seen Oct 25, 2026
- carbonit2023/claude-skillstheir own version, first seen Oct 20, 2026
- ai-vita/skillstheir own version, first seen Oct 20, 2026
- timruebenach/claude-skillstheir own version, first seen Oct 13, 2026
- trysonar/skillstheir own version, first seen Oct 1, 2026
- hristo2612/aso-clitheir own version, first seen Sep 23, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- hristo2612/aso-cli★ 13same name
- Kungfookenny123/aso-skills★ 2same name
- mia-ppp/PMM-Skills★ 2same name
- Shri-Phnx/claude-skills★ 2same name
- ai-vita/skills★ 1same name
- blueskynnn-cloud/claude-skills★ 0same name
- carbonit2023/claude-skills★ 0same name
- excell2024/ClaudeSkills★ 0same name
- timruebenach/claude-skills★ 0same name
- trysonar/skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- app-discoverySkill
- competitor-analysisSkill
- growth-analysisSkill
- keyword-researchSkill
- review-analysisSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Before rewriting a title, subtitle or description.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ASO audit
When to use
- "Audit my app's store listing", "how can X rank higher", "review my ASO".
- Before rewriting a title, subtitle or description.
Inputs
| Input | Default | Notes |
| App | required | Any identifier. A name that exists on both stores needs store. |
| Country | us | The storefront to audit (listing text and chart ranks). |
Tools
get_app_detail, search_keywords, live_keyword_metrics, get_store_ranking_history, get_app_reviews, search_apps, search_ads (mode: "app_keywords", iOS only).
Workflow
get_app_detailwithcountry: title, subtitle / short description, description, category,ratingScore,ratingsCount, last update, size (Google Play only), price.- Take 3–5 core terms from the title and subtitle.
search_keywordsfor each: are they terms with real demand (applePopularity,volume)? For an iOS app audited outside the US,applePopularityis the US figure, so also check these terms withlive_keyword_metrics(source: "apple",storefront: <country>). Use it the same way when a figure is missing or stale (oldupdatedAt/appleUpdatedAt). Each live lookup costs 3 quota units (1 whencached: true), and the tool allows 10 lookups per minute per workspace. search_keywordsfor the app's core use case (2–3 seeds) to find strong keywords the listing does not use.search_appsfor the top 3 apps in the same category (sort: "installs") and compare their titles and subtitles withget_app_detail.get_store_ranking_historywithcountry: where the app charts and how stable it is.get_app_reviewswithsort: "lowest_rated",limit: 50: problems that pull the rating down.- iOS:
search_adswithmode: "app_keywords": keywords the app already appears on in Apple Search Ads.
Output
A checklist. For each area give a status (good / improve / missing), the finding, and the evidence:
- Title (length, main keyword, brand)
- Subtitle (iOS) or short description (Android)
- Description (first lines, keyword use, readability)
- Keyword coverage (strong keywords used vs. missing)
- Category fit
- Ratings and reviews (score, volume, recurring complaints)
- Chart ranks (where, how stable)
- Update frequency
Then the 5 most important fixes in order, each with the expected benefit.
Limitations
- The audit cannot see screenshots, the icon, the preview video or the iOS hidden keyword field. Say so rather than guessing.
- Keyword metrics:
applePopularityfromsearch_keywordsis US App Store only;live_keyword_metricsmeasures other storefronts one keyword at a time, and those non-US values are not saved in ASOSpy. Google figures are not store search counts.measured: falsefromlive_keyword_metricsmeans unknown, not 0. - Conversion rate, impressions and page views are not in the data.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.