App Store Optimization
manojbajaj95/claude-gtm-plugin
A skill your agent uses when optimizing app store listings, researching keywords, or tracking mobile app performance on Apple App Store and Google Play Store.
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.
Install App Store Optimization
$ npx skills add cbrock84/headcount --skill app-store-optimization -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount app-store-optimization --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/demand-generation/skills/app-store-optimization .claude/skills/app-store-optimization && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "app-store-optimization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/app-store-optimization into .claude/skills/app-store-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-store-optimization", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/app-store-optimizationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill app-store-optimization -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount app-store-optimization --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/demand-generation/skills/app-store-optimization .agents/skills/app-store-optimization && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "app-store-optimization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/app-store-optimization into .agents/skills/app-store-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-store-optimization", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill app-store-optimization -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount app-store-optimization --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/demand-generation/skills/app-store-optimization .cursor/skills/app-store-optimization && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "app-store-optimization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/app-store-optimization into .cursor/skills/app-store-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-store-optimization", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/demand-generation/skills/app-store-optimization--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill app-store-optimization -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount app-store-optimization --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/demand-generation/skills/app-store-optimization .gemini/skills/app-store-optimization && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "app-store-optimization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/app-store-optimization into .gemini/skills/app-store-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-store-optimization", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount app-store-optimizationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill app-store-optimization -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/demand-generation/skills/app-store-optimization .github/skills/app-store-optimization && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "app-store-optimization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/app-store-optimization into .github/skills/app-store-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-store-optimization", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill app-store-optimization -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount app-store-optimization --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/demand-generation/skills/app-store-optimization .opencode/skills/app-store-optimization && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "app-store-optimization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/app-store-optimization into .opencode/skills/app-store-optimization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "app-store-optimization", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
app-store-optimization- GitHub stars
- 2k
- Token cost
- ~947 tokens
- SKILL.md length
- 528 words
- Files
- 2 (incl. references)
- Skills in repo
- 177
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Tasks that involve App store release
- SKILL.md covers Being found, Being installed, Reviews and Testing, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
App Store Optimization is an agent skill from cbrock84/headcount. 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.
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in Mobile, covering App store release. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
When your agent uses it
- Tasks that involve App store release
Example prompts
- “Use the app-store-optimization skill to improve visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots…”
- “/app-store-optimization”
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
App Store Optimization loads about 947 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 528 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 528 words, ~947 tokens.
Download SKILL.mdSave it as
.claude/skills/app-store-optimization/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- app-store-optimization
- description
- 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.
App store optimization
Two levers, and they are separate problems: being found, and being installed once found. Diagnose which is failing before changing anything.
Being found
The stores index different fields, so the same metadata does not work on both.
- App name / title — the single heaviest field. Brand plus the primary descriptive term. Do not spend it on brand alone.
- Subtitle and keyword field — no repetition across fields; duplicated terms are wasted characters, not reinforcement.
- Long description — indexed on one store, effectively not on the other. Write it for the store that indexes it and for humans on the store that does not.
- Category — pick where you can rank, not where you technically belong.
Target terms with real intent. Ranking first for a term nobody searches is a vanity result.
Being installed
Most visitors decide from the first screenshot and the rating, without scrolling or reading.
- Screenshots — the first two carry the decision. Lead with the outcome or the core screen, with a caption stating the benefit. Never lead with an onboarding or login screen.
- Icon — recognizable at actual size, distinct from category conventions. Test at real scale on a device.
- Rating — the strongest single conversion factor. Prompt for review after a success moment, never on launch or mid-task.
- Video — only if it demonstrates something a screenshot cannot. A weak one costs installs.
Reviews
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.
Testing
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.
Show full SKILL.md (223 more words)Show less
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Tooling
The consoles are the source of truth: App Store Connect and Google Play Console, including their own experiment features — product page optimization and store listing experiments — which test on real store traffic rather than a simulation.
Keyword and competitor research: AppTweak, Sensor Tower, data.ai, AppFollow, and similar. Treat their volume estimates as directional; the stores do not publish the underlying numbers.
Review management and reply workflows live in the consoles or in the same tools, and replying is the part most teams skip.
Never
- Chase a keyword the app does not deliver on. Installs from a mismatched query become one-star reviews and a worse ranking than you started with.
- Change metadata, screenshots, and the icon in the same release. Nothing that moves afterward can be attributed.
- Solicit ratings from a user mid-task. The prompt lands where frustration is highest and the score reflects that.
- Ignore reviews on the version you just shipped. They are the fastest signal you will get that a release broke something.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/demand-generation/skills/app-store-optimization of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
App Store Optimization next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| App Store Optimization this skillcbrock84/headcount | 2k | — | ~947 | Automated safety check: Pass | MIT | |
| App Store Optimizationmanojbajaj95/claude-gtm-plugin | 104 | — | ~4.2k | Automated safety check: Pass | MIT | |
| App Store Featuredappeeky/aso-skills | 2.1k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Aso Auditappeeky/aso-skills | 2.1k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Apple Appstore Reviewergithub/awesome-copilot | 40k | 2 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Aso Routerappeeky/aso-skills | 2.1k | — | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
App Store Featured
appeeky/aso-skills
When the user wants to get featured on the App Store or understand the editorial process.
Aso Audit
appeeky/aso-skills
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking.
- Official
Apple Appstore Reviewer
github/awesome-copilot
Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.
Aso Router
appeeky/aso-skills
Single entry point that routes any ASO, App Store, Google Play, app marketing, paid UA, monetization, retention, reviews, ratings, market-intel, or app-analytics question to the correct specialist…
Attribution Setup
appeeky/aso-skills
When the user wants to set up, debug, or interpret app install attribution — including SKAdNetwork (SKAN), Apple's AdAttributionKit, Google Play Install Referrer, MMPs (AppsFlyer, Adjust, Singular…
More from cbrock84/headcount
All 177 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
AI Search Optimization
cbrock84/headcount
Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf.
Related
Categories
Questions about App Store Optimization
What does App Store Optimization do?
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. App Store Optimization is an agent skill from cbrock84/headcount. 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.
When should I use App Store Optimization?
App Store Optimization fits situations like: tasks that involve App store release.
How do I install App Store Optimization in Claude Code?
Run `npx skills add cbrock84/headcount --skill app-store-optimization -a claude-code`. Or copy the skill folder (plugins/demand-generation/skills/app-store-optimization in cbrock84/headcount) into .claude/skills/app-store-optimization in your project. Claude Code loads it when a task matches its description.
How do I install App Store Optimization in Codex?
Run `npx skills add cbrock84/headcount --skill app-store-optimization -a codex`. Or copy the skill folder (plugins/demand-generation/skills/app-store-optimization in cbrock84/headcount) into .agents/skills/app-store-optimization in your project. Codex loads it when a task matches its description.
Can I use App Store Optimization in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill app-store-optimization -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/app-store-optimization, .gemini/skills/app-store-optimization, .github/skills/app-store-optimization and .opencode/skills/app-store-optimization in your project.
What does App Store Optimization need to run?
SKILL.md names no scripts, command-line tools or credentials: App Store Optimization is instructions for the agent only.
Does App Store Optimization access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is App Store Optimization safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does App Store Optimization use?
App Store Optimization is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does App Store Optimization use?
About 947 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 465 tokens, read only when the agent opens those files.
What are the alternatives to App Store Optimization?
Skills that share tags, products or a category with App Store Optimization: App Store Optimization (manojbajaj95/claude-gtm-plugin, 104 stars), App Store Featured (appeeky/aso-skills, 2.1k stars), Aso Audit (appeeky/aso-skills, 2.1k stars) and Apple Appstore Reviewer (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains App Store Optimization?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,001 GitHub stars. The repository holds 177 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.