AGENT SKILLBY ERONRED
Keyword research
AT A GLANCE
Keyword research is an agent skill for SEO. When the user wants to discover, evaluate, or prioritize App Store keywords. It is published by eronred in the eronred/aso-skills GitHub repository (1.8K stars) under the MIT license. Install it with: npx skills add eronred/aso-skills --skill keyword-research
- SOURCE REPOSITORY
- eronred/aso-skills (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- SKILL.MD SIZE
- 4.8 KB135 LINES
QUICK ANSWER
- WHAT IT IS01
- 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. The value is a focused slice of competitive research judgment, useful when several similar skills cover the same ground.
- INPUTS02
- Context for competitive research: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result for competitive research: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add eronred/aso-skills --skill keyword-researchREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 10
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#
- Check for
app-marketing-context.md— read it for app context, competitors, and goals - Ask for the App ID (to understand current rankings)
- Ask for target country (default: US)
- Ask for seed keywords — 3-5 words that describe the app's core function
- 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:
- Immediate changes to make
- Keywords to start tracking
- 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 metadataaso-audit— Broader audit that includes keyword performancecompetitor-analysis— Deep dive into competitor keyword strategieslocalization— Keyword research for international markets
FAQ
07 QUESTIONS
01What is the Keyword research agent 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. It is listed under SEO and go-to-market in the 100xLab agent skills directory.
02How do I install Keyword research in Cursor, Claude Code, or Codex?
Run npx skills add eronred/aso-skills --skill keyword-research in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Keyword research, not every skill in the repository.
03What does the Keyword research SKILL.md cover?
The SKILL.md includes sections on Initial Assessment, Research Process, Phase 1: Seed Expansion, Phase 2: Keyword Evaluation, Phase 3: Opportunity Scoring and Phase 4: Keyword Grouping. Read the full text on this page or in plain markdown at /resources/agent-skills/eronred-aso-skills--keyword-research--dafgxw/raw.
04Which agents can use Keyword research?
Keyword research installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Keyword research under?
The eronred/aso-skills repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is Keyword research free to use?
Reading, copying and installing Keyword research costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of Keyword research?
Keyword research comes from https://github.com/eronred/aso-skills, which has 1.8K GitHub stars. The SKILL.md is at https://github.com/eronred/aso-skills/blob/HEAD/skills/keyword-research/SKILL.md. The author is eronred.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Keyword research was written by its original authors and is published in eronred/aso-skills (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.