keyword-clustering
Skill233 starsChanged 3 months agoMITView on GitHub
Cluster keywords by intent and map them to existing or proposed pages.
14 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- kostja94/marketing-skillstheir own version, first seen Nov 8, 2026
- foverse/seoverseedited, first seen Nov 8, 2026
- akii-technologies-ltd/akii-seo-ai-search-optimizertheir own version, first seen Nov 1, 2026
- mtarcure/claude-vibe-squadtheir own version, first seen Oct 28, 2026
- winsley-jeune/harborrank-skillsedited, first seen Oct 27, 2026
- jwuthri-cloud/Tracely-aiword for word, first seen Oct 20, 2026
Used with
Projects with it also use openseo-release-notes, openseo-review-web-content and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JwuthriSkillopenseo-release-notes
Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.
Also in 6 projects that use this
JwuthriSkillopenseo-review-web-content
Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.
Also in 5 projects that use this
huiferSkilllocal-seo
本地 SEO 分析和优化专家。自动检测项目是否需要本地 SEO,分析 NAP(Name, Address, Phone)一致性、本地关键词优化、Google Business Profile (GBP) 优化和本地结构化数据生成。提供本地商家搜索引擎排名优化建议,包括 NAP 标准化、本地关键词策略、GBP 完整性检查、评论策略、地图嵌入和本地 SEO 审计。
Also in 6 projects that use this
ten9876Skillpapercuts
Read-only AetherSDR issue triage that surfaces the UX papercuts, bugs, and regressions you can fix AND prove today with the agent automation bridge. Use when the user says $papercuts or /papercuts, or asks to "find papercuts", "what can I fix and prove today", "triage bridge-provable issues", "what UX bugs can the bridge close", "sort issues by priority I can knock out", or otherwise wants a curated, lifecycle-aware (design→code→prove) shortlist of issues — NOT the label-and-respond /triage workflow. This is the discovery step that feeds /fb. Strictly read-only: it never labels, comments, closes, or edits issues.
Also in 4 projects that use this
01claudingSkillseo-report
SEO reporting and analytics dashboard generation. Creates weekly digests, monthly performance reports, quarterly strategy reviews, and real-time dashboard templates. Use when user says "SEO report", "weekly digest", "monthly report", "dashboard", "SEO metrics", "performance summary".
Also in 3 projects that use this
- +2 more from Jwuthri
Other versions14 projects use a version of this.
Word for word · 4
- Jwuthri/Tracely-ai★ 1.3k100% same
- VladSez/easy-invoice-pdf★ 1.1k100% same
- jwuthri-cloud/Tracely-ai★ 979100% same
- IsaacBell/ai-marketing-toolkit★ 0100% same
Edited · 6
- every-app/open-seo★ 27k53% same
- foverse/seoverse★ 453% same
- kid7st/agenticseo★ 223% same
- ventra-rocket/EchoSEO★ 298% same
- winsley-jeune/harborrank-skills★ 227% same
- ictlondon/kraftskills★ 072% same
Wrote their own version · 4
- kostja94/marketing-skills★ 1.1ksame name
- mtarcure/claude-vibe-squad★ 220same name
- akii-technologies-ltd/akii-seo-ai-search-optimizer★ 79same name
- searchfit/searchfit-seo★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- competitive-landscapeSkill
- competitor-analysisSkill
- keyword-researchSkill
- link-prospectingSkill
- no-em-dashesSkill
- seo-coachSkill
- seo-project-setupSkill
- write-changelogSkill
The file
We split this skill into the rules it gives an agent
12 rules. 4 are common, 3 are distinctive, and 5 are very specific to this project.
4
Common
Most of the 9 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
If keywords are not provided, use list_saved_keywords for saved sets, research_keywords for seed discovery, or get_ranked_keywords when the …
- Very specific: line 33
Use get_search_console_performance (dimensions ["query","page"]) when Search Console is connected to start from real queries and the pages …
- Very specific: line 34
Use get_ranked_keywords for domain/page-driven clustering.
- Very specific: line 35
Use search_local_businesses and get_local_serp_results when proximity, local packs, or Google Business results determine whether terms …
- Common: line 36
Remove duplicates, irrelevant terms, and terms that clearly require a different product or audience.
- Distinctive: line 45
Do-not-target / later bucket, if weak or off-strategy
- Very specific: line 47
Ask before applying cluster tags with save_keywords.
- Distinctive: line 51
Start with a short mapping summary:
- Common: line 73
Do not over-cluster tiny keyword sets.
- Common: line 74
Do not rely on lexical similarity alone.
- Distinctive: line 75
Do not replace tags broadly without explicit confirmation.
- Common: line 76
If existing URL data is missing, label target pages as proposed.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OpenSEO Keyword Clustering
Goal
Group keywords into page-level clusters and decide which existing or new page should target each cluster. This is a keyword mapping workflow, not just a semantic grouping exercise.
Required inputs
projectId- A keyword list, saved keyword tag, seed topic, or target domain
- Optional existing URLs/pages to map against
If keywords are not provided, use list_saved_keywords for saved sets, research_keywords for seed discovery, or get_ranked_keywords when the user starts from a target domain.
OpenSEO MCP tools
list_saved_keywords: fetch an existing keyword set, optionally filtered by tags.research_keywords: expand a seed when the user starts from a topic.get_ranked_keywords: gather exact ranking keywords and URLs when the user starts from a domain or page.get_search_console_performance: when Search Console is connected, pull real queries withdimensions: ["query","page"]to map terms to the pages already earning impressions and to surface cannibalization (one query splitting clicks across multiple URLs).get_serp_results: validate whether keywords belong on the same page by checking SERP overlap and intent.get_local_serp_results: use for local SEO clusters when Maps/local-pack intent should affect page mapping.save_keywords: optionally tag final clusters after user confirmation.
Workflow
- Gather the candidate keyword set.
- Use
get_search_console_performance(dimensions["query","page"]) when Search Console is connected to start from real queries and the pages already ranking for them. - Use
get_ranked_keywordsfor domain/page-driven clustering. - Use
search_local_businessesandget_local_serp_resultswhen proximity, local packs, or Google Business results determine whether terms belong on location pages.
- Use
- Remove duplicates, irrelevant terms, and terms that clearly require a different product or audience.
- Build clusters around intent and page type:
- Same SERP intent and similar ranking pages belong together.
- Different intent, buyer stage, or SERP format should be split.
- Similar words do not guarantee the same cluster.
- For important borderline terms, use a small
get_serp_resultsbatch to check overlap. - Assign each cluster to:
- Existing URL, if supplied and appropriate
- New page recommendation, if no existing page fits
- Do-not-target / later bucket, if weak or off-strategy
- Identify cannibalization risk when multiple pages would target the same intent. When Search Console is connected, confirm it from real data with
get_search_console_performance(dimensions: ["query","page"]) — the same query sending impressions to multiple URLs. - Ask before applying cluster tags with
save_keywords.
Output format
Start with a short mapping summary:
- Number of clusters
- Pages to create
- Existing pages to update
- Cannibalization or consolidation issues
Then include:
| Cluster | Primary keyword | Secondary keywords | Intent | Target page | Priority | Notes |
For each cluster, include a recommended page brief:
- Page type
- Searcher problem
- Required sections
- Internal-link opportunities
- Save/tag suggestion
Guardrails
- Do not over-cluster tiny keyword sets. If there are fewer than 10 usable terms, produce a simple map.
- Do not rely on lexical similarity alone. SERP intent wins.
- Do not replace tags broadly without explicit confirmation.
- If existing URL data is missing, label target pages as proposed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

