Keyword Research
nowork-studio/notfair-plugin
Finds, scores and groups keywords from a seed term or niche for SEO and AI search content strategies, with intent labels, difficulty estimates and topic clusters.
Run keyword research, classify by search intent, cluster into topical groups, and prioritize for content production.
Install SEO Keyword
$ npx skills add rampstackco/claude-skills --skill seo-keyword -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rampstackco/claude-skills seo-keyword --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-keyword .claude/skills/seo-keyword && rm -rf skills-srcUse ~/.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/
Install the "seo-keyword" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/seo-keyword into .claude/skills/seo-keyword/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword", 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 install https://github.com/rampstackco/claude-skills/tree/main/skills/seo-keywordType 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.
$ npx skills add rampstackco/claude-skills --skill seo-keyword -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rampstackco/claude-skills seo-keyword --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo-keyword .agents/skills/seo-keyword && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "seo-keyword" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/seo-keyword into .agents/skills/seo-keyword/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword", 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.
$ npx skills add rampstackco/claude-skills --skill seo-keyword -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rampstackco/claude-skills seo-keyword --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo-keyword .cursor/skills/seo-keyword && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "seo-keyword" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/seo-keyword into .cursor/skills/seo-keyword/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword", 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 https://github.com/rampstackco/claude-skills.git --path skills/seo-keyword--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rampstackco/claude-skills --skill seo-keyword -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rampstackco/claude-skills seo-keyword --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo-keyword .gemini/skills/seo-keyword && rm -rf skills-srcUse ~/.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/
Install the "seo-keyword" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/seo-keyword into .gemini/skills/seo-keyword/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword", 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.
$ gh skill install rampstackco/claude-skills seo-keywordInstalls 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).
$ npx skills add rampstackco/claude-skills --skill seo-keyword -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo-keyword .github/skills/seo-keyword && rm -rf skills-srcUse ~/.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/
Install the "seo-keyword" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/seo-keyword into .github/skills/seo-keyword/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword", 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.
$ npx skills add rampstackco/claude-skills --skill seo-keyword -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rampstackco/claude-skills seo-keyword --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo-keyword .opencode/skills/seo-keyword && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "seo-keyword" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/seo-keyword into .opencode/skills/seo-keyword/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-keyword", 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
seo-keyword- GitHub stars
- 940
- Token cost
- ~2k tokens
- SKILL.md length
- 990 words
- Files
- 4 (incl. references)
- Skills in repo
- 103
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run keyword research, classify by search intent, cluster into topical groups, and prioritize for content production.
- Works in 4 steps: Discover → Classify by intent → Cluster → …
- The user asks to do keyword research
- SKILL.md covers When to use, When NOT to use, Required inputs and The framework: 4 stages, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
SEO Keyword is an agent skill from rampstackco/claude-skills. Run keyword research, classify by search intent, cluster into topical groups, and prioritize for content production. Use this skill whenever the user asks to do keyword research, find target keywords, identify ranking opportunities, classify search intent, build a topical map, or plan a content strategy around what people search for. Triggers on keyword research, keyword strategy, search intent, keyword clustering, topic clusters, keyword difficulty, search volume, ranking opportunity, content gap, what should I…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `README.md`, `references/intent-classification-guide.md` and `references/keyword-research-template.md`).
It sits in Marketing & SEO, covering Keyword research and Content strategy. It works with Google Search Console. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.
When your agent uses it
- The user asks to do keyword research
- Find target keywords
- Identify ranking opportunities
- Classify search intent
Example prompts
- “/seo-keyword”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 482c9bf. 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
SEO Keyword loads about 2k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 174 tokens; SKILL.md has 990 words of instructions outside code blocks.
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 rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 990 words, ~2,004 tokens.
Download SKILL.mdSave it as
.claude/skills/seo-keyword/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- seo-keyword
- description
- Run keyword research, classify by search intent, cluster into topical groups, and prioritize for content production. Use this skill whenever the user asks to do keyword research, find target keywords, identify ranking opportunities, classify search intent, build a topical map, or plan a content strategy around what people search for. Triggers on keyword research, keyword strategy, search intent, keyword clustering, topic clusters, keyword difficulty, search volume, ranking opportunity, content gap, what should I write about, target keyword, primary keyword, secondary keyword, long-tail. Also triggers when planning a content calendar or new site without keywords yet defined.
- category
- seo-foundation
- catalog_summary
- Discovery, intent classification, clustering, prioritization
- display_order
- 3
Keyword Research
Find the queries worth ranking for, classify them by intent, cluster them into topics, and prioritize what to produce. Stack-agnostic. Tool-agnostic (works with any keyword tool).
When to use
- Starting a new site or content section
- Planning a content calendar
- Looking for ranking opportunities on an existing site
- Understanding search intent before writing
- Building topic clusters for internal linking
- Identifying content gaps vs competitors
When NOT to use
- Optimizing a single page where the target query is already known (use
seo-onpage) - Comparing your site to a competitor across many dimensions (use
seo-competitor) - Auditing existing content for performance (use
seo-content-audit)
Required inputs
- The site or topic area
- The target audience and what they need
- A keyword tool (Ahrefs, Semrush, Moz, Google Keyword Planner, or similar) OR access to search console for an existing site
- Optional: 3 to 5 known competitors to seed the research
If no tool is available, the skill still works using SERP inspection and search console data alone, but the volume estimates will be rough.
The framework: 4 stages
Stage 1: Discover
Cast a wide net. Sources:
- Seed terms from the brief or the user's vocabulary
- Competitor keywords (any keyword tool will export these)
- Search console queries for an existing site (find the page-1 and page-2 queries)
- Related searches and "People also ask" in actual SERPs
- Customer language (support tickets, sales calls, reviews)
- Forum and community language (Reddit, niche forums, Stack Overflow)
Goal: 200 to 500 candidate keywords for a typical content sprint. More if planning a year of content.
Stage 2: Classify by intent
Every keyword maps to one of four intents. Get this right or the rest is noise.
| Intent | Signal | Page type that wins |
|---|---|---|
| Informational | "how to," "what is," "why," "best way to" | Article, guide, tutorial |
| Navigational | brand or product name + modifier | Brand homepage, product page |
| Commercial | "best," "review," "vs," "comparison," "alternatives" | Listicle, comparison, review |
| Transactional | "buy," "price," "deal," "near me," "for sale" | Product page, category page |
A keyword tool's volume tells you the demand. The SERP tells you the intent. When in doubt, look at what's actually ranking. If page 1 is articles, the query is informational. If page 1 is product pages, it's transactional.
Hybrid intents exist. "Best running shoes" is commercial-investigational. "Best running shoes under $100" is the same intent narrowed by a budget filter. Treat hybrids as their dominant intent and note the modifier.
Stage 3: Cluster
Group keywords that should target the same page (or topic cluster).
Two clustering approaches:
Approach A: SERP overlap. If two keywords share at least 3 of the top 10 results, they target the same page. This is mechanical and reliable.
Approach B: Topical relevance. Group keywords by the underlying topic, not just word overlap. "How to start a podcast" and "podcast equipment for beginners" are the same topic, different facets.
Use both. A typical cluster has:
- 1 primary keyword (highest volume, broadest intent)
- 5 to 15 secondary keywords (variations and long-tails)
- 1 page that targets them all
Stage 4: Prioritize
For each cluster, score on three dimensions:
Opportunity (1 to 5):
- Volume (raw search demand)
- Click potential (some queries answer themselves in the SERP, lowering CTR)
- Conversion potential (does this query attract buyers or browsers?)
Difficulty (1 to 5):
- Domain authority of top results
- Backlink count of top results
- Content depth and freshness of top results
- Whether the SERP has features (featured snippets, AI overview, video carousel) that compete with organic
Strategic fit (1 to 5):
- Does it serve our audience?
- Does it support our positioning?
- Does it link to commercial pages naturally?
Priority score = Opportunity + Strategic fit - Difficulty.
Rank the clusters. Top 20 percent get produced first.
Show full SKILL.md (384 more words)Show less
Workflow
- Define the scope. What site, what topic area, what audience.
- Run discovery. Pull seeds, competitor exports, search console data, SERP inspections. Aim for 200 to 500 candidates.
- Deduplicate and clean. Remove obvious junk, brand misspellings, irrelevant terms.
- Classify by intent. Mark each keyword.
- Cluster. Group into topical clusters. Aim for 20 to 50 clusters.
- Score each cluster on opportunity, difficulty, and strategic fit.
- Prioritize. Rank by composite score. Identify the top 10 to 20 clusters to produce first.
- Output. Use the template in
references/keyword-research-template.md.
Failure patterns
- Chasing volume without intent. A 10,000-volume informational keyword does not drive purchases. Match query to commercial outcome.
- Targeting impossibly competitive keywords. New sites cannot rank for "credit cards." Find the underserved long-tail variant.
- Ignoring search console. Existing sites already rank for queries they did not target. These are the easiest wins.
- Treating clusters as one-keyword-per-page. A page can target 10 to 30 related keywords. One-keyword-per-page leads to thin, cannibalized content.
- Ignoring SERP features. A query with a featured snippet, AI overview, and a video carousel above the organic results may not be worth pursuing.
- Static keyword research. Search demand shifts. Refresh the research at least annually for evergreen sites, quarterly for fast-moving topics.
Output format
Default output: a spreadsheet (CSV or sheet) with one row per keyword and one row per cluster, plus a markdown summary with the top 10 to 20 clusters detailed.
Recommended columns for the keyword sheet:
| Column | Source |
|---|---|
| Keyword | Discovery |
| Volume | Tool |
| Difficulty | Tool |
| Intent | Manual classification |
| SERP features | Manual or tool |
| Cluster | Stage 3 |
| Cluster role (primary/secondary) | Stage 3 |
| Opportunity score | Stage 4 |
| Strategic fit | Stage 4 |
| Priority | Composite |
| Notes | Free text |
If required data is unavailable
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
Reference files
references/keyword-research-template.md- Spreadsheet column definitions and a markdown summary template.references/intent-classification-guide.md- Detailed examples of each of the four intent categories.
© rampstackco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/seo-keyword of rampstackco/claude-skills.
- SKILL.md
- README.md
- references/intent-classification-guide.md
- references/keyword-research-template.md
Open the folder on GitHubat commit 482c9bf
Compare with similar skills
SEO Keyword 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| SEO Keyword this skillrampstackco/claude-skills | 940 | — | ~2k | Automated safety check: Pass | MIT | |
| Keyword Researchnowork-studio/notfair-plugin | 3.9k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Mkt SEO Opsevolution-foundation/evo-nexus | 545 | — | ~1.1k | Automated safety check: Notes | Custom licence | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 18k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| SEO Content Brief GeneratorAgriciDaniel/claude-seo | 18k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Strategic SEO PlanningAgriciDaniel/claude-seo | 18k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Mkt SEO Ops
evolution-foundation/evo-nexus
AI-powered SEO operations with keyword intelligence, competitor gap analysis, GSC optimization, and trend detection.
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.
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.
Strategic SEO Planning
AgriciDaniel/claude-seo
Builds an SEO strategy for a new or existing site: discovery, competitor analysis, site architecture, content plan, technical foundation and a four-phase roadmap.
Search Console Content Planner
nowork-studio/notfair-plugin
Turns Google Search Console data into a dated content calendar by finding striking-distance queries and unanswered intent, ready to hand to a writer.
More from rampstackco/claude-skills
All 103 skills in this repoAfter Action Report
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
Analytics Strategy
rampstackco/claude-skills
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.
Brand Style Guide
rampstackco/claude-skills
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.
Brand Voice
rampstackco/claude-skills
Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.
Content And Copy
rampstackco/claude-skills
Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.
Content Strategy
rampstackco/claude-skills
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.
Related
Works with
Categories
Questions about SEO Keyword
What does SEO Keyword do?
Run keyword research, classify by search intent, cluster into topical groups, and prioritize for content production. SEO Keyword is an agent skill from rampstackco/claude-skills. Run keyword research, classify by search intent, cluster into topical groups, and prioritize for content production.
When should I use SEO Keyword?
SEO Keyword fits situations like: the user asks to do keyword research; find target keywords; identify ranking opportunities; classify search intent.
How do I install SEO Keyword in Claude Code?
Run `npx skills add rampstackco/claude-skills --skill seo-keyword -a claude-code`. Or copy the skill folder (skills/seo-keyword in rampstackco/claude-skills) into .claude/skills/seo-keyword in your project. Claude Code loads it when a task matches its description.
How do I install SEO Keyword in Codex?
Run `npx skills add rampstackco/claude-skills --skill seo-keyword -a codex`. Or copy the skill folder (skills/seo-keyword in rampstackco/claude-skills) into .agents/skills/seo-keyword in your project. Codex loads it when a task matches its description.
Can I use SEO Keyword 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 rampstackco/claude-skills --skill seo-keyword -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-keyword, .gemini/skills/seo-keyword, .github/skills/seo-keyword and .opencode/skills/seo-keyword in your project.
What does SEO Keyword need to run?
SKILL.md names no scripts, command-line tools or credentials: SEO Keyword is instructions for the agent only.
Does SEO Keyword 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 SEO Keyword 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 SEO Keyword use?
SEO Keyword 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 SEO Keyword use?
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.5k tokens, read only when the agent opens those files.
What are the alternatives to SEO Keyword?
Skills that share tags, products or a category with SEO Keyword: Keyword Research (nowork-studio/notfair-plugin, 3.9k stars), Mkt SEO Ops (evolution-foundation/evo-nexus, 545 stars), SEO Keyword Clustering (AgriciDaniel/claude-seo, 18k stars) and SEO Content Brief Generator (AgriciDaniel/claude-seo, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains SEO Keyword?
rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 940 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.
Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.