keyword-research▌
aaron-he-zhu/seo-geo-claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Discovers high-value keywords with intent classification, difficulty scoring, and topic clustering for SEO content strategy.
- ›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
Keyword Research
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.
When This Must Trigger
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.
- Starting a new content strategy or campaign
- Expanding into new topics or markets
- Finding keywords for a specific product or service
- Identifying long-tail keyword opportunities
- Understanding search intent for your industry
- Planning content calendars
- Researching keywords for GEO optimization
What This Skill Does
- Keyword Discovery: Generates comprehensive keyword lists from seed terms
- Intent Classification: Categorizes keywords by user intent (informational, navigational, commercial, transactional)
- Difficulty Assessment: Evaluates competition level and ranking difficulty
- Opportunity Scoring: Prioritizes keywords by potential ROI
- Clustering: Groups related keywords into topic clusters
- GEO Relevance: Identifies keywords likely to trigger AI responses
Quick Start
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Basic Keyword Research
Research keywords for [topic/product/service]
Find keyword opportunities for a [industry] business targeting [audience]
With Specific Goals
Find low-competition keywords for [topic] with commercial intent
Identify question-based keywords for [topic] that AI systems might answer
Competitive Research
What keywords is [competitor URL] ranking for that I should target?
Skill Contract
Expected output: a prioritized research brief, evidence-backed findings, and a short handoff summary ready for memory/research/.
- Reads: user goals, target market inputs, available tool data, and prior strategy from CLAUDE.md and the shared State Model when available.
- Writes: a user-facing research deliverable plus a reusable summary that can be stored under
memory/research/. - Promotes: durable keyword priorities, competitor facts, entity candidates, and strategic decisions to
CLAUDE.md,memory/decisions.md, andmemory/research/; hand canonical entity work toentity-optimizer. - Next handoff: use the
Next Best Skillbelow when the findings are ready to drive action.
Data Sources
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:
- Seed keywords or topic description
- Target audience and geographic location
- Business goals (traffic, leads, sales)
- Current domain authority (if known) or site age
- Any known keyword performance data or search volume estimates
Proceed with the full analysis using provided data. Note in the output which metrics are from automated collection vs. user-provided data.
Instructions
When a user requests keyword research:
At the start of each phase, announce: [Phase X/8: Name] so the user can track progress.
Phase 1/8: Scope
Ask clarifying questions if not provided:
- What is your product/service/topic?
- Who is your target audience?
- What is your business goal? (traffic, leads, sales)
- What is your current domain authority? (new site, established, etc.)
- Any specific geographic targeting?
- Preferred language?
Phase 2/8: Discover
Start with:
- Core product/service terms
- Problem-focused keywords (what issues do you solve?)
- Solution-focused keywords (how do you help?)
- Audience-specific terms
- Industry terminology
Phase 3/8: Variations
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
Phase 4/8: Classify
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 |
Phase 5/8: Score
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
Opportunity Score
Formula: Opportunity = (Volume × Intent Value) / Difficulty
Intent Value assigns a numeric weight by search intent:
- Informational = 1
- Navigational = 1
- Commercial = 2
- Transactional = 3
### 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 | ⭐⭐ |
Phase 6/8: GEO-Check — AI Answer Overlap
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
Phase 7/8: Cluster
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...]
Phase 8/8: Deliver
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.
Validation Checkpoints
Input Validation
- Seed keywords or topic description clearly provided
- Target audience and business goals specified
- Geographic and language targeting confirmed
- Domain authority or site maturity level established
Output Validation
- Every recommendation cites specific data points (not generic advice)
- Search volume and difficulty scores included for each keyword
- Keywords grouped by intent and mapped to content types
- Topic clusters show clear pillar-to-cluster relationships
- Source of each data point clearly stated (~~SEO tool data, user-provided, or estimated)
Example
Reference: See references/example-report.md for a complete example report fo
How to use keyword-research on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add keyword-research
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches keyword-research from GitHub repository aaron-he-zhu/seo-geo-claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate keyword-research. Access the skill through slash commands (e.g., /keyword-research) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★58 reviews- ★★★★★Dhruvi Jain· Dec 24, 2024
keyword-research has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Liam Khanna· Dec 24, 2024
We added keyword-research from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ren Mensah· Dec 16, 2024
Useful defaults in keyword-research — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Liam Malhotra· Dec 8, 2024
keyword-research fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Lucas Gill· Dec 8, 2024
Registry listing for keyword-research matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Evelyn Lopez· Nov 27, 2024
keyword-research is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kwame Liu· Nov 27, 2024
I recommend keyword-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Lucas Rao· Nov 27, 2024
keyword-research reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Oshnikdeep· Nov 15, 2024
Solid pick for teams standardizing on skills: keyword-research is focused, and the summary matches what you get after install.
- ★★★★★Evelyn Haddad· Nov 15, 2024
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