competitor-analysis Skill
当用户想用 ASOScan 将应用与已追踪的竞争对手进行比较时使用(关键词重合与差距、各竞对使用的商店分类、分类图表排名随时间的变化,以及评分走势),或通过商店 URL 添加新对手。当用户提到"把我的应用和竞对比较"、"我在和谁竞争"、"添加这个竞争对手"、"我表现如何"、"和他们比我是在进步还是落后"、"我的竞对用什么分类"或"分类排名"时也使用。要查看竞对的完整关键词列表,参见 keyword-spy。
安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。
技能指令原文(SKILL.md)
Competitor Analysis
Position the app against the rivals ASOScan tracks — where it's ahead, where it's
behind, and the single biggest lever — using real rank, rating, and keyword data.
When to use
- "Compare my app to my competitors."
- "Add
as a competitor." - "What category do my competitors use / how's my category rank vs theirs?"
Getting the data (two modes)
Pick the first mode that applies, then follow the steps below.
- ASOScan tools are connected (the ASOScan plugin or connector in ChatGPT or Claude, or any MCP client): use the tool named in the table. Do not ask for an API key and do not run
curl. Tool results have the same fields as the API responses below, and a list comes back insideitems. If a tool answers with a message instead of data (reconnect, credits used up, plan limit, "preparing"), pass that message on and stop. - No tools, but you can run shell commands and
ASOSCAN_API_KEYis set: make the API call in the table. Basehttps://asoscan.com/api/public/v1, headerAuthorization: Bearer $ASOSCAN_API_KEY, JSON with camelCase fields. Never print the key. Capture the HTTP status and handle errors as described at the bottom. - Neither: hand off to asoscan-setup. It explains how to connect ASOScan in ChatGPT or Claude, or how to create an API key.
ASOScan only sees the apps in the user's own account and the competitors they track. Every call uses API credits (failed calls are free). Before a call that costs more than 2 API credits, or one that uses AI, tell the user the cost and wait for a yes. Before any call that changes data, ask first.
| Step | Tool (connected) | API call (key) | API credits |
|---|---|---|---|
| Find the app | list_my_apps | GET /apps | free |
| One app's facts (category, rating) | get_app_details | GET /apps/{id} | free |
| Competitors | get_competitors | GET /apps/{id}/competitors?country= | free |
| Add a rival by store link (changes data) | add_competitor | POST /apps/{id}/competitors with { "storeUrl": "..." } | 2, ask first |
| Category rank over time | get_category_rank | GET /apps/{id}/category-rank?country=&days=30 | free |
| Rating history | get_rating_history | GET /apps/{id}/rating-history | free |
Steps
- Find the app —
GET /apps→{ id, name, category, rating, … }(your own
category is here).
- Competitors —
GET /apps/{id}/competitors?country=(free) →
[{ id, name, developer, iconUrl, rating, ratingCount, category }]. The
category is each competitor's primary store category — this answers "what
category do my competitors use?" (only the primary is exposed, not Apple's
secondary).
- Add a rival (if asked) —
POST /apps/{id}/competitors { "storeUrl": "…" }
(2 credits, write key). Confirm before writing.
- Category rank over time —
GET /apps/{id}/category-rank?country=&days=30
(free) → { category, country, rankType, currentRank, points[]{ date, rank } }.
- Rating trajectory —
GET /apps/{id}/rating-history(free) →
[{ rating, totalRatings, date }].
- Keyword overlap — pair with keyword-spy on each competitor for the gap list.
Category-rank and rating-history are per-app; to compare a competitor, run the same
reads on that competitor's app id (it must be a tracked competitor).
How to analyze
- Category placement — list each competitor's primary
categorynext to yours.
If rivals cluster in a different (or less crowded) category, flag it — category
choice is an ASO lever.
- Rank momentum — climbing or sliding over the window (
points)?
A point exists only for a date that was measured, so rank: null means **measured and
not in the tracked chart** — say "not charting yet", never "no data". Unmeasured dates
are absent, so a 30-day window may return fewer than 30 points. An app whose points are
all null is not broken data: it hasn't broken into the chart, and volume/authority is
the lever, not metadata.
- Rating gap — average
ratingand its direction vs competitors. - Keyword gap (highest-leverage) — relevant terms rivals win that you don't
target (from keyword-spy), ranked by relevance × volume.
- Positioning — one honest line (leader / challenger / niche) + the biggest lever.
Output template
### Competitive position — {App} ({country}) · credits left: {remaining}
| App | Category | Category rank (now → {N}d ago) | Rating (now → trend) |
|---|---|---|---|
| {you} | {your category} | … | … |
| {competitor} | {their category} | … | … |
**Keyword gaps** (they rank, you don't — relevant): …
**Biggest lever:** {one specific move}
**Next in ASOScan:** run `keyword-spy` per competitor, then `keyword-opportunities` + `metadata-audit`.
Errors, credits & honesty
401→ asoscan-setup ·403no API access (or read-only key on the add) ·402
out of credits · 404 not tracked · 503 not enabled yet. Reads here are
free; only adding a competitor costs credits.
- Compete on breadth, coverage, and momentum. Clean numbers — don't concede a
rival's data is "more accurate", and don't claim a tactic guarantees a rank change.
- Full reference:
Related
- keyword-spy — reverse-lookup each competitor's keywords.
- keyword-opportunities — turn gaps into a tracked target list.
- review-insights — compare what users say (add rivals as competitors first).