aso-researchlisted
Install: claude install-skill zohaibmushwani/agent-skills
# aso-research
Do the ASO job with open data and be explicit about its limits. Paid tools sell *estimates* built from private panels; an agent can still do the useful 80%: find the words people type, see what competitors rank for, and write a listing that fits the store rules.
## What is measurable for free, and what is not
| Question | Free answer | Not available free |
|---|---|---|
| What do people type? | Store autocomplete suggestions (`scripts/gplay_probe.mjs suggest`) | real search volume / popularity (Play) |
| Who ranks for a keyword? | position in search results, first page only (`search`) | deep ranks, historical rank |
| What do competitors say? | title, short + long description, ratings, install bucket, updated date, reviews (`app`, `reviews`) | downloads and revenue (only buckets such as "1M+") |
| Is my listing valid? | `scripts/metadata_check.py` against store limits | store-side policy review |
| Which words recur? | `scripts/keyword_freq.py` over competitor text | keyword difficulty scores (a vendor's estimate) |
| Your own app's numbers | Play Console / App Store Connect reports (needs your account) | - |
iOS keyword popularity exists only through Apple Search Ads (a free account is enough); the open-source `semihcihan/App-Store-Optimization-CLI` and `KenanAtmaca/aso-mcp` use it or their own scoring. Treat any score as an estimate and label it so.
## Workflow
1. **Frame.** Platform(s), countries and languages, app category, 3-6 seed phrases (what the use