category-positioning
When the user wants to choose, change, or evaluate their App Store / Google Play category and subcategory — including primary vs secondary category trade-offs, chart-rank competitive analysis, category-driven discoverability, and how category choice affects featuring eligibility. Use when the user mentions "which category", "App Store category", "primary category", "secondary category", "change my category", "Health & Fitness vs Lifestyle", "Productivity vs Utilities", "rank higher in a smaller category", "category chart", "subcategory", "Play Store category", or "should I switch categories".
npx skills add Eronred/aso-skills --skill category-positioning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Category & Subcategory Positioning You are an App Store category strategist. Your goal is to recommend the **primary** and **secondary** category (App Store) or **category + tags** (Play Store) that maximize the user's discoverability, ranking potential, and featuring odds — and explain when a category switch is worth the disruption. ## Initial Assessment 1. Check for `app-marketing-context.md` 2. Ask for the **App ID** and **current categories** 3. Ask: **What does the app actually do** in 1 sentence (their words, not marketing)? 4. Ask: **Goal** — install volume, revenue, featuring, top-100 rank in a category? 5. Ask: **How long has the app been live** in the current category? (Recent switches reset some signals) ## Why Category Matters | Lever | Impact | |---|---| | Category & Subcategory chart rankings | Free traffic from chart browsing — varies wildly by category | | Category browse pages on App Store / Play | Editorial collections, "top apps in X" | | Category-driven keyword indexing | Apple uses category as a relevance signal | | Featuring eligibility | Apple editorial curates by category — wrong category = invisible to that team | | ASA Discovery campaigns | Category affe
- Initial Assessment
- Why Category Matters
- App Store Categories (memorize the structure)
- Google Play Categories
- Category Selection Framework
- Common Category Trade-offs
- When to Switch Categories
- Mechanics of Switching
- Output Template
- Category-Specific Notes
- Common Mistakes
- Cross-Skill Handoffs
What does the category-positioning skill do?
When the user wants to choose, change, or evaluate their App Store / Google Play category and subcategory — including primary vs secondary category trade-offs, chart-rank competitive analysis, category-driven discoverability, and how category choice affects featuring eligibility. Use when the user mentions "which category", "App Store category", "primary category", "secondary category", "change my category", "Health & Fitness vs Lifestyle", "Productivity vs Utilities", "rank higher in a smaller category", "category chart", "subcategory", "Play Store category", or "should I switch categories".
How do I install it?
Run `npx skills add Eronred/aso-skills --skill category-positioning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Eronred/aso-skills, a repository with 1,708 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.