Discovers high-value keywords with intent classification, difficulty scoring, and topic clustering for SEO content strategy.
Works with
Classifies keywords by search intent (informational, commercial, transactional, navigational) and assigns opportunity scores based on volume, difficulty, and business value
Integrates with Ahrefs, SEMrush, Google Keyword Planner, and Google Search Console; also accepts manual data input for sites without tool access
Groups keywords into topic clusters with pill
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionkeyword-researchExecute the skills CLI command in your project's root directory to begin installation:
Fetches keyword-research from aaron-he-zhu/seo-geo-claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate keyword-research. Access via /keyword-research in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
873
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
873
stars
SEO & GEO Skills Library · 20 skills for SEO + GEO · ClawHub · skills.sh System Mode: This research skill follows the shared Skill Contract and State Model.
Discovers, analyzes, and prioritizes keywords for SEO and GEO content strategies. Identifies high-value opportunities based on search volume, competition, intent, and business relevance.
System role: Research layer skill. It turns market signals into reusable strategic inputs for the rest of the library.
Use this when the conversation involves any of these situations — even if the user does not use SEO terminology:
Use this whenever the task needs reusable market intelligence that should influence strategy, not just an ad hoc answer.
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Research keywords for [topic/product/service]
Find keyword opportunities for a [industry] business targeting [audience]
Find low-competition keywords for [topic] with commercial intent
Identify question-based keywords for [topic] that AI systems might answer
What keywords is [competitor URL] ranking for that I should target?
Expected output: a prioritized research brief, evidence-backed findings, and a short handoff summary ready for memory/research/.
memory/research/.CLAUDE.md, memory/decisions.md, and memory/research/; hand canonical entity work to entity-optimizer.Next Best Skill below when the findings are ready to drive action.Note: All integrations are optional. This skill works without any API keys — users provide data manually when no tools are connected.
See CONNECTORS.md for tool category placeholders.
With ~~SEO tool + ~~search console connected: Automatically pull historical search volume data, keyword difficulty scores, SERP analysis, current rankings from ~~search console, and competitor keyword overlap. The skill will fetch seed keyword metrics, related keyword suggestions, and search trend data.
With manual data only: Ask the user to provide:
Proceed with the full analysis using provided data. Note in the output which metrics are from automated collection vs. user-provided data.
When a user requests keyword research:
At the start of each phase, announce: [Phase X/8: Name] so the user can track progress.
Ask clarifying questions if not provided:
Start with:
For each seed keyword, generate variations:
## Keyword Expansion Patterns
### Modifiers
- Best [keyword]
- Top [keyword]
- [keyword] for [audience]
- [keyword] near me
- [keyword] [year]
- How to [keyword]
- What is [keyword]
- [keyword] vs [alternative]
- [keyword] examples
- [keyword] tools
### Long-tail Variations
- [keyword] for beginners
- [keyword] for small business
- Free [keyword]
- [keyword] software/tool/service
- [keyword] template
- [keyword] checklist
- [keyword] guide
Categorize each keyword:
| Intent | Signals | Example | Content Type |
|---|---|---|---|
| Informational | what, how, why, guide, learn | "what is SEO" | Blog posts, guides |
| Navigational | brand names, specific sites | "google analytics login" | Homepage, product pages |
| Commercial | best, review, vs, compare | "best SEO tools [current year]" | Comparison posts, reviews |
| Transactional | buy, price, discount, order | "buy SEO software" | Product pages, pricing |
Score each keyword (1-100 scale):
### Difficulty Factors
**High Difficulty (70-100)**
- Major brands ranking
- High domain authority competitors
- Established content (1000+ backlinks)
- Paid ads dominating SERP
**Medium Difficulty (40-69)**
- Mix of authority and niche sites
- Some opportunities for quality content
- Moderate backlink requirements
**Low Difficulty (1-39)**
- Few authoritative competitors
- Thin or outdated content ranking
- Long-tail variations
- New or emerging topics
Formula: Opportunity = (Volume × Intent Value) / Difficulty
Intent Value assigns a numeric weight by search intent:
### Opportunity Matrix
| Scenario | Volume | Difficulty | Intent | Priority |
|----------|--------|------------|--------|----------|
| Quick Win | Low-Med | Low | High | ⭐⭐⭐⭐⭐ |
| Growth | High | Medium | High | ⭐⭐⭐⭐ |
| Long-term | High | High | High | ⭐⭐⭐ |
| Research | Low | Low | Low | ⭐⭐ |
Keywords likely to trigger AI responses:
### GEO-Relevant Keywords
**High GEO Potential**
- Question formats: "What is...", "How does...", "Why is..."
- Definition queries: "[term] meaning", "[term] definition"
- Comparison queries: "[A] vs [B]", "difference between..."
- List queries: "best [category]", "top [number] [items]"
- How-to queries: "how to [action]", "steps to [goal]"
**AI Answer Indicators**
- Query is factual/definitional
- Answer can be summarized concisely
- Topic is well-documented online
- Low commercial intent
Group keywords into content clusters:
## Topic Cluster: [Main Topic]
**Pillar Content**: [Primary keyword]
- Search volume: [X]
- Difficulty: [X]
- Content type: Comprehensive guide
**Cluster Content**:
### Sub-topic 1: [Secondary keyword]
- Volume: [X]
- Difficulty: [X]
- Links to: Pillar
- Content type: [Blog post/Tutorial/etc.]
### Sub-topic 2: [Secondary keyword]
- Volume: [X]
- Difficulty: [X]
- Links to: Pillar + Sub-topic 1
- Content type: [Blog post/Tutorial/etc.]
[Continue for all cluster keywords...]
Produce a report containing: Executive Summary, Top Keyword Opportunities (Quick Wins, Growth, GEO), Topic Clusters, Content Calendar, and Next Steps.
Quality bar — every recommendation must include at least one specific number. If it reads like the left column, rewrite it before including.
| ❌ Generic (rewrite before including) | ✅ Actionable |
|---|---|
| "Target long-tail keywords for better results" | "Target 'project management for nonprofits' (vol: 320, KD: 22) — no DR>40 sites in top 10" |
| "This keyword has good potential" | "Opportunity 8.4: vol 4,800, KD 28, transactional intent — gap analysis shows no content updated since 2023 in top 5" |
| "Consider creating content around this topic" | "Write '[Tool A] vs [Tool B] for small teams' — 1,200/mo searches, current #1 is a 2022 article with 12 backlinks" |
| "Optimize your page for this keyword" | "Add primary keyword to H1 (currently missing), write a 40-word direct answer in paragraph 1, add 3 internal links from your /blog/ cluster" |
Reference: See references/example-report.md for the full report template and example.
Reference: See references/example-report.md for a complete example report fo
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
keyword-research has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added keyword-research from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in keyword-research — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
keyword-research fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for keyword-research matched our evaluation — installs cleanly and behaves as described in the markdown.
keyword-research is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend keyword-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
keyword-research reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: keyword-research is focused, and the summary matches what you get after install.
Keeps context tight: keyword-research is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 58