# Aso Router

Single entry point that routes any ASO, App Store, Google Play, app marketing, paid UA...

- Repository: https://github.com/appeeky/aso-skills (2243 stars)
- Category: Mobile
- License: MIT
- Last updated: 2026-10-06
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add appeeky/aso-skills --skill aso-router -g -a claude-code -y`
Codex: `npx skills add appeeky/aso-skills --skill aso-router -g -a codex -y`
Cursor: `npx skills add appeeky/aso-skills --skill aso-router -g -a cursor -y`
Gemini CLI: `npx skills add appeeky/aso-skills --skill aso-router -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add appeeky/aso-skills`

## Description

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 skill in this library. Use FIRST whenever the user mentions an app, App Store, Play Store, keywords, ranking, downloads, revenue, subscriptions, screenshots, icon, reviews, competitors, charts, in-app events, launch, press, or ads, but the right specialized skill is not obvious. Triggers: "/aso-router", "/aso-skill", "/aso", "aso help", "help me with my app", "I need ASO", "which skill should I use", or any ambiguous app-marketing request. Skip this router only when the user explicitly invokes a specific skill (e.g. /aso-audit, /keyword-research).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# ASO Router

You are the routing layer for the ASO Skills library. Your single job is to read the user's request, pick the **one** (or at most three) specialist skill(s) that best fit, and load them. Do NOT try to answer the ASO question yourself, your job is dispatch, not delivery.

## How to Use This Skill

1. Read the user's message.
2. Match it against the routing table below.
3. Announce the chosen skill in one short sentence: `→ Loading: <skill-name>` (and 2nd/3rd if relevant).
4. Read `skills/<skill-name>/SKILL.md` and follow it.
5. If the user's intent is genuinely ambiguous, ask **one** clarifying question from the disambiguation playbook below.

Never load more than 3 skills at once. If you would, ask the user to narrow down.

## Routing Table

Match by intent first, then by exact phrase. Top match wins.

### ASO Core

| User intent / phrase | Route to |
|---|---|
| "audit my listing", "ASO score", "why am I not ranking", "review my app store page" | `aso-audit` |
| "find keywords", "keyword research", "search volume", "keyword difficulty", "keyword ideas" | `keyword-research` |
| "write my title", "optimize subtitle", "keyword field", "rewrite description", "character limits" | `metadata-optimization` |
| "compare to competitors", "keyword gap", "what are competitors doing", "competitive teardown" | `competitor-analysis` |
| "track competitors weekly", "alert me when competitor changes", "monitor competitor metadata" | `competitor-tracking` |
| "Google Play", "Play Store", "Android ASO", "short description", "indexed full description" | `android-aso` |
| "localize", "translate listing", "expand to new countries", "international markets" | `localization` |
| "seasonal", "holiday", "Christmas", "Valentine's", "summer", "back to school", "trending moment" | `seasonal-aso` |

### Creative

The rest: https://github.com/appeeky/aso-skills/blob/HEAD/skills/aso-router/SKILL.md