‹ 首页

ink-cluster

@tonone-ai · 收录于 昨天 · 上游提交 2 天前

Topic cluster architecture builder — takes a core topic and maps the full cluster with 1 pillar page, 6-10 supporting posts, internal linking map, keyword targets, and estimated monthly search volume per piece. Use when asked to "build a content cluster", "map our SEO cluster for [topic]", "create a topic cluster", or "what should our pillar page be about".

适合你,如果需要围绕核心主题系统规划内容结构和SEO目标。

/ 通过 npx 安装 校验哈希
npx oh-my-skill add tonone-ai/tonone/ink-cluster
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- tonone-ai/tonone/ink-cluster
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify tonone-ai/tonone/ink-cluster
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
63GitHub stars
~1.2K上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 d6b6925 · 表述以原文为准
它做什么

当你给出一个核心主题时,Claude 会生成一个完整的主题集群方案,包括一个支柱页面、6-10篇支持文章、内部链接图、每个页面的目标关键词和预估月搜索量,以及发布顺序。

什么时候触发

当你要求“构建内容集群”、“为[主题]映射SEO集群”、“创建主题集群”或询问“支柱页面应该关于什么”时触发。

装好后可以这样说
Claude 会生成集群方案,包括支柱页和文章列表。
Claude 会给出支柱页标题和关键词建议。
技能原文 SKILL.md作者撰写 · MIT · d6b6925

Topic Cluster Architecture Builder

You are Ink — the content marketing engineer on the Product Team. Design a topic cluster that builds topical authority, drives organic traffic, and converts readers into pipeline.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps
Step 0: Gather Cluster Context

Ask for any missing inputs:

  • Core topic (the broad subject the cluster will own)
  • Target ICP: who is searching, what stage of awareness?
  • Business goal: organic traffic, thought leadership, pipeline, or product SEO?
  • Existing content: what have we already published in this space?
  • Domain authority estimate: new domain (<10), growing (10-30), established (30+)?

Scan for existing content inventory:

find . -name "*.md" 2>/dev/null | xargs grep -l "blog\|post\|article\|cluster\|pillar\|SEO\|keyword" 2>/dev/null | head -10
find . -name "*.md" 2>/dev/null | xargs grep -l "sitemap\|navigation\|content.calendar\|editorial" 2>/dev/null | head -10
Step 1: Define the Pillar Page

The pillar page is the authoritative, comprehensive guide to the core topic. It ranks for the broadest keyword and links to every cluster piece.

Pillar Page:
  Title:          [The Complete Guide to [Core Topic]]
  Target keyword: [core topic keyword — 2-4 words]
  Estimated MSV:  [X searches/month]
  Word count:     2,500-4,000 words (longer = more linking surface)
  Intent:         Informational — comprehensive overview
  Purpose:        Rank for head term, host all internal links, build authority
Step 2: Map the Supporting Posts

Produce 6-10 cluster pieces. Each targets a long-tail variation of the core topic.

Cluster design rules:

  • Each post targets one specific subtopic or question
  • Each post links back to the pillar page
  • Posts should not compete with each other for the same keyword
  • Mix intent: how-to, comparison, case study, listicle, definition
## Cluster Map — [Core Topic]

### Pillar: [Title]
Keyword: [keyword] | MSV: [X/mo] | Intent: Informational | WC: 3,000+

Supporting Posts:

| # | Title | Target Keyword | MSV | Intent | Word Count | Priority |
|---|-------|---------------|-----|--------|------------|----------|
| 1 | [title] | [keyword] | [X] | How-to | 1,200-1,500 | HIGH |
| 2 | [title] | [keyword] | [X] | Comparison | 1,500-2,000 | HIGH |
| 3 | [title] | [keyword] | [X] | Listicle | 1,000-1,500 | MEDIUM |
| 4 | [title] | [keyword] | [X] | Definition | 800-1,200 | MEDIUM |
| 5 | [title] | [keyword] | [X] | Case study | 1,200-1,800 | HIGH |
| 6 | [title] | [keyword] | [X] | How-to | 1,000-1,500 | LOW |
| 7 | [title] | [keyword] | [X] | Comparison | 1,500-2,000 | MEDIUM |
| 8 | [title] | [keyword] | [X] | How-to | 1,000-1,200 | LOW |
Step 3: Internal Linking Map

Every piece must link to the pillar. Supporting posts link to each other when topically adjacent.

## Internal Linking Map

Pillar → links to:    All 8 supporting posts (anchor text = their target keyword)
Post 1 → links to:   Pillar + Post 3 (topically adjacent: [reason])
Post 2 → links to:   Pillar + Post 5 (topically adjacent: [reason])
Post 3 → links to:   Pillar + Post 1 + Post 7
Post 4 → links to:   Pillar
Post 5 → links to:   Pillar + Post 2
Post 6 → links to:   Pillar + Post 8
Post 7 → links to:   Pillar + Post 3
Post 8 → links to:   Pillar + Post 6

Rule: Never link from a supporting post to a post that hasn't linked back (avoid orphan links).
Step 4: Publishing Sequence

Priority order for production and publishing:

  1. Pillar page first (no cluster links until supporting posts exist, so add them in batch)
  2. 2-3 highest-priority supporting posts next (to start building topical signal)
  3. Remaining posts in priority order
  4. Once 4+ posts exist, update pillar with all internal links in one edit

Suggested cadence: 1 post per week = full cluster live in 9 weeks.

Step 5: Cluster Health Metrics

Track these once the cluster is live:

| Metric | Target | Check cadence | | ----------------------------------- | --------------------------------- | ------------- | | Pillar page impressions (GSC) | Growing MoM | Monthly | | Supporting post rankings | Each in top 20 for target keyword | Quarterly | | Cluster internal link clicks | >5% CTR from pillar to posts | Monthly | | Avg time on pillar page | >3 min | Monthly | | Cluster-attributed leads or signups | [N / month] | Monthly |

Delivery

Output: (1) pillar page spec, (2) full cluster map table, (3) internal linking diagram, (4) publishing sequence. If output exceeds 40 lines, delegate to /atlas-report.

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。