find-keywords

calm-north/seojuice-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/calm-north/seojuice-skills --skill find-keywords
0 commentsdiscussion
summary

Prioritized keyword research with intent mapping, difficulty scoring, and cluster seeding for SEO strategy.

  • Builds a three-tier keyword universe (head, body, long-tail) with monthly volume, difficulty scores (0-100), and intent classification across informational, commercial, transactional, and navigational categories
  • Includes cannibalization screening to prevent targeting keywords your site already ranks for, plus low-hanging fruit detection for quick wins in positions 11-20
  • Scores
skill.md

Find Keywords

Build a prioritized keyword universe from a seed topic using intent mapping, difficulty-adjusted opportunity scoring, and cluster seeding.

Before You Start

Gather this context (ask if not provided):

  1. Domain and goal. What site is this for? What is the primary conversion (leads, sign-ups, sales, traffic)?
  2. Seed topic. The core subject area — not a single keyword but the business category (e.g., "project management software", "personal injury law Chicago").
  3. Existing rankings. Does the site already rank for terms in this area? Existing rankings tell you where to defend vs. expand.
  4. Constraints. Budget, team size, content velocity — these determine whether to chase head terms or focus on long-tail.

Step 0: Cannibalization Screen

Before building a new keyword list, check what the site already targets. Creating a new page for a keyword you already rank for can split authority and hurt both pages.

For each keyword you're considering:

  1. Search site:yourdomain.com [keyword] — does an existing page already target this term?
  2. Check Google Search Console — is an existing page already getting impressions for this keyword?
  3. If yes: update the existing page instead of creating a new one.
  4. If multiple pages rank for the same keyword: you have a cannibalization problem. Consolidate before expanding.

Low-Hanging Fruit Check

Before chasing new keywords, look for existing wins:

  • Positions 11-20 — You're almost on page 1. These keywords need content improvements or better internal linking, not new pages.
  • High impressions, low clicks — Title/meta description optimization can unlock traffic without new content.
  • Declining positions — Keywords where you're losing ground may need content refreshes (see recover-content).

Address these before building net-new keyword lists.

Keyword Universe Construction

Build the universe in three tiers:

Tier 1 — Head Terms (high volume, high difficulty)

  • Typically 1-2 words
  • Define the category
  • Target with pillar pages or the homepage
  • Realistic timeline: 6-18 months for new sites

Tier 2 — Body Terms (medium volume, medium difficulty)

  • Typically 2-3 words, specific enough to indicate intent
  • Target with dedicated landing pages or cluster articles
  • 3-6 month window for established sites

Tier 3 — Long-tail Terms (lower volume, low difficulty)

  • 3+ words, specific intent
  • Fastest to rank, highest conversion rate
  • Target with blog posts, FAQ sections, supporting content
  • 4-12 week window for fresh content

For each tier, produce:

Keyword Monthly Volume Difficulty (0-100) Intent Tier Priority
... ... ... informational / transactional / navigational / commercial 1/2/3 high / medium / low

Intent Classification

Classify every keyword by search intent and sub-category:

Informational (user wants to learn)

Sub-category Signal Words Example Content Type
Educational what, why, definition, explain "what is SEO" Guide, explainer
Instructional how to, steps, tutorial, guide "how to set up GA4" Step-by-step tutorial
Exploratory types of, techniques, strategies "link building techniques" Comprehensive roundup
Troubleshooting not working, fix, error, why is "why is my site not ranking" Diagnostic guide

Commercial Investigation (user is evaluating)

Sub-category Signal Words Example Content Type
Comparison vs, compared to, or "Ahrefs vs SEMrush" Side-by-side comparison
Review-seeking review, worth it, honest "Ahrefs review" In-depth review
Best-of best, top, tools for "best SEO tools" Curated list
Evaluation for [audience], features, pricing "SEO tools for small business" Buyer's guide

Transactional (user is ready to act)

Sub-category Signal Words Example Content Type
Purchase buy, price, discount, deal "buy Ahrefs subscription" Product/pricing page
Signup/Trial free trial, sign up, demo "Ahrefs free trial" Landing page
Download download, template, PDF, checklist "SEO checklist PDF" Gated resource
Hire/Engage hire, agency, near me, book "SEO agency near me" Service page

Navigational (looking for a specific brand)

Sub-category Signal Words Example Content Type
Brand search [brand name] "HubSpot" Homepage/brand page
Feature search [brand] + [feature] "Ahrefs keyword explorer" Feature page
Support/docs [brand] + login, docs, help "Ahrefs API docs" Support content

SERP Feature Correlation by Intent

Use this to anticipate which SERP features you can target per keyword:

SERP Feature Informational Commercial Transactional Navigational
Featured Snippet Very High High Low Low
People Also Ask Very High Very High Low Medium
AI Overview Very High High Low-Medium Low
Shopping Results Very Low Medium Very High Low
Local Pack Low Low High Low
Sitelinks Low Low Medium Very High

Conversion Potential by Intent

Intent Avg Conversion Rate Nurture Length
Informational 0.5-2% Long (weeks to months)
Commercial Investigation 2-5% Medium (days to weeks)
Transactional 5-15% Short (immediate to days)
Navigational N/A — brand-dependent N/A

Common Classification Mistakes

Mistake Correct Classification
Treating "best CRM software" as informational Commercial Investigation
Treating "how much does X cost" as informational Commercial / Transactional
Ignoring local intent in "SEO services" Transactional (local)
Assuming single intent for "SEO tools" Mixed — check the SERP to confirm

Two keywords with different intents should never target the same page.

Opportunity Scoring

Score each keyword:

Opportunity Score = (Volume x (1 - Difficulty/100)) x Intent Multiplier

Intent multipliers:

  • Transactional: 1.5
  • Commercial investigation: 1.3
  • Informational: 1.0
  • Navigational: 0.2

This surfaces low-competition, high-intent targets over vanity volume plays.

Cluster Seeding

Group the keyword universe into topic clusters:

Cluster Name Pillar Keyword Supporting Keywords (3-5) Total Volume
... ... ... ...

Each cluster needs one pillar page (head term) and 3-8 supporting pages (body + long-tail).

Output Format

Keyword Research: [topic or domain]

Summary

  • Total keywords: [count]
  • Total addressable volume: [sum]
  • Difficulty range: [min]-[max]
  • Clusters identified: [count]

Priority Matrix [Tiered keyword table]

Cluster Seeds [Cluster table]

Start Here — Top 5 Keywords

For each of the 5 highest-opportunity keywords:

  • Why this keyword now (difficulty, intent, business value)
  • What page type to create
  • Which cluster it anchors or supports

Pro Tip: Use the free Blog Keyword Generator and Autocomplete Research tools at seojuice.com for seed keyword discovery. SEOJuice MCP users can run /seojuice:keyword-analysis for live ranking data and /seojuice:content-strategy to see content gaps — keywords your competitors rank for that you don't.

how to use find-keywords

How to use find-keywords on Cursor

AI-first code editor with Composer

1

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 find-keywords
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/calm-north/seojuice-skills --skill find-keywords

The skills CLI fetches find-keywords from GitHub repository calm-north/seojuice-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/find-keywords

Reload or restart Cursor to activate find-keywords. Access the skill through slash commands (e.g., /find-keywords) 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

GET_STARTED →

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.754 reviews
  • Emma Harris· Dec 28, 2024

    find-keywords is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Dhruvi Jain· Dec 24, 2024

    find-keywords fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Tariq Gonzalez· Dec 20, 2024

    Useful defaults in find-keywords — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Hassan Menon· Nov 23, 2024

    find-keywords reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Emma Khan· Nov 19, 2024

    find-keywords fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Oshnikdeep· Nov 15, 2024

    find-keywords is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ren Desai· Nov 11, 2024

    find-keywords has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Hassan Bansal· Oct 14, 2024

    Registry listing for find-keywords matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Hassan Agarwal· Oct 10, 2024

    We added find-keywords from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ganesh Mohane· Oct 6, 2024

    Keeps context tight: find-keywords is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 54

1 / 6