build-clusters▌
calm-north/seojuice-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Build topical authority clusters with pillar-spoke architecture and interlinking strategies.
- ›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
Build Clusters
Build a topical authority cluster from a seed keyword using pillar-spoke structure, coverage scoring, and interlinking plans.
What is a Topic Cluster?
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:
- Pillar page — comprehensive overview of the broad topic (targets head term)
- Spoke pages — focused articles covering subtopics (target body/long-tail terms)
- Internal links — every spoke links to the pillar, pillar links to all spokes, spokes cross-link to siblings
Before You Start
Gather this context (ask if not provided):
- Seed topic. The broad subject area to build authority around.
- Existing content. Does the site already have pages on this topic? List them.
- Business relevance. How does this topic connect to the product or service?
- Content capacity. How many pieces can the team produce per month?
Step 1: Subtopic Discovery
From the seed topic, generate subtopics using these methods:
Search-derived:
- People Also Ask questions for the seed keyword
- Related searches at the bottom of SERPs
- Autocomplete suggestions (seed + a, b, c...)
- Competitor content analysis — what subtopics do top-ranking sites cover?
Intent-derived:
- Awareness: "what is [topic]", "why [topic] matters"
- Consideration: "best [topic] tools", "[topic] vs [alternative]"
- Implementation: "how to [topic]", "[topic] tutorial"
- Troubleshooting: "[topic] not working", "common [topic] mistakes"
Audience-derived:
- Beginner questions about the topic
- Advanced practitioner concerns
- Decision-maker evaluation criteria
Aim for 8-20 subtopics per cluster.
Step 2: Cluster Map
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)
Step 3: Coverage Scoring
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) |
- Full gap — no existing page, needs creation
- Partial gap — page exists but is thin, outdated, or off-intent
- Covered — strong existing page, may just need internal linking
Step 4: Pillar Page Design
The pillar page should:
- Cover the topic comprehensively at an overview level (2,000-4,000 words)
- Link to every spoke page for deeper dives
- Be structured as a table of contents for the entire cluster
- Target the highest-volume keyword in the cluster
- Include a summary of each subtopic (2-3 paragraphs) with a link to the full spoke
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.
Step 5: Interlinking Plan
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:
- Every spoke links to the pillar (mandatory)
- Pillar links to every spoke (mandatory)
- Spokes cross-link to 2-4 siblings (where contextually natural)
- Use varied anchor text (not always the exact keyword)
Step 6: Cluster Health Metrics
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 |
Expected Outcomes by Health Level
| 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 |
Internal Link Standards per Cluster
| 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.
Step 7: Production Sequence
Order the content production for maximum impact:
- Pillar page first — even as a draft, it establishes the hub
- Highest-opportunity spokes next — pages targeting gaps with the best opportunity scores
- Refresh existing spokes — update and relink any partial-gap pages
- Remaining spokes — fill out the cluster over time
- Update pillar — add links to each new spoke as it's published
Output Format
Topic Cluster: [seed topic]
Cluster Summary
- Pillar keyword: [keyword] (volume: [x], difficulty: [y])
- Total spokes: [count]
- Existing coverage: [x]% ([n] pages exist, [n] need creation)
- Total cluster volume: [sum of all keyword volumes]
Cluster Map [Visual structure from Step 2]
Coverage Scorecard [Table from Step 3]
Pillar Page Spec
- Target keyword: [keyword]
- Recommended title: [title]
- Structure: [heading outline with spoke links]
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.
How to use build-clusters on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add build-clusters
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches build-clusters from GitHub repository calm-north/seojuice-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate build-clusters. Access the skill through slash commands (e.g., /build-clusters) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ 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.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★52 reviews- ★★★★★Jin Reddy· Dec 24, 2024
I recommend build-clusters for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Naina Huang· Dec 12, 2024
Registry listing for build-clusters matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Nia Johnson· Dec 8, 2024
Solid pick for teams standardizing on skills: build-clusters is focused, and the summary matches what you get after install.
- ★★★★★Nia Tandon· Dec 8, 2024
Keeps context tight: build-clusters is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dhruvi Jain· Dec 4, 2024
Solid pick for teams standardizing on skills: build-clusters is focused, and the summary matches what you get after install.
- ★★★★★Evelyn Kapoor· Nov 27, 2024
We added build-clusters from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Oshnikdeep· Nov 23, 2024
We added build-clusters from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Amina Gill· Nov 15, 2024
build-clusters reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Arjun Huang· Nov 7, 2024
build-clusters is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Jin Sharma· Nov 3, 2024
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