aso works through a listing audit in phases. It detects the store from the URL, fetches the listing, assesses brand maturity, scores each dimension, optionally compares competitors and generates a report.
It knows the field limits and rules of Apple and Google Play, including title, subtitle, short description, promotional text and screenshots, and ends with a checklist of common issues.
What You Get
- A fetched summary of listing fields such as title, subtitle, screenshots, ratings and recent reviews
- A score for each dimension against written scoring criteria
- An optional side-by-side comparison with competitor listings
- A report built from a report template
- A common issues checklist and store-specific rules
Common Use Cases
- Auditing a new app’s listing before launch
- Choosing between title and keyword options
- Finding why downloads are low despite traffic
- Comparing a listing with two competitors
What Makes It Unique
It adjusts scoring to brand maturity, so an established brand and a new app are judged differently. References hold the character limits and specs for Apple and Google Play, scoring criteria and benchmarks.
Under The Hood
The SKILL.md and five references (Apple specs, Google Play specs, benchmarks, scoring criteria and a report template) are loaded as context. The skill ships no scripts. It tells the agent to use WebFetch to read the public store listing page and to search the web for the listing when only a name is given.