agentleFS
EronredEronred/aso-skills/skills/keyword-research/SKILL.md

keyword-research

Skill2.2k starsChanged 9 months agoMITView on GitHub

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.

54 other projects use a version of this, 2 of them edited.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

Used with

Projects with it also use link-prospecting, seo-project-setup and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JwuthriSkill

    link-prospecting

    Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.

    Also in 11 projects that use this

  • JwuthriSkill

    seo-project-setup

    Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.

    Also in 11 projects that use this

  • liangdabiaoSkill

    review-analysis

    对亚马逊商品评论进行深度分析,自动识别产品痛点、分析退货原因,生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.

    Also in 5 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 12 projects that use this

  • opencueSkill

    serp-analysis

    Use when the user asks to "analyze SERPs"; reviews ranking factors, features, intent, AI Overviews, and snippets. SERP分析/搜索结果

    Also in 6 projects that use this

  • +5 more from Jwuthri

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 48 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for app-marketing-context.md — read it for app context, competitors, and goals

    line 14
  2. Distinctive:

    Ask for the App ID (to understand current rankings)

    line 15
  3. Distinctive:

    Ask for target country (default: US)

    line 16
  4. Distinctive:

    Ask for seed keywords — 3-5 words that describe the app's core function

    line 17
  5. Distinctive:

    Ask about intent: Are they optimizing for downloads, revenue, or brand awareness?

    line 18
  6. Distinctive:

    Start with the user's seed keywords and expand using multiple methods:

    line 24
  7. Distinctive:

    Use each seed keyword to get autocomplete suggestions

    line 27
  8. Distinctive:

    Look for keywords where competitors rank poorly (opportunity)

    line 34
  9. Distinctive:

    Consider how users actually describe the problem (not the solution)

    line 42
  10. Distinctive:

    Must appear in title or subtitle

    line 76

“Common” is measured: kept by at least 6 in 10 of the 48 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

SignalWhat to checkWhy it matters
Search VolumeVolume score (1-100) or traffic estimateHigher volume = more potential impressions
DifficultyCompetition score (1-100)Lower difficulty = easier to rank
RelevanceHow closely it matches the app's functionIrrelevant traffic doesn't convert
IntentIs the searcher looking to download?"how to edit photos" vs "photo editor app"
Current RankWhere 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:

KeywordVolumeDifficultyRelevanceOpportunityCurrent RankAction
[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:

KeywordYour RankCompetitor 1Competitor 2Competitor 3Gap?

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.