agentleFS
kostja94kostja94/marketing-skills/skills/keyword-clustering/SKILL.md

keyword-clustering

Skill1.1k starsChanged 26 days agoMITView on GitHub

Groups candidate keywords by user task and tests whether one page can satisfy them. Use for same-page decisions, mixed intent and adjacent queries.

16 other projects use a version of this.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the kostja94/marketing-skills repository that our weekly crawl found: only 4 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Used with

Projects with it also use seo-project-setup, openseo-release-notes and 8 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 11 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 11 projects that use this

  • ten9876Skill

    papercuts

    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

  • 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 3 projects that use this

  • +5 more from Jwuthri

The file

Files
SKILL.md

Keyword Clustering

For each candidate, identify the user's starting state, operation, desired result and next action. Group tentative variants only when one focused page can fully serve them. Check product capability and expected page type. Compare actual ranking URLs and page types in the target locale when available. Record market and date. If search evidence and task analysis disagree, explain the disagreement and leave the decision pending.

Keep the base expression family visible across the handoff. Assign variants to a page cluster or mark their intent pending. A process noun can attract both tool users and readers researching the method; compare page types before deciding. Deduplicate exact repeats while preserving meaningful wording differences.

Classify relationships as same-page variants, parent/child, adjacent tasks, conditional modifiers, mixed intent or exclusions. Free, bulk and API can change the required experience. Shared vocabulary or overlapping results alone cannot establish compatibility. For example, removing white to obtain transparency and adding white for a product listing have opposite output requirements.

Return a representative term, same-page variants, concrete task, expected asset, adjacent clusters, evidence and unresolved check. Preserve hypotheses when evidence is thin. Hand clusters to keyword-opportunity or keyword-mapping; content-strategy owns broader topic organization.

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.