agentleFS
foversefoverse/seoverse/.agents/skills/keyword-clustering/SKILL.md

keyword-clustering

Skill4 starsChanged 13 days agoMITView on GitHub

Cluster keywords by intent and map them to existing or proposed pages.

16 other projects use a version of this, 11 of them edited; 9 of 9 edited versions we compared changed its rules; 1 new project in the last 4 weeks, against 1 the 4 before.

How people change it

9 of 9 edited versions changed its rules, and some changes recur.

Of the 9 edited versions we compared: 9 made changes of their own.

Rules people drop

  1. Before spending credits, check the research log. If the same research ran within the last 30 days, reuse that result and say so instead of re-buying it.dropped by 8 of 9
  2. If a report template applies (see seo-report), its sections and tone replace this list.dropped by 8 of 9
  3. Call get_project_context first and ground the mapping in it — the saved key pages are the existing pages clusters should map to, and the business and goal decide which clusters are worth targeting.dropped by 7 of 9
  4. Do-not-target / later bucket, if weak or off-strategydropped by 1 of 9
  5. Do not replace tags broadly without explicit confirmation.dropped by 1 of 9

Rules people add

  1. Start with a short mapping summary:added by 8 of 9

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Steady: 1 new project took it in the last 4 weeks, 1× the 4 weeks before.thin data

Week of Sep 20: 1 new projectWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 1 new projectWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 2 in all, so this is a hint, not a trend.

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 6 are common, 1 is distinctive, and 7 are very specific to this project.

  • 6

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If keywords are not provided, use list_saved_keywords for saved sets, research_keywords for seed discovery, or get_ranked_keywords when the …

    line 18
  2. Very specific:

    Call get_project_context first and ground the mapping in it — the saved key pages are the existing pages clusters should map to, and the …

    line 24
  3. Distinctive:

    Before spending credits, check the research log.

    line 26
  4. Very specific:

    Use get_search_console_performance (dimensions ["query","page"]) when Search Console is connected to start from real queries and the pages …

    line 46
  5. Very specific:

    Use get_ranked_keywords for domain/page-driven clustering.

    line 47
  6. Very specific:

    Use search_local_businesses and get_local_serp_results when proximity, local packs, or Google Business results determine whether terms …

    line 48
  7. Common:

    Remove duplicates, irrelevant terms, and terms that clearly require a different product or audience.

    line 49
  8. Common:

    Do-not-target / later bucket, if weak or off-strategy

    line 58
  9. Very specific:

    Ask before applying cluster tags with save_keywords.

    line 60
  10. Very specific:

    If a report template applies (see seo-report), its sections and tone replace this list.

    line 66
  11. Common:

    Do not over-cluster tiny keyword sets.

    line 79
  12. Common:

    Do not rely on lexical similarity alone.

    line 80
  13. Common:

    Do not replace tags broadly without explicit confirmation.

    line 81
  14. Common:

    If existing URL data is missing, label target pages as proposed.

    line 82

“Common” is measured: kept by at least 6 in 10 of the 14 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Project context

The project-context tools are free and shared with the app and other agents.

  1. Call get_project_context first and ground the mapping in it — the saved key pages are the existing pages clusters should map to, and the business and goal decide which clusters are worth targeting.
  2. This skill needs key pages. If none are saved, run a minimal inline setup: ask the user for the pages that matter, or propose a shortlist from the site, an audit, or Search Console and confirm it, write it back with update_project_context (addKeyPages), then continue the clustering. Never front-load the full interview; suggest seo-project-setup at the end for the rest.
  3. Before spending credits, check the research log. If the same research ran within the last 30 days, reuse that result and say so instead of re-buying it.
  4. On finish, write back what is durable with update_project_context — new or corrected addKeyPages entries with the topic each page now targets — and append a research log entry: { appendResearchLog: { summary: "Keyword clustering: <keyword set>. Verdict: <conclusion>" } }.

Deliver as a report

Deliver through the seo-report skill, saving with skill: "keyword-clustering". If that skill is not available, say so and stop before writing HTML.

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 with dimensions: ["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

  1. 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_keywords for domain/page-driven clustering.
    • Use search_local_businesses and get_local_serp_results when proximity, local packs, or Google Business results determine whether terms belong on location pages.
  2. Remove duplicates, irrelevant terms, and terms that clearly require a different product or audience.
  3. 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.
  4. For important borderline terms, use a small get_serp_results batch to check overlap.
  5. 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
  6. 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.
  7. Ask before applying cluster tags with save_keywords.

Output format

h1: the site or keyword set.

If a report template applies (see seo-report), its sections and tone replace this list.

Sections in this order:

  1. The map — one or two opening sentences: how many clusters, how many pages to create, how many to update, and any cannibalization found.
  2. Clusters — a table of cluster, primary keyword, intent, target page, and priority. Keep secondary keywords in the per-cluster briefs, not in this table.
  3. Page briefs — one finding per cluster: the page type and the searcher's problem, then the page to create or update. List required sections and internal links underneath.
  4. Cannibalization — a table of the query, the competing URLs, and which one to keep, only when there is real evidence for it.
  5. What to do next — an ordered list, including the tag suggestions and the explicit ask before applying them.
  6. How this report was made — opens with the skill link line from seo-report, pointing at https://openseo.so/docs/skills/keyword-clustering ("OpenSEO Keyword Clustering skill"), then where the keywords came from, and a note labelling target pages as proposed when no URL data was supplied.

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.