Agent skill

Keyword Research

When the user wants to discover, evaluate, or prioritize App Store keywords.

Install Keyword Research

skills CLI

$ npx skills add appeeky/aso-skills --skill keyword-research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills keyword-research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/keyword-research .claude/skills/keyword-research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "keyword-research" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/keyword-research into .claude/skills/keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-research", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/appeeky/aso-skills/tree/main/skills/keyword-research

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add appeeky/aso-skills --skill keyword-research -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills keyword-research --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/keyword-research .agents/skills/keyword-research && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "keyword-research" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/keyword-research into .agents/skills/keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-research", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add appeeky/aso-skills --skill keyword-research -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills keyword-research --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/keyword-research .cursor/skills/keyword-research && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "keyword-research" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/keyword-research into .cursor/skills/keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-research", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/appeeky/aso-skills.git --path skills/keyword-research

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add appeeky/aso-skills --skill keyword-research -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills keyword-research --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/keyword-research .gemini/skills/keyword-research && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "keyword-research" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/keyword-research into .gemini/skills/keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-research", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install appeeky/aso-skills keyword-research

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add appeeky/aso-skills --skill keyword-research -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/keyword-research .github/skills/keyword-research && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "keyword-research" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/keyword-research into .github/skills/keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-research", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add appeeky/aso-skills --skill keyword-research -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills keyword-research --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/keyword-research .opencode/skills/keyword-research && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "keyword-research" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/keyword-research into .opencode/skills/keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-research", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: keyword-research
GitHub stars: 2.2k
Token cost: ~1.3k tokens
SKILL.md length: 580 words
Files: 1
Skills in repo: 39
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

When the user wants to discover, evaluate, or prioritize App Store keywords.

Works in 4 steps: Seed Expansion → Keyword Evaluation → Opportunity Scoring → …
Wants to discover
SKILL.md covers Initial Assessment, Research Process, Output Format and Tips for the User, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Keyword Research is an agent skill from appeeky/aso-skills. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Keyword research and App store release. The repository describes itself as: AI agent skills for App Store Optimization (ASO) and app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent… The licence is MIT.

When your agent uses it

Wants to discover
Prioritize App Store keywords
The user mentions keyword research
Keyword difficulty

Example prompts

“keyword research”
“find keywords”
“search volume”
“/keyword-research”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Seed Expansion
Keyword Evaluation
Opportunity Scoring
Keyword Grouping

What it can do on your machine

Read from SKILL.md and the folder at commit 3919d7c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Keyword Research loads about 1.3k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 580 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~95
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from appeeky/aso-skills at commit 3919d7c, republished under its MIT licence (© appeeky). 580 words, ~1,341 tokens.

Download SKILL.mdSave it as .claude/skills/keyword-research/SKILL.md (or your agent's skills folder).

name: keyword-research
description: 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.
metadata.version: 1.0.0

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)

Show full SKILL.md (253 more words)Show less

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

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

Files

Just SKILL.md in skills/keyword-research of appeeky/aso-skills.

Open the folder on GitHubat commit 3919d7c

Compare with similar skills

Keyword Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Keyword Research compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Keyword Research this skillappeeky/aso-skills	2.2k	—	~1.3k	Automated safety check: Pass	MIT	3 days ago
Launch Asset Packageraaron-he-zhu/aaron-marketing-skills	2.9k	—	~3.2k	Automated safety check: Pass	Apache-2.0	yesterday
Krankie Auditn0an/VivaDicta	131	—	~1.3k	Automated safety check: Pass	MIT	4 days ago
SEO Keyword ClusteringAgriciDaniel/claude-seo	19k	2 repos	~3.3k	Automated safety check: Pass	MIT	5 days ago
Evaluate Skillevery-app/open-seo	23k	—	~1.8k	Automated safety check: Notes	MIT	yesterday
SEO Content Brief GeneratorAgriciDaniel/claude-seo	19k	2 repos	~2.6k	Automated safety check: Pass	MIT	5 days ago

Similar skills

Launch Asset Packager
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "package the launch assets", "build a press kit", or "prep the store listing and go-live checklist"; produces a tier-scoped launch asset manifest with…
2.9k GitHub stars~3.2k tokensUpdated yesterday
Marketing & SEOAuto-check passed
Krankie Audit
n0an/VivaDicta
Run an ASO audit on canonical App Store metadata under ./metadata, then a krankie-based competitor keyword-gap analysis (no Astro subscription).
131 GitHub stars~1.3k tokensUpdated 4 days ago
MobileAuto-check passed
SEO Keyword Clustering
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
19k GitHub starsUsed in 2 repos~3.3k tokens
Marketing & SEOAuto-check passed
Evaluate Skill
every-app/open-seo
Test a candidate OpenSEO skill end to end by running fresh, isolated Codex sessions against the local backend and scoring the reports they save.
23k GitHub stars~1.8k tokensUpdated yesterday
Marketing & SEOAuto-check: notes
SEO Content Brief Generator
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
19k GitHub starsUsed in 2 repos~2.6k tokens
Marketing & SEOAuto-check passed
Blog Google
AgriciDaniel/claude-blog
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
2.3k GitHub starsUsed in 1 repo~3.3k tokens
Marketing & SEOAuto-check: notes

Questions about Keyword Research

What does Keyword Research do?

When the user wants to discover, evaluate, or prioritize App Store keywords. Keyword Research is an agent skill from appeeky/aso-skills. When the user wants to discover, evaluate, or prioritize App Store keywords.

When should I use Keyword Research?

Keyword Research fits situations like: wants to discover; prioritize App Store keywords; the user mentions keyword research; keyword difficulty.

How do I install Keyword Research in Claude Code?

Run `npx skills add appeeky/aso-skills --skill keyword-research -a claude-code`. Or copy the skill folder (skills/keyword-research in appeeky/aso-skills) into .claude/skills/keyword-research in your project. Claude Code loads it when a task matches its description.

How do I install Keyword Research in Codex?

Run `npx skills add appeeky/aso-skills --skill keyword-research -a codex`. Or copy the skill folder (skills/keyword-research in appeeky/aso-skills) into .agents/skills/keyword-research in your project. Codex loads it when a task matches its description.

Can I use Keyword Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add appeeky/aso-skills --skill keyword-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/keyword-research, .gemini/skills/keyword-research, .github/skills/keyword-research and .opencode/skills/keyword-research in your project.

What does Keyword Research need to run?

SKILL.md names no scripts, command-line tools or credentials: Keyword Research is instructions for the agent only.

Does Keyword Research access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Keyword Research safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Keyword Research use?

Keyword Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Keyword Research use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Keyword Research?

Skills that share tags, products or a category with Keyword Research: Launch Asset Packager (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Krankie Audit (n0an/VivaDicta, 131 stars), SEO Keyword Clustering (AgriciDaniel/claude-seo, 19k stars) and Evaluate Skill (every-app/open-seo, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Keyword Research?

appeeky (a GitHub organization) maintains it in appeeky/aso-skills, which has 2,159 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 6, 2026.

Source: appeeky/aso-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Keyword Research

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Keyword Research

Initial Assessment

Research Process

Phase 1: Seed Expansion

Phase 2: Keyword Evaluation

Phase 3: Opportunity Scoring

Phase 4: Keyword Grouping

Output Format

Keyword Research Report

Tips for the User

Related Skills

Files

Compare with similar skills

Similar skills

More from appeeky/aso-skills

Related

Questions about Keyword Research