agentleFS
UXMagicaiUXMagicai/seosorted-skills/skills/topic-clusters/SKILL.md

topic-clusters

Skill0 starsChanged 39 days agoMITView on GitHub

Plan topic clusters (pillar page plus supporting articles) for topical authority using SEOsorted keyword data. Use when the user asks for a content strategy, content plan, topic clusters, pillar pages, topical authority, a content roadmap, or how to organize many keywords into a site structure with internal links.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Start from a keyword shortlist (run keyword-research first if there is none) or research_keywords operation: "list" for saved keywords.

    line 10
  2. Very specific:

    Run cannibalization-check across the whole plan.

    line 13
  3. Very specific:

    Check manage_articles operation: "list" so existing pages slot into clusters instead of being rewritten.

    line 14
  4. Very specific:

    Write the pillar first with write-article (content type PILLAR_GUIDE), then the supporting articles with bulk-content-run.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Topic clusters

Steps

  1. Start from a keyword shortlist (run keyword-research first if there is none) or research_keywords operation: "list" for saved keywords.
  2. Group by search intent and entity, not by shared words. A cluster is one topic a reader would explore in one sitting (e.g. "tirzepatide dosing": dosage chart, units conversion, titration schedule, missed dose).
  3. Pick each cluster's pillar: the broadest keyword with the highest volume that a comprehensive guide can satisfy. Supporting articles take the narrower intents.
  4. Run cannibalization-check across the whole plan. Pairs sharing 7+ of Google's top 10 URLs belong in one page — merge them. Pairs sharing 4–6 need clearly different angles.
  5. Check manage_articles operation: "list" so existing pages slot into clusters instead of being rewritten.

Output

For each cluster:

RoleKeywordVolumeKDStatus (new / exists)Links to

Pillar links to every supporting article; every supporting article links back to the pillar and to 1–2 siblings.

Order clusters by total opportunity (sum of volume of quick-win and high keywords) and by fit with what the business sells.

Next

Write the pillar first with write-article (content type PILLAR_GUIDE), then the supporting articles with bulk-content-run.

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.