Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.
npx skills add https://github.com/cbrock84/headcount --skill app-store-optimization
Two levers, and they are separate problems: being found, and being installed once found.
Diagnose which is failing before changing anything.
The stores index different fields, so the same metadata does not work on both.
spend it on brand alone.
characters, not reinforcement.
that indexes it and for humans on the store that does not.
Target terms with real intent. Ranking first for a term nobody searches is a vanity result.
Most visitors decide from the first screenshot and the rating, without scrolling or reading.
a caption stating the benefit. Never lead with an onboarding or login screen.
a device.
never on launch or mid-task.
Respond to negative reviews specifically and without defensiveness, naming the fix and its version
where there is one. Prospects read the responses as much as the complaints, and a pattern of real
answers converts.
Watch review text for recurring themes — it is the cheapest continuous product research available.
Change one element at a time and let it run a full weekly cycle; app traffic is strongly
day-of-week seasonal. Attributing a lift to the wrong change is worse than not testing.
Take cbrock84/app-store-optimization from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.