Build topical authority clusters with pillar-spoke architecture and interlinking strategies.
Works with
Generates 8-20 subtopics from search data, intent patterns, and audience research to populate a cluster around a seed keyword
Structures clusters with a comprehensive pillar page (hub) and focused spoke pages (satellites), with mandatory bidirectional linking and lateral cross-links between siblings
Scores existing content coverage, identifies gaps (full, partial, or none), and flags pages ne
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbuild-clustersExecute the skills CLI command in your project's root directory to begin installation:
Fetches build-clusters from calm-north/seojuice-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate build-clusters. Access via /build-clusters in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
5
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
5
stars
Build a topical authority cluster from a seed keyword using pillar-spoke structure, coverage scoring, and interlinking plans.
A topic cluster is a group of interlinked pages that collectively cover a subject area. Google evaluates topical authority at the cluster level — ranking a single page is harder if the site has no supporting content around the topic.
Structure:
Gather this context (ask if not provided):
From the seed topic, generate subtopics using these methods:
Search-derived:
Intent-derived:
Audience-derived:
Aim for 8-20 subtopics per cluster.
Organize subtopics into a structured cluster:
Pillar: [Broad Topic] (head term)
│
├── Spoke: [Subtopic 1] (body term)
│ └── Intent: informational
│
├── Spoke: [Subtopic 2] (body term)
│ └── Intent: commercial investigation
│
├── Spoke: [Subtopic 3] (long-tail)
│ └── Intent: transactional
│
├── Spoke: [Subtopic 4] (long-tail)
│ └── Intent: informational
│
└── ... (8-15 more spokes)
Score how well the existing site covers the cluster:
| Subtopic | Existing Page? | Quality (1-5) | Traffic | Gap? |
|---|---|---|---|---|
| [subtopic 1] | /blog/topic-1 | 4 | 500/mo | No |
| [subtopic 2] | — | — | — | Yes |
| [subtopic 3] | /blog/old-post | 2 | 50/mo | Partial (needs refresh) |
The pillar page should:
Pillar page is NOT a mega-article that tries to cover everything in depth. It is a hub that distributes authority and directs readers to the right spoke.
Map the internal links:
| From Page | To Page | Anchor Text | Context |
|---|---|---|---|
| Pillar | Spoke 1 | "[subtopic 1] guide" | In the subtopic 1 overview section |
| Spoke 1 | Pillar | "[broad topic]" | In the introduction or conclusion |
| Spoke 1 | Spoke 2 | "[subtopic 2]" | Where subtopic 2 is mentioned contextually |
| Spoke 3 | Spoke 1 | "[subtopic 1]" | Where comparison is relevant |
Rules:
Score the cluster's readiness to compete:
Coverage Score = (Covered spokes / Total spokes) x 100
Link Health = (Spokes with bidirectional pillar link / Total spokes) x 100
Content Quality = (Spokes scoring 3+ quality / Total spokes) x 100
| Metric | Score | Threshold |
|---|---|---|
| Coverage | [x]% | > 70% to start ranking for pillar keyword |
| Link Health | [x]% | 100% is the target — every spoke must link to pillar and back |
| Content Quality | [x]% | > 80% — clusters with thin spokes dilute authority |
| Cluster State | Coverage | Link Health | Content Quality | Expected Result |
|---|---|---|---|---|
| Incomplete | <50% | <70% | Any | Pillar unlikely to rank page 1; spokes rank individually at best |
| Developing | 50-70% | 70-90% | 50-80% | Pillar may appear page 2-3; some spokes rank for long-tail |
| Competitive | 70-90% | 100% | 80-90% | Pillar competes for page 1; most spokes rank for their targets |
| Dominant | >90% | 100% | >90% | Pillar strong on page 1; cluster captures most queries in the topic |
| Link Type | Minimum Count | Direction |
|---|---|---|
| Pillar → each spoke | 1 per spoke | Downward — link from the relevant section of the pillar |
| Each spoke → pillar | 1 per spoke | Upward — "our complete [topic] guide" |
| Spoke ↔ sibling spokes | 2-4 per spoke | Lateral — where contextually natural |
| Cross-cluster bridges | 0-2 per cluster | Between hubs — only with genuine topical relevance |
Cluster ready to compete: Coverage > 70%, Link Health = 100%, Content Quality > 80%. Below these thresholds, prioritize filling gaps before expecting the pillar to rank.
Order the content production for maximum impact:
Cluster Summary
Cluster Map [Visual structure from Step 2]
Coverage Scorecard [Table from Step 3]
Pillar Page Spec
Interlinking Plan [Table from Step 5]
Production Roadmap [Ordered list from Step 6 with estimated timelines]
Pro Tip: Use the free Blog Keyword Generator to discover subtopics for your cluster. SEOJuice MCP users get automatic cluster mapping — run
/seojuice:content-strategyto see existing clusters with coverage metrics, or uselist_clustersandget_cluster_detailto check cluster health and identify gaps.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
erichowens/some_claude_skills
I recommend build-clusters for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for build-clusters matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: build-clusters is focused, and the summary matches what you get after install.
Keeps context tight: build-clusters is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: build-clusters is focused, and the summary matches what you get after install.
We added build-clusters from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added build-clusters from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
build-clusters reduced setup friction for our internal harness; good balance of opinion and flexibility.
build-clusters is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in build-clusters — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 52