Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计提醒

build-clusters建立集群

Agent Skill

build-clusters 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

38,677

周安装

1,585

GitHub Stars

7

下载量

12,482
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:build-clusters(建立集群)
来源仓库:https://github.com/calm-north/seojuice-skills
仓库路径:skills/build-clusters
安装命令:
npx skills add https://github.com/calm-north/seojuice-skills --skill build-clusters
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/calm-north/seojuice-skills --skill build-clusters

简介

通过支柱架构和互联策略构建主题权威集群。

  • 根据搜索数据、意图模式和受众研究生成 8-20 个子主题,以围绕种子关键字填充集群
  • 具有综合支柱页面(中心)和重点分支页面(卫星)的结构集群,具有强制双向链接和同级页面之间的横向交叉链接
  • 对现有内容覆盖率进行评分,识别差距(全部、部分或无),并标记需要创建或刷新的页面
  • 提供生产排序、具有锚文本指导的互连表以及集群健康指标(覆盖范围、链接健康状况、内容质量),以确定排名的准备情况

SKILL.md

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):

  1. Seed topic. The broad subject area to build authority around.
  2. Existing content. Does the site already have pages on this topic? List them.
  3. Business relevance. How does this topic connect to the product or service?
  4. 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:

SubtopicExisting Page?Quality (1-5)TrafficGap?
[subtopic 1]/blog/topic-14500/moNo
[subtopic 2]Yes
[subtopic 3]/blog/old-post250/moPartial (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 PageTo PageAnchor TextContext
PillarSpoke 1"[subtopic 1] guide"In the subtopic 1 overview section
Spoke 1Pillar"[broad topic]"In the introduction or conclusion
Spoke 1Spoke 2"[subtopic 2]"Where subtopic 2 is mentioned contextually
Spoke 3Spoke 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
MetricScoreThreshold
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 StateCoverageLink HealthContent QualityExpected Result
Incomplete<50%<70%AnyPillar unlikely to rank page 1; spokes rank individually at best
Developing50-70%70-90%50-80%Pillar may appear page 2-3; some spokes rank for long-tail
Competitive70-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 TypeMinimum CountDirection
Pillar → each spoke1 per spokeDownward — link from the relevant section of the pillar
Each spoke → pillar1 per spokeUpward — "our complete [topic] guide"
Spoke ↔ sibling spokes2-4 per spokeLateral — where contextually natural
Cross-cluster bridges0-2 per clusterBetween 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:

  1. Pillar page first — even as a draft, it establishes the hub
  2. Highest-opportunity spokes next — pages targeting gaps with the best opportunity scores
  3. Refresh existing spokes — update and relink any partial-gap pages
  4. Remaining spokes — fill out the cluster over time
  5. 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-strategy to see existing clusters with coverage metrics, or use list_clusters and get_cluster_detail to check cluster health and identify gaps.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.63%
按下载量换算4,572

Claude

29.38%
按下载量换算3,667

Cursor

15.91%
按下载量换算1,986

Gemini CLI

9.34%
按下载量换算1,166

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills