Local Content Strategy
garrettjsmith/localseoskills
Build a complete local content strategy from keyword research output.
A skill your agent uses when planning a topic cluster (hub + spokes) for a new content area.
Install Topic Cluster Planning
$ npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install inhouseseo/superseo-skills topic-cluster-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/topic-cluster-planning .claude/skills/topic-cluster-planning && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "topic-cluster-planning" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/topic-cluster-planning into .claude/skills/topic-cluster-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-cluster-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/inhouseseo/superseo-skills/tree/main/skills/topic-cluster-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install inhouseseo/superseo-skills topic-cluster-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/topic-cluster-planning .agents/skills/topic-cluster-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "topic-cluster-planning" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/topic-cluster-planning into .agents/skills/topic-cluster-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-cluster-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install inhouseseo/superseo-skills topic-cluster-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/topic-cluster-planning .cursor/skills/topic-cluster-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "topic-cluster-planning" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/topic-cluster-planning into .cursor/skills/topic-cluster-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-cluster-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/inhouseseo/superseo-skills.git --path skills/topic-cluster-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install inhouseseo/superseo-skills topic-cluster-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/topic-cluster-planning .gemini/skills/topic-cluster-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "topic-cluster-planning" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/topic-cluster-planning into .gemini/skills/topic-cluster-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-cluster-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install inhouseseo/superseo-skills topic-cluster-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/topic-cluster-planning .github/skills/topic-cluster-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "topic-cluster-planning" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/topic-cluster-planning into .github/skills/topic-cluster-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-cluster-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install inhouseseo/superseo-skills topic-cluster-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/topic-cluster-planning .opencode/skills/topic-cluster-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "topic-cluster-planning" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/topic-cluster-planning into .opencode/skills/topic-cluster-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topic-cluster-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
topic-cluster-planning- GitHub stars
- 352
- Token cost
- ~1.7k tokens
- SKILL.md length
- 951 words
- Files
- 6 (incl. references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when planning a topic cluster (hub + spokes) for a new content area.
- Works in 6 steps: Research the Topic Space → Identify the Hub → Map the Spokes → …
- Planning a topic cluster (hub + spokes) for a new content area
- SKILL.md covers Input, Role, Step 1: Research the Topic Space and Step 2: Identify the Hub, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Topic Cluster Planning is an agent skill from inhouseseo/superseo-skills. Use when planning a topic cluster (hub + spokes) for a new content area. The agent researches the space, identifies the hub topic, maps the spokes, and produces a specific content plan with internal linking strategy.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/first-link-weight-evidence.md`, `references/pillar-page-template.md` and `references/publishing-sequence-decisions.md`).
It sits in Writing & Content, covering Content strategy and On-page SEO. The repository describes itself as: 11 Claude skills for SEO: page audits, linkbuilding, article writing, E-E-A-T audits, semantic gap analysis, link building. Methodology from Koray Tuğberk, Kyle Roof, and Lily…. The licence is Apache-2.0.
When your agent uses it
- Planning a topic cluster (hub + spokes) for a new content area
- Tasks that involve Content strategy
- Tasks that involve On-page SEO
Example prompts
- “/topic-cluster-planning”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9cf22cc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Topic Cluster Planning loads about 1.7k tokens when it runs, and up to ~9.2k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 951 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from inhouseseo/superseo-skills at commit 9cf22cc, republished under its Apache-2.0 licence (© inhouseseo). 951 words, ~1,670 tokens.
Download SKILL.mdSave it as
.claude/skills/topic-cluster-planning/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- topic-cluster-planning
- description
- Use when planning a topic cluster (hub + spokes) for a new content area. The agent researches the space, identifies the hub topic, maps the spokes, and produces a specific content plan with internal linking strategy.
Topic Cluster Planning
Builds a hub-and-spoke architecture for a new content area. Hub = a broad pillar page that owns the topic. Spokes = specific articles that target long-tail keywords and link up to the hub. Done right, this signals topical authority to Google and concentrates link equity on the pages that matter.
Input
Seed topic or broad keyword (required). Example: "email marketing", "keto diet", "small business accounting".
Optionally: your domain, so the agent can check what you've already published in this space.
Role
You are a senior SEO content strategist specializing in topical authority architecture. You think in clusters, not individual articles.
Step 1: Research the Topic Space
Google the seed topic. Read:
- The top 10 results for the broad keyword
- The People Also Ask questions
- The "Searches related to" at the bottom of the SERP
- 2-3 major publications in the space to see how they structure their content
Note:
- Who dominates the broad keyword? (This tells you the difficulty level.)
- What sub-topics emerge from PAA and related searches?
- What specific questions do people ask?
Use only PAA questions and related searches you actually saw — don't pad the spoke list with invented queries. If the SERP shows few, say so and lean harder on competitor coverage.
Step 2: Identify the Hub
The hub is the one page that deserves to own the broad topic. It should:
- Target the broad/seed keyword directly
- Cover the topic comprehensively at a high level (don't go deep on every sub-topic)
- Link out to all the spoke articles
Hub content type options:
- Ultimate guide ("The Complete Guide to X") — best for broad informational topics
- Pillar + chapters (pillar page with a TOC linking to deep-dive chapters) — best for very broad topics with clear sub-chapters
- Category page with curated featured content — best for product/service topics
State your recommended hub format with reasoning.
Step 3: Map the Spokes
From the PAA questions, related searches, and competitor coverage, identify 8-15 specific spoke topics. Each spoke should:
- Target a long-tail keyword or specific question
- Go deeper on one narrow sub-topic than the hub can
- Link back to the hub (primary)
- Link to 2-3 related spokes
For each spoke, specify:
- Target keyword / question it answers
- Content type (how-to / definition / comparison / case study / listicle)
- Approximate word count
- Why it matters for the cluster (what sub-topic does it own?)
Rule of thumb: a spoke should answer a question the hub can only summarize.
Step 4: Map the Internal Linking
Draw the link graph:
- Every spoke links to the hub with a keyword-rich anchor
- Hub links to every spoke (usually in a "In this guide" TOC or a "Related deep dives" section)
- Related spokes link to each other (but sparingly — don't over-link)
- External links from the hub to 3-5 authoritative sources in the space
Critical: the first link from any spoke TO the hub is what Google's algorithm weights most heavily. Make sure it's contextual (within the article body), with a descriptive anchor text.
Step 5: Publishing Order
Don't publish the hub first. Publish 3-4 high-quality spokes first, then the hub with links to them. Then publish the remaining spokes, each linking back to the now-established hub.
This prevents the hub from launching as a link-less orphan that has nothing to point to.
Step 6: Output
Cluster Overview
- Seed topic | Estimated difficulty (Easy / Moderate / Hard) based on SERP competition
- Realistic timeline to build out (how many articles, how many months)
Show full SKILL.md (387 more words)Show less
Hub
- Recommended format (Ultimate guide / Pillar + chapters / Category)
- Target keyword (the broad seed)
- Main H2 sections (roughly 5-10)
- Approximate word count
- What the hub should NOT cover in depth (save that for spokes)
Spoke List
| # | Spoke Topic | Target Keyword | Content Type | Words | Hub Anchor Text |
|---|
8-15 rows. Sorted by priority: highest-impact/easiest-to-rank first.
Publishing Sequence
- Month 1: 3-4 spokes (pick from rows 1-4)
- Month 2: Publish the hub, link it to the published spokes
- Month 3-4: Remaining spokes, each linking back to the hub
Internal Link Map
A simple list showing which spokes link to which other spokes. Not every spoke needs to link to every other — just the naturally related ones.
External Linking Strategy
3-5 authoritative external sources the hub should cite. (Not competitors — actual authoritative sources: research papers, industry standards, government/university resources, or the primary creators of the concepts you're discussing.)
Success Metrics
- Month 3: Hub should rank somewhere in top 50 for the seed keyword
- Month 6: At least 2-3 spokes ranking in top 20 for their long-tail keywords
- Month 9: Hub ranking top 20, cluster driving consistent organic traffic
- Month 12: Cluster becomes a topical authority signal for the whole domain
What to Ignore
- Publishing everything at once — Google needs time to see the cluster form. Spread it over 3-4 months.
- Over-linking between spokes — if it doesn't feel natural in the article, skip it
- Keyword density in the hub — the hub is about breadth, not keyword stuffing
Next Step
For each spoke, use content-brief with the spoke's target keyword to produce a writer-ready brief. Then write-content to write the article.
Bundled references
Load from references/ only when the step calls for them.
first-link-weight-evidence.md— the evidence behind "the first link in the body is weighted most heavily" and why it matters for spoke → hub linking (Step 4, when briefing the writer on anchor placement)publishing-sequence-decisions.md— the full decision framework for "don't publish the hub first" and the exceptions (Step 5, when the user pushes back on the staggered launch)spoke-selection-worked-example.md— a full cluster worked end-to-end (seed → hub → 12 spokes → link map) for a sample niche, to anchor Step 3 when spoke selection feels arbitrarytopic-cluster-strategy.md— the theory behind hub-and-spoke architecture and topical authority signals (background, optional)pillar-page-template.md— exact H1/H2 structure for the hub page (Step 2, after the hub format is chosen)
© inhouseseo, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in skills/topic-cluster-planning of inhouseseo/superseo-skills.
- SKILL.md
- references/first-link-weight-evidence.md
- references/pillar-page-template.md
- references/publishing-sequence-decisions.md
- references/spoke-selection-worked-example.md
- references/topic-cluster-strategy.md
Open the folder on GitHubat commit 9cf22cc
Compare with similar skills
Topic Cluster Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Topic Cluster Planning this skillinhouseseo/superseo-skills | 352 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Local Content Strategygarrettjsmith/localseoskills | 121 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Blog BriefAgriciDaniel/claude-blog | 2.3k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Blog BriefAgriciDaniel/claude-blog | 2.3k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Content Brief Factorygooseworks-ai/goose-skills | 1.2k | 1 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Blog BriefInfrasity-Labs/dev-gtm-claude-skills | 136 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Blog Brief
AgriciDaniel/claude-blog
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…
Blog Brief
AgriciDaniel/claude-blog
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…
Content Brief Factory
gooseworks-ai/goose-skills
Generate detailed, differentiated content briefs at scale. An agent skill from gooseworks-ai/goose-skills.
Blog Brief
Infrasity-Labs/dev-gtm-claude-skills
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…
Content Creator
sickn33/agentic-awesome-skills
Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.
More from inhouseseo/superseo-skills
All 11 skills in this repoContent Brief
inhouseseo/superseo-skills
A skill your agent uses when planning a new article. An agent skill from inhouseseo/superseo-skills.
Eeat Audit
inhouseseo/superseo-skills
A skill your agent uses when auditing a page for E-E-A-T signals.
Expert Interview
inhouseseo/superseo-skills
A skill your agent uses when extracting first-party expertise from a subject-matter expert before writing content.
Featured Snippet Optimizer
inhouseseo/superseo-skills
A skill your agent uses when you want to win a featured snippet for a keyword you already rank for.
Improve Content
inhouseseo/superseo-skills
A skill your agent uses when rewriting or refreshing an existing page that's underperforming.
Keyword Deep Dive
inhouseseo/superseo-skills
A skill your agent uses when planning to rank for a specific keyword.
Related
Categories
Questions about Topic Cluster Planning
What does Topic Cluster Planning do?
A skill your agent uses when planning a topic cluster (hub + spokes) for a new content area. Topic Cluster Planning is an agent skill from inhouseseo/superseo-skills. Use when planning a topic cluster (hub + spokes) for a new content area.
When should I use Topic Cluster Planning?
Topic Cluster Planning fits situations like: planning a topic cluster (hub + spokes) for a new content area; tasks that involve Content strategy; tasks that involve On-page SEO.
How do I install Topic Cluster Planning in Claude Code?
Run `npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a claude-code`. Or copy the skill folder (skills/topic-cluster-planning in inhouseseo/superseo-skills) into .claude/skills/topic-cluster-planning in your project. Claude Code loads it when a task matches its description.
How do I install Topic Cluster Planning in Codex?
Run `npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a codex`. Or copy the skill folder (skills/topic-cluster-planning in inhouseseo/superseo-skills) into .agents/skills/topic-cluster-planning in your project. Codex loads it when a task matches its description.
Can I use Topic Cluster Planning in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add inhouseseo/superseo-skills --skill topic-cluster-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/topic-cluster-planning, .gemini/skills/topic-cluster-planning, .github/skills/topic-cluster-planning and .opencode/skills/topic-cluster-planning in your project.
What does Topic Cluster Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Topic Cluster Planning is instructions for the agent only.
Does Topic Cluster Planning access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Topic Cluster Planning safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Topic Cluster Planning use?
Topic Cluster Planning is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Topic Cluster Planning use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.5k tokens, read only when the agent opens those files.
What are the alternatives to Topic Cluster Planning?
Skills that share tags, products or a category with Topic Cluster Planning: Local Content Strategy (garrettjsmith/localseoskills, 121 stars), Blog Brief (AgriciDaniel/claude-blog, 2.3k stars), Blog Brief (AgriciDaniel/claude-blog, 2.3k stars) and Content Brief Factory (gooseworks-ai/goose-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Topic Cluster Planning?
inhouseseo (a GitHub user) maintains it in inhouseseo/superseo-skills, which has 352 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 3, 2026.
Source: inhouseseo/superseo-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.