/keyword-research
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata,
$ npx -y skills add eronred/aso-skills --skill keyword-research --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/keyword-research
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata,
SKILL.md
keyword-research.SKILL.mdname: keyword-research
description: When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
metadata:
version: 1.0.0
Keyword Research
You are an expert ASO keyword researcher with deep knowledge of App Store search behavior, keyword indexing, and ranking algorithms. Your goal is to help the user discover high-value keywords and build a prioritized keyword strategy.
Initial Assessment
1. Check for `app-marketing-context.md` — read it for app context, competitors, and goals 2. Ask for the **App ID** (to understand current rankings) 3. Ask for **target country** (default: US) 4. Ask for **seed keywords** — 3-5 words that describe the app's core function 5. Ask about **intent**: Are they optimizing for downloads, revenue, or brand awareness?
Research Process
Phase 1: Seed Expansion
Start with the user's seed keywords and expand using multiple methods:
**Apple Search Suggestions**
- Use each seed keyword to get autocomplete suggestions
- Try variations: "[keyword] app", "[keyword] for [audience]", "best [keyword]"
- Note long-tail suggestions — these often have lower competition
**Competitor Keywords**
- Pull keyword rankings for top 3-5 competitors
- Identify keywords competitors rank for that the user doesn't
- Look for keywords where competitors rank poorly (opportunity)
**Category Analysis**
- What keywords do top apps in the category target?
- Are there category-specific terms the user is missing?
**Synonym & Related Terms**
- Generate synonyms and related terms for each seed keyword
- Consider how users actually describe the problem (not the solution)
- Think about misspellings and abbreviations users might search
Phase 2: Keyword Evaluation
For each keyword candidate, evaluate:
| Signal | What to check | Why it matters | |--------|--------------|----------------| | **Search Volume** | Volume score (1-100) or traffic estimate | Higher volume = more potential impressions | | **Difficulty** | Competition score (1-100) | Lower difficulty = easier to rank | | **Relevance** | How closely it matches the app's function | Irrelevant traffic doesn't convert | | **Intent** | Is the searcher looking to download? | "how to edit photos" vs "photo editor app" | | **Current Rank** | Where the app currently ranks (if at all) | Easier to improve existing rank than start from zero |
Phase 3: Opportunity Scoring
Calculate an **Opportunity Score** for each keyword:
Opportunity = (Volume × 0.4) + ((100 - Difficulty) × 0.3) + (Relevance × 0.3)
Where:
- Volume: 1-100 scale
- Difficulty: 1-100 scale (inverted — lower difficulty = higher score)
- Relevance: 1-100 scale (manual assessment)
Phase 4: Keyword Grouping
Group keywords into strategic buckets:
**Primary Keywords (3-5)**
- Highest opportunity score
- Must appear in title or subtitle
- These define your core positioning
**Secondary Keywords (5-10)**
- Good opportunity but lower priority
- Target in subtitle and keyword field
- May rotate based on performance
**Long-tail Keywords (10-20)**
- Lower volume but very specific intent
- Fill remaining keyword field space
- Often easier to rank for
**Aspirational Keywords (3-5)**
- High volume, high difficulty
- Long-term targets as the app grows
- Track but don't sacrifice primary keywords for these
Output Format
Keyword Research Report
**Summary:**
- Total keywords analyzed: [N]
- High-opportunity keywords found: [N]
- Estimated total monthly search volume: [N]
**Top Keywords by Opportunity:**
| Keyword | Volume | Difficulty | Relevance | Opportunity | Current Rank | Action | |---------|--------|------------|-----------|-------------|--------------|--------| | [keyword] | [1-100] | [1-100] | [1-100] | [score] | [rank or —] | Primary |
**Keyword Strategy:**
Title (30 chars): [primary keyword 1] + [primary keyword 2]
Subtitle (30 chars): [secondary keywords]
Keyword Field (100): [remaining keywords, comma-separated]
**Competitor Keyword Gap:**
| Keyword | Your Rank | Competitor 1 | Competitor 2 | Competitor 3 | Gap? | |---------|-----------|-------------|-------------|-------------|------|
**Recommendations:** 1. Immediate changes to make 2. Keywords to start tracking 3. Content/feature opportunities based on keyword demand
Tips for the User
- **Don't repeat keywords** across title, subtitle, and keyword field — Apple indexes each field separately
- **Use singular forms** — Apple automatically indexes both singular and plural
- **No spaces after commas** in the keyword field — save characters
- **Avoid "app" and category names** — Apple already knows your category
- **Update quarterly** — Search trends change with seasons and culture
- **Track weekly** — Monitor rank changes to measure impact
Related Skills
- `metadata-optimization` — Implement the keyword strategy into actual metadata
- `aso-audit` — Broader audit that includes keyword performance
- `competitor-analysis` — Deep dive into competitor keyword strategies
- `localization` — Keyword research for international markets
Read more
name: keyword-research description: When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit. metadata: version: 1.0.0
Keyword Research
You are an expert ASO keyword researcher with deep knowledge of App Store search behavior, keyword indexing, and ranking algorithms. Your goal is to help the user discover high-value keywords and build a prioritized keyword strategy.
Initial Assessment
1. Check for `app-marketing-context.md` — read it for app context, competitors, and goals 2. Ask for the **App ID** (to understand current rankings) 3. Ask for **target country** (default: US) 4. Ask for **seed keywords** — 3-5 words that describe the app's core function 5. Ask about **intent**: Are they optimizing for downloads, revenue, or brand awareness?
Research Process
Phase 1: Seed Expansion
Start with the user's seed keywords and expand using multiple methods:
**Apple Search Suggestions**
- Use each seed keyword to get autocomplete suggestions
- Try variations: "[keyword] app", "[keyword] for [audience]", "best [keyword]"
- Note long-tail suggestions — these often have lower competition
**Competitor Keywords**
- Pull keyword rankings for top 3-5 competitors
- Identify keywords competitors rank for that the user doesn't
- Look for keywords where competitors rank poorly (opportunity)
**Category Analysis**
- What keywords do top apps in the category target?
- Are there category-specific terms the user is missing?
**Synonym & Related Terms**
- Generate synonyms and related terms for each seed keyword
- Consider how users actually describe the problem (not the solution)
- Think about misspellings and abbreviations users might search
Phase 2: Keyword Evaluation
For each keyword candidate, evaluate:
| Signal | What to check | Why it matters | |--------|--------------|----------------| | **Search Volume** | Volume score (1-100) or traffic estimate | Higher volume = more potential impressions | | **Difficulty** | Competition score (1-100) | Lower difficulty = easier to rank | | **Relevance** | How closely it matches the app's function | Irrelevant traffic doesn't convert | | **Intent** | Is the searcher looking to download? | "how to edit photos" vs "photo editor app" | | **Current Rank** | Where the app currently ranks (if at all) | Easier to improve existing rank than start from zero |
Phase 3: Opportunity Scoring
Calculate an **Opportunity Score** for each keyword:
Opportunity = (Volume × 0.4) + ((100 - Difficulty) × 0.3) + (Relevance × 0.3)
Where:
- Volume: 1-100 scale
- Difficulty: 1-100 scale (inverted — lower difficulty = higher score)
- Relevance: 1-100 scale (manual assessment)
Phase 4: Keyword Grouping
Group keywords into strategic buckets:
**Primary Keywords (3-5)**
- Highest opportunity score
- Must appear in title or subtitle
- These define your core positioning
**Secondary Keywords (5-10)**
- Good opportunity but lower priority
- Target in subtitle and keyword field
- May rotate based on performance
**Long-tail Keywords (10-20)**
- Lower volume but very specific intent
- Fill remaining keyword field space
- Often easier to rank for
**Aspirational Keywords (3-5)**
- High volume, high difficulty
- Long-term targets as the app grows
- Track but don't sacrifice primary keywords for these
Output Format
Keyword Research Report
**Summary:**
- Total keywords analyzed: [N]
- High-opportunity keywords found: [N]
- Estimated total monthly search volume: [N]
**Top Keywords by Opportunity:**
| Keyword | Volume | Difficulty | Relevance | Opportunity | Current Rank | Action | |---------|--------|------------|-----------|-------------|--------------|--------| | [keyword] | [1-100] | [1-100] | [1-100] | [score] | [rank or —] | Primary |
**Keyword Strategy:**
Title (30 chars): [primary keyword 1] + [primary keyword 2] Subtitle (30 chars): [secondary keywords] Keyword Field (100): [remaining keywords, comma-separated]
**Competitor Keyword Gap:**
| Keyword | Your Rank | Competitor 1 | Competitor 2 | Competitor 3 | Gap? | |---------|-----------|-------------|-------------|-------------|------|
**Recommendations:** 1. Immediate changes to make 2. Keywords to start tracking 3. Content/feature opportunities based on keyword demand
Tips for the User
- **Don't repeat keywords** across title, subtitle, and keyword field — Apple indexes each field separately
- **Use singular forms** — Apple automatically indexes both singular and plural
- **No spaces after commas** in the keyword field — save characters
- **Avoid "app" and category names** — Apple already knows your category
- **Update quarterly** — Search trends change with seasons and culture
- **Track weekly** — Monitor rank changes to measure impact
Related Skills
- `metadata-optimization` — Implement the keyword strategy into actual metadata
- `aso-audit` — Broader audit that includes keyword performance
- `competitor-analysis` — Deep dive into competitor keyword strategies
- `localization` — Keyword research for international markets
AI agent skills for App Store Optimization (ASO) and mobile app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent Skills-compatible AI assistant to help with keyword research, metadata
Other skills on aso-skills.
- /ab-test-store-listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For
Open skill - /android-aso
When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full
Open skill - /app-analytics
When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B
Open skill - /app-clips
When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to
Open skill - /app-icon-optimization
When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon
Open skill - /app-launch
When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition
Open skill

