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
- asospy/asospy-agent-skillstheir own version, first seen Nov 15, 2026
- GroMarketing/keyword-planner-mcptheir own version, first seen Nov 15, 2026
- HyunSeob/skillstheir own version, first seen Nov 15, 2026
- nowork-studio/notfair-plugintheir own version, first seen Nov 11, 2026
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- kostja94/marketing-skillstheir own version, first seen Nov 8, 2026
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.
JwuthriSkilllink-prospecting
Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.
Also in 11 projects that use this
JwuthriSkillseo-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-ltdSkillkeyword-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
opencueSkillserp-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
Other versions55 projects use a version of this.
Word for word · 1
- Nirusan/claude-config★ 7100% same
Edited · 2
- Kungfookenny123/aso-skills★ 238% same
- trysonar/skills★ 013% same
Wrote their own version · 52
- every-app/open-seo★ 28ksame name
- Ryze-AI-Adgent/open-seo-mcp-skills★ 8.4ksame name
- nowork-studio/notfair-plugin★ 4.2ksame name
- nowork-studio/toprank★ 4.1ksame name
- Jwuthri/Tracely-ai★ 1.3ksame name
- liangdabiao/amazon-sorftime-research-MCP-skill★ 1.1ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- kostja94/marketing-skills★ 1.1ksame name
- jwuthri-cloud/Tracely-ai★ 979same name
- indranilbanerjee/digital-marketing-pro★ 934same name
42 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- appkittieSkill
- ad-intelligenceSkill
- app-discoverySkill
- app-marketing-contextSkill
- competitor-analysisSkill
- creator-discoverySkill
- growth-analysisSkill
- metadata-optimizationSkill
- onboarding-analysisSkill
- revenue-analysisSkill
- review-analysisSkill
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
- Very specific: line 14
Check for app-marketing-context.md — read it for app context, competitors, and goals
- Distinctive: line 15
Ask for seed keywords — 3–5 words that describe the app's core function
- Very specific: line 16
Ask for store source if unclear (apple_mobile by default, google_mobile for Google Play)
- Very specific: line 17
Ask for target country (default: US).
- Distinctive: line 18
Ask about intent: downloads, revenue, or brand awareness?
- Very specific: line 24
Start with batch_keyword_difficulty to evaluate the user's seed keywords (up to 10 at a time).
- Very specific: line 43
Use search_apps to find competitors, then analyze which keywords they're likely targeting based on their titles and descriptions.
- Distinctive: line 51
Must appear in title or subtitle
“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.
Files
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
- Check for
app-marketing-context.md— read it for app context, competitors, and goals - Ask for seed keywords — 3–5 words that describe the app's core function
- Ask for store source if unclear (
apple_mobileby default,google_mobilefor Google Play) - Ask for target country (default: US). Use
get_supported_countriesif unsure - 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 appstrafficScore— 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:
| Keyword | Popularity | Difficulty | Apps Count | Traffic Score | Action |
| [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:
| Competitor | Their Keywords (inferred) | Shared | Unique to Them |
Recommendations:
- Immediate keyword changes to make
- Keywords to start tracking weekly
- 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 metadatacompetitor-analysis— Deep dive into competitor keyword strategiesapp-discovery— Find apps ranking for target keywords
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
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.

