agentleFS
AppKittieAppKittie/aso-mcp-skills/skills/keyword-research/SKILL.md

keyword-research

Skill8 starsChanged 18 days agoMITView on GitHub

When the user wants to discover, evaluate, or prioritize App Store or Google Play keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", "what keywords should I target", or "ASO keywords". For implementing keywords into metadata, see metadata-optimization. For broader app discovery, see app-discovery.

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

Adopted by

Most recently taken up by

Used with

Projects with it also use link-prospecting, seo-project-setup and 7 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

  • 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

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    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 seed keywords — 3–5 words that describe the app's core function

    line 15
  3. Very specific:

    Ask for store source if unclear (apple_mobile by default, google_mobile for Google Play)

    line 16
  4. Very specific:

    Ask for target country (default: US).

    line 17
  5. Distinctive:

    Ask about intent: downloads, revenue, or brand awareness?

    line 18
  6. Very specific:

    Start with batch_keyword_difficulty to evaluate the user's seed keywords (up to 10 at a time).

    line 24
  7. Very specific:

    Use search_apps to find competitors, then analyze which keywords they're likely targeting based on their titles and descriptions.

    line 43
  8. Distinctive:

    Must appear in title or subtitle

    line 51

“Common” is measured: kept by at least 6 in 10 of the 49 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 and Google Play search behavior, keyword indexing, and ranking algorithms. Your goal is to help the user discover high-value keywords and build a prioritized keyword strategy using AppKittie's keyword intelligence.

Initial Assessment

  1. Check for app-marketing-context.md — read it for app context, competitors, and goals
  2. Ask for seed keywords — 3–5 words that describe the app's core function
  3. Ask for store source if unclear (apple_mobile by default, google_mobile for Google Play)
  4. Ask for target country (default: US). Use get_supported_countries if unsure
  5. Ask about intent: downloads, revenue, or brand awareness?

Research Process

Phase 1: Seed Expansion & Evaluation

Start with batch_keyword_difficulty to evaluate the user's seed keywords (up to 10 at a time). Pass source: "google_mobile" for Google Play research; otherwise it defaults to apple_mobile.

Response fields:

  • popularity — search volume proxy (higher = more searches)
  • difficulty — competition score (higher = harder to rank)
  • appsCount — number of competing apps
  • trafficScore — estimated traffic potential

Results are auto-sorted by opportunity — best keywords first.

Phase 2: Deep Dive

For the top 3–5 keywords, use get_keyword_difficulty individually to see:

  • Top-ranking apps — who currently owns these keywords?
  • Are the top apps beatable? (low reviews, low ratings = opportunity)
  • Is there a gap between keyword volume and competition?

Phase 3: Competitor Keywords

Use search_apps to find competitors, then analyze which keywords they're likely targeting based on their titles and descriptions. Feed those keywords back into batch_keyword_difficulty.

Phase 4: Keyword Grouping

Group keywords into strategic buckets:

Primary Keywords (3–5)

  • Highest opportunity score
  • Must appear in title or subtitle
  • Define 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

Opportunity Scoring

Opportunity = (Popularity × 0.4) + ((100 - Difficulty) × 0.3) + (Relevance × 0.3)

Where Relevance is your manual assessment (0–100) of how well the keyword matches the app.

Output Format

Keyword Research Report

Summary:

  • Keywords analyzed: [N]
  • High-opportunity keywords found: [N]
  • Target country: [code]

Top Keywords by Opportunity:

KeywordPopularityDifficultyApps CountTraffic ScoreAction
[keyword][score][score][count][score]Primary / Secondary / Long-tail

Keyword Strategy:

Title (30 chars):     [primary keyword 1] + [primary keyword 2]
Subtitle (30 chars):  [secondary keywords forming a benefit statement]
Keyword Field (100):  [remaining keywords, comma-separated, no spaces]

Competitor Keyword Analysis:

CompetitorTheir Keywords (inferred)SharedUnique to Them

Recommendations:

  1. Immediate keyword changes to make
  2. Keywords to start tracking weekly
  3. Content/feature opportunities based on keyword demand

iOS Keyword Rules

  • 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
  • Title has highest weight for keyword ranking
  • Update quarterly — search trends change with seasons

Related Skills

  • metadata-optimization — Implement the keyword strategy into actual metadata
  • competitor-analysis — Deep dive into competitor keyword strategies
  • app-discovery — Find apps ranking for target keywords

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.