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.
Find quick-win SEO content opportunities by comparing your site's existing content against competitor keyword rankings.
Install SEO Opportunity Finder
$ npx skills add gooseworks-ai/goose-skills --skill seo-opportunity-finder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gooseworks-ai/goose-skills seo-opportunity-finder --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/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo/composites/seo-opportunity-finder .claude/skills/seo-opportunity-finder && 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-opportunity-finder" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/seo-opportunity-finder into .claude/skills/seo-opportunity-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-opportunity-finder", 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/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/seo-opportunity-finderType 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 gooseworks-ai/goose-skills --skill seo-opportunity-finder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gooseworks-ai/goose-skills seo-opportunity-finder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo/composites/seo-opportunity-finder .agents/skills/seo-opportunity-finder && 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-opportunity-finder" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/seo-opportunity-finder into .agents/skills/seo-opportunity-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-opportunity-finder", 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 gooseworks-ai/goose-skills --skill seo-opportunity-finder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gooseworks-ai/goose-skills seo-opportunity-finder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo/composites/seo-opportunity-finder .cursor/skills/seo-opportunity-finder && 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-opportunity-finder" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/seo-opportunity-finder into .cursor/skills/seo-opportunity-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-opportunity-finder", 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/gooseworks-ai/goose-skills.git --path skills/seo/composites/seo-opportunity-finder--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 gooseworks-ai/goose-skills --skill seo-opportunity-finder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gooseworks-ai/goose-skills seo-opportunity-finder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo/composites/seo-opportunity-finder .gemini/skills/seo-opportunity-finder && 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-opportunity-finder" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/seo-opportunity-finder into .gemini/skills/seo-opportunity-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-opportunity-finder", 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 gooseworks-ai/goose-skills seo-opportunity-finderInstalls 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 gooseworks-ai/goose-skills --skill seo-opportunity-finder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo/composites/seo-opportunity-finder .github/skills/seo-opportunity-finder && 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-opportunity-finder" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/seo-opportunity-finder into .github/skills/seo-opportunity-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-opportunity-finder", 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 gooseworks-ai/goose-skills --skill seo-opportunity-finder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gooseworks-ai/goose-skills seo-opportunity-finder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo/composites/seo-opportunity-finder .opencode/skills/seo-opportunity-finder && 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-opportunity-finder" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/seo-opportunity-finder into .opencode/skills/seo-opportunity-finder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-opportunity-finder", 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-opportunity-finder- GitHub stars
- 1.2k
- Used in
- 1 other repo
- Token cost
- ~1.4k tokens
- SKILL.md length
- 537 words
- Files
- 2
- Skills in repo
- 273
- Repo updated
- First seen
- Licence
- MIT
At a glance
Find quick-win SEO content opportunities by comparing your site's existing content against competitor keyword rankings.
- Works in 5 steps: Intake → Catalog Your Existing Content → Analyze Competitor SEO Footprint → …
- A seed/Series A team wants to start winning organic traffic without guessing
- SKILL.md covers When to Use, Phase 0: Intake, Phase 1: Catalog Your Existing… and Phase 2: Analyze Competitor…, plus 5 more sections
- Needs APIFY_API_TOKEN
What it does
SEO Opportunity Finder is an agent skill from gooseworks-ai/goose-skills. Find quick-win SEO content opportunities by comparing your site's existing content against competitor keyword rankings. Chains site-content-catalog and seo-domain-analyzer to build a content inventory, then identifies gaps — topics competitors rank for that you don't cover yet. Outputs a prioritized list of posts to write or update. Use when a seed/Series A team wants to start winning organic traffic without guessing.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`).
It sits in Marketing & SEO, covering On-page SEO. It works with Apify. The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.
When your agent uses it
- A seed/Series A team wants to start winning organic traffic without guessing
- Tasks that involve On-page SEO
Example prompts
- “/seo-opportunity-finder”
Requirements
- A credential in APIFY_API_TOKEN
Workflow steps
5 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 c650c6d. 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 (its code samples are markdown).
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 these keys or tokens, usually read from environment variables:
APIFY_API_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
SEO Opportunity Finder loads about 1.4k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 537 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 gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 537 words, ~1,437 tokens.
Download SKILL.mdSave it as
.claude/skills/seo-opportunity-finder/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- seo-opportunity-finder
- description
- Find quick-win SEO content opportunities by comparing your site's existing content against competitor keyword rankings. Chains site-content-catalog and seo-domain-analyzer to build a content inventory, then identifies gaps — topics competitors rank for that you don't cover yet. Outputs a prioritized list of posts to write or update. Use when a seed/Series A team wants to start winning organic traffic without guessing.
- tags
- seo
SEO Opportunity Finder
Identify the highest-leverage content gaps between your site and competitors. Combines a crawl of your existing content with competitor keyword/traffic analysis to surface a prioritized list of posts worth writing.
Core principle: Don't start from a blank keyword list. Start by knowing what you have, then find what competitors have that you don't — and pick the gaps most likely to convert.
When to Use
- "Find SEO content gaps vs our competitors"
- "What topics should we write about to rank?"
- "We're starting a blog — where should we focus first?"
- "What keywords are [competitor] ranking for that we're missing?"
Phase 0: Intake
- Your website URL (e.g.,
https://yourcompany.com) - 2-3 competitor URLs to compare against
- Primary ICP — who are you trying to attract? (This filters for commercial intent vs. general traffic)
- Any topics/keyword themes that are definitely in scope? (Optional — helps prioritize output)
Phase 1: Catalog Your Existing Content
Build an inventory of the target site's current pages and posts:
- Fetch sitemap.xml (check
/sitemap.xml,/sitemap_index.xml,robots.txtforSitemap:directives) - Fall back to RSS feeds (
/feed,/blog/feed) or blog index crawl if no sitemap - Extract: all blog post titles and URLs, inferred topics/themes per post, estimated content age
This prevents recommending content you've already written.
Phase 2: Analyze Competitor SEO Footprint
For each competitor domain, pull SEO metrics:
- Domain overview — authority score, organic traffic estimate, top ranking keywords (via Apify Semrush scraper if
APIFY_API_TOKENis set) - Top pages — highest-traffic pages and their primary keywords
- Keyword categories — which topic clusters they're winning in
If Apify data is limited, supplement with web search probes:
site:[competitor]for indexed page count- Search target keywords and note which competitors rank where
- SimilarWeb free tier for traffic estimates
Phase 3: Identify Gaps
Compare your content inventory (Phase 1) against competitor keyword/topic coverage (Phase 2):
Show full SKILL.md (231 more words)Show less
Gap Classification
| Type | Definition | Priority |
|---|---|---|
| Hard gap | Competitor has a page/post on topic, you have nothing | High |
| Soft gap | You have content on topic but it's thin (< 500 words, old, no depth) | Medium |
| Positioning gap | Competitor owns a keyword cluster that maps to your ICP's exact problem | High |
| Informational gap | High traffic, low commercial intent — good for awareness, not conversion | Low |
Commercial Intent Filter
For each gap topic, score commercial intent (1-5):
- 5 — Directly maps to your product (e.g., "best AI SDR tools for startups")
- 4 — Problem-aware but not product-specific (e.g., "how to scale outbound SDR")
- 3 — Adjacent pain point (e.g., "cold email open rates benchmark 2026")
- 2 — Educational, tangential (e.g., "what is lead scoring")
- 1 — Generic traffic, low conversion potential
Prioritize gaps with score ≥ 3.
Phase 4: Synthesize & Output
Produce a prioritized opportunity table + editorial brief starters:
# SEO Opportunity Report — [Your Company] vs [Competitors]
Generated: [DATE]
## Your Content Snapshot
- Total indexed pages: [N]
- Blog posts: [N]
- Main topic clusters: [list]
## Competitor Benchmarks
| Domain | DR | Est. Monthly Organic Traffic | Top Keyword Clusters |
|--------|----|-----------------------------|----------------------|
| [comp1] | [X] | [X] | [topics] |
| [comp2] | [X] | [X] | [topics] |
## Top 10 Content Opportunities
### 1. [Topic/Title Suggestion]
- **Keyword target:** [keyword phrase]
- **Why it matters:** [what problem it solves for ICP]
- **Competitor owning it:** [competitor URL]
- **Est. monthly searches:** [range]
- **Commercial intent score:** [1-5]
- **Recommended format:** [listicle / how-to / comparison / landing page]
- **Estimated effort:** [hours or word count target]
### 2. [Topic/Title Suggestion]
...
## Quick Wins (update existing posts)
| Your Post | Issue | What to Add |
|-----------|-------|-------------|
| [URL] | [thin/outdated] | [recommendation] |
## Recommended Content Calendar (Next 90 Days)
| Month | Post | Intent Score | Est. Traffic Potential |
|-------|------|-------------|----------------------|
| Month 1 | [post 1] | [score] | [range] |
| Month 1 | [post 2] | [score] | [range] |
| Month 2 | [post 3] | [score] | [range] |
...Save to the current working directory or wherever the user prefers.
Cost
| Component | Cost |
|---|---|
| Site content catalog | Free (sitemap crawl) |
| SEO domain analyzer (per competitor) | ~$1-3 (Apify Semrush scraper) |
| Traffic analyzer (supplement) | ~$0.10-0.50 (web search probes) |
| Total per run | ~$3-10 for 3 competitors |
Tools Required
- Apify API token —
APIFY_API_TOKENenv var (for Semrush/Ahrefs data; free web search probes work without it) - Web search and web fetch capabilities
Trigger Phrases
- "Find our SEO content gaps"
- "What should we write about to rank?"
- "Compare our content coverage to [competitor]"
- "Run SEO opportunity finder for [client]"
© gooseworks-ai, 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 1 other file in skills/seo/composites/seo-opportunity-finder of gooseworks-ai/goose-skills.
- SKILL.md
- skill.meta.json
Open the folder on GitHubat commit c650c6d
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 9, 2026.
Compare with similar skills
SEO Opportunity Finder 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 Opportunity Finder this skillgooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 19k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| SEO Content Brief GeneratorAgriciDaniel/claude-seo | 19k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Nemoclaw Maintainer Normalize Title TagsNVIDIA/NemoClaw | 23k | — | ~693 | Automated safety check: Pass | Apache-2.0 | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 455 | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| AI Citability Scorerzubair-trabzada/geo-seo-claude | 11k | 2 repos | ~3.7k | Automated safety check: Notes | MIT |
Similar skills
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.
- Official
Nemoclaw Maintainer Normalize Title Tags
NVIDIA/NemoClaw
Remove bracketed NemoClaw tags from GitHub issue and PR titles.
SEO Optimizer
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
AI Citability Scorer
zubair-trabzada/geo-seo-claude
Scores how likely AI assistants are to quote passages from a web page and suggests rewrites that make those passages easier to extract.
SEO Drift Monitor
AgriciDaniel/claude-seo
Captures baselines of a page's SEO-critical elements, compares later snapshots against them and flags regressions by severity, like version control for on-page SEO.
More from gooseworks-ai/goose-skills
All 273 skills in this repoReddit Post Finder
gooseworks-ai/goose-skills
Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.
Create Image Fal
gooseworks-ai/goose-skills
Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.
Render Hook Replacement
gooseworks-ai/goose-skills
Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.
Blog Feed Monitor
gooseworks-ai/goose-skills
Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.
Competitor Post Engagers
gooseworks-ai/goose-skills
Find leads by scraping engagers from a competitor's top LinkedIn posts.
Render Chatgpt Chat
gooseworks-ai/goose-skills
Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…
Related
Works with
Categories
Questions about SEO Opportunity Finder
What does SEO Opportunity Finder do?
Find quick-win SEO content opportunities by comparing your site's existing content against competitor keyword rankings. SEO Opportunity Finder is an agent skill from gooseworks-ai/goose-skills. Find quick-win SEO content opportunities by comparing your site's existing content against competitor keyword rankings.
When should I use SEO Opportunity Finder?
SEO Opportunity Finder fits situations like: A seed/Series A team wants to start winning organic traffic without guessing; tasks that involve On-page SEO.
How do I install SEO Opportunity Finder in Claude Code?
Run `npx skills add gooseworks-ai/goose-skills --skill seo-opportunity-finder -a claude-code`. Or copy the skill folder (skills/seo/composites/seo-opportunity-finder in gooseworks-ai/goose-skills) into .claude/skills/seo-opportunity-finder in your project. Claude Code loads it when a task matches its description.
How do I install SEO Opportunity Finder in Codex?
Run `npx skills add gooseworks-ai/goose-skills --skill seo-opportunity-finder -a codex`. Or copy the skill folder (skills/seo/composites/seo-opportunity-finder in gooseworks-ai/goose-skills) into .agents/skills/seo-opportunity-finder in your project. Codex loads it when a task matches its description.
Can I use SEO Opportunity Finder 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 gooseworks-ai/goose-skills --skill seo-opportunity-finder -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-opportunity-finder, .gemini/skills/seo-opportunity-finder, .github/skills/seo-opportunity-finder and .opencode/skills/seo-opportunity-finder in your project.
What does SEO Opportunity Finder need to run?
Going by SKILL.md and its folder, SEO Opportunity Finder needs credentials named APIFY_API_TOKEN. Our summary lists: A credential in APIFY_API_TOKEN.
Does SEO Opportunity Finder 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 Opportunity Finder 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 Opportunity Finder use?
SEO Opportunity Finder 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 Opportunity Finder use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to SEO Opportunity Finder?
Skills that share tags, products or a category with SEO Opportunity Finder: SEO Keyword Clustering (AgriciDaniel/claude-seo, 19k stars), SEO Content Brief Generator (AgriciDaniel/claude-seo, 19k stars), Nemoclaw Maintainer Normalize Title Tags (NVIDIA/NemoClaw, 23k stars) and SEO Optimizer (ailabs-393/ai-labs-claude-skills, 455 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains SEO Opportunity Finder?
gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,240 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.
Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.