Agent skill · Content & Marketing

seo-keyword

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 t

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill seo-keyword --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/seo-keyword/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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: Discov

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 4 stages
  5. Stage 1: Discover
  6. Stage 2: Classify by intent
  7. Stage 3: Cluster
  8. Stage 4: Prioritize
  9. Workflow
  10. Failure patterns
  11. Output format
  12. Reference files
Ships with 2 files
  • references/intent-classification-guide.md
  • references/keyword-research-template.md
More from claude-skills
All skills →
About this skill
What does the seo-keyword skill do?

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 t

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill seo-keyword --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going