agentleFS
mtarcuremtarcure/claude-vibe-squad/.agents/skills/keyword-clustering/SKILL.md

keyword-clustering

Skill220 starsChanged 20 days agoMITView on GitHub

Use when supplied or grounded search queries must be grouped into reproducible intent/topic clusters and mapped one-cluster-per-page; emit the evidence table with source/date/locale/device and explicit split/merge rules. Not for measuring ranking impact without analytics.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-project-setup, openseo-release-notes and 10 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.
  • JwuthriSkill

    seo-project-setup

    Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.

    Also in 13 projects that use this

  • JwuthriSkill

    openseo-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

  • MicrosoftSkill

    competitive-landscape

    Use when a branch manager asks something like \"Who are we up against in each metro\"

    Also in 13 projects that use this

  • every-appSkill

    ai-prompt-research

    Find the questions people ask about a market, how ChatGPT answers them, and which sites get cited in the answers. Use when the user asks what people ask AI about their niche, wants prompt ideas, or wants to know where their brand is missing before choosing prompts to track. Research only; it never saves tracking or starts answer collection.

    Also in 3 projects that use this

  • 01claudingSkill

    seo-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 4 projects that use this

  • huiferSkill

    local-seo

    本地 SEO 分析和优化专家。自动检测项目是否需要本地 SEO,分析 NAP(Name, Address, Phone)一致性、本地关键词优化、Google Business Profile (GBP) 优化和本地结构化数据生成。提供本地商家搜索引擎排名优化建议,包括 NAP 标准化、本地关键词策略、GBP 完整性检查、评论策略、地图嵌入和本地 SEO 审计。

    Also in 8 projects that use this

  • +5 more from Jwuthri

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Every query has complete source/date/locale/device provenance and an intent confidence.

    line 28

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

Keyword Clustering

Group supplied or grounded search queries by intent and topic, and map each reproducible cluster to a page.

Required evidence table

Produce one row per normalized query with these fields: source, collection date, locale, device, raw query, normalized query, intent label, intent confidence, similarity/split-merge rule applied, cluster ID, target page, and exception rationale. Pin the similarity method and split/merge threshold before clustering; if judgment overrides that rule, the row's exception rationale makes the override reviewable.

Steps

  1. Record the query source, collection date, locale, and device; never invent query or volume evidence.
  2. Normalize each raw query with a stated rule while preserving the raw value in the table.
  3. Tag intent as informational / navigational / transactional / commercial, with a confidence value and an explicit multi-intent exception where one label would misrepresent the query.
  4. Apply the pinned similarity and split/merge rule so one cluster expresses one reviewable user need.
  5. Map each cluster to one target page/content piece and record why any mapping exception is necessary.
  6. Flag cannibalization wherever existing or proposed pages compete for the same cluster.

Acceptance

  • Every query has complete source/date/locale/device provenance and an intent confidence.
  • The normalization, similarity, and split/merge rules are fixed and replayable; exceptions carry reasons.
  • Each cluster maps to exactly one page (no two pages target the same cluster).
  • Queries/volumes are grounded, not fabricated, and the required evidence table accompanies the map.

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.