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, see metadata-optimization. For auditing current keyword performance, see aso-audit.
- Installs
- 3.7K
- Last 24h
- +16
- Trending rank
- #6873
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/appeeky/aso-skills --skill keyword-research- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads keyword-research automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
What does the keyword-research skill do?
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.
How do I install keyword-research?
Run npx skills add https://github.com/appeeky/aso-skills --skill keyword-research in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/keyword-research/ (personal) or .claude/skills/keyword-research/ (project).
Which AI agents can use keyword-research?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is keyword-research safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains keyword-research?
It is published by appeeky in appeeky/aso-skills. It has 3,741 recorded installs.
More from appeeky/aso-skills
aso-audit
appeeky/aso-skills
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
monetization-strategy
appeeky/aso-skills
When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.
metadata-optimization
appeeky/aso-skills
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
competitor-analysis
appeeky/aso-skills
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
screenshot-optimization
appeeky/aso-skills
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
app-marketing-context
appeeky/aso-skills
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。