# Aso Skill

> Query ASO Skill for current Apple App Store search rankings, autocomplete suggestions, keyword difficulty and popularity, app metadata, credit balances, and credit-pack discovery. Use for live App Store keyword or competitor research. Do not use for Android data, download or revenue estimates, historical rankings, or predictions.

- Skill: `aso-skill/aso-skill-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add aso-skill/aso-skill-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aso-skill/aso-skill-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: ASO-Skill (https://skillmd.com/u/aso-skill)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aso-skill/aso-skill-2

---


# Use ASO Skill

Prefer the connected ASO Skill MCP tools. ASO Skill is independent of Apple.

## Boundaries

- Use current App Store search results, autocomplete suggestions, keyword difficulty (0–100), keyword popularity (1–100), and metadata for known App Store IDs.
- Do not claim Android data, downloads, revenue, historical rankings, or future ranking outcomes.
- Successful search, autocomplete, popularity, and app lookup calls cost one credit. Balance and pack discovery are free.
- Minimize paid calls and batch up to 10 app IDs in one lookup.
- Never request or expose API keys. The MCP client handles OAuth.

## Choose tools

- `search_app_store`: current ranked results and keyword difficulty; one credit.
- `autocomplete_app_store_keywords`: up to ten platform-specific keyword completions; one credit.
- `get_keyword_popularity`: current keyword popularity and source; one credit.
- `lookup_app_store_apps`: metadata for 1–10 numeric app IDs; one credit per batch.
- `get_credit_balance`: available and used credits; free.
- `list_credit_packs`: current prepaid pack choices; free and read-only.

If storefront or platform is absent, infer it from context or default to `US` and `iphone`, and state the assumption. Popularity has no platform parameter.

## Interpret results

- Report storefront, platform when relevant, `fetchedAt`, and cache state when freshness matters.
- Search is fresh for one hour; a `stale` search fallback is never older than 24 hours. Autocomplete is fresh for 30 days per storefront and platform. Optional result fields may be absent when app-summary enrichment is throttled.
- Keep difficulty and popularity distinct unless the user asks for a labeled heuristic.
- Report missing app IDs instead of silently omitting them.
- Identify popularity source when material. `autocomplete` is a conservative 6–10 estimate for a censored low-volume term; `fallback` means no stronger signal was available.

## Handle failures

- Fix invalid requests instead of retrying them.
- On insufficient credits, call `list_credit_packs` once and present choices. Do not initiate payment through MCP.
- Honor `Retry-After` for throttling or temporary failures.
- Do not automatically retry an ambiguous network failure because a successful first call may have consumed a credit.

Read [references/api.md](references/api.md) for response and retry details.