Agent skill · Content & Marketing

blog-cluster

Semantic topic cluster planning and automated execution engine for claude-blog. Performs SERP-based keyword research, groups keywords by search intent and SERP overlap, builds a hub-and-spoke cluster architecture, generates an interactive SVG cluster map, and executes the full cluster by orchestrating blog-write calls with shared cluster context and automatic internal-link injection. Fills the strategy-to-execution gap: blog-strategy plans the blueprint, blog-cluster builds the house. Use when user says "blog cluster", "topic cluster", "content cluster", "cluster plan", "cluster execute", "pil

Infrasity-Labsgithub.com/Infrasity-LabsGitHub ↗
claude-codeMIT
Install
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-cluster --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 17 KB
Bundled scripts: none
Requires: Requires Claude Code and claude-blog (provides blog-write, blog-chart, blog-image)
Path: .claude/skills/blog-cluster/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 97
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Blog Cluster (Semantic Topic Cluster Engine) Plans and executes entire interlinked content ecosystems from a single seed keyword. Three layers: Semantic Clustering (the brain), Cluster Architecture (the structure), and Execution Engine (the machine). ## Commands | Command | What it does | |---------|--------------| | `/blog cluster` | Interactive. Asks whether to plan or execute. | | `/blog cluster plan <seed-keyword>` | SERP-based semantic analysis. Outputs cluster plan + map. | | `/blog cluster plan --from strategy [path]` | Imports existing `blog-strategy` cluster build plan and validates against SERP data. | | `/blog cluster execute [path-to-plan]` | Sequential `blog-write` calls with cluster context and auto-interlinks. | ## Key references (load on demand) - `references/semantic-clustering.md` (SERP overlap analysis, intent classification, keyword universe expansion) - `references/cluster-architecture.md` (hub-and-spoke specs, schema strategy, link-density rules) - `references/execution-workflow.md` (execution order, context injection, scorecard, failure handling) ## Cross-references to existing claude-blog skills | Skill | When this skill calls it | |-------|---------------

What's inside
Steps it walks through
  1. Commands
  2. Key references (load on demand)
  3. Cross-references to existing claude-blog skills
  4. Command Routing
  5. Plan Phase: /blog cluster plan <seed-keyword>
  6. Step 1. Seed keyword expansion
  7. Step 2. Semantic clustering
  8. Step 3. Cluster architecture design
  9. Step 4. Internal link matrix
  10. Step 5. Generate output files
  11. Step 6. Present plan to user
  12. Strategy Import: /blog cluster plan --from strategy [path]
  13. Execute Phase: /blog cluster execute [path-to-plan]
  14. Step 1. Load plan
Ships with 3 files
  • references/cluster-architecture.md
  • references/execution-workflow.md
  • references/semantic-clustering.md
More from dev-gtm-claude-skills
All skills →
About this skill
What does the blog-cluster skill do?

Semantic topic cluster planning and automated execution engine for claude-blog. Performs SERP-based keyword research, groups keywords by search intent and SERP overlap, builds a hub-and-spoke cluster architecture, generates an interactive SVG cluster map, and executes the full cluster by orchestrating blog-write calls with shared cluster context and automatic internal-link injection. Fills the strategy-to-execution gap: blog-strategy plans the blueprint, blog-cluster builds the house. Use when user says "blog cluster", "topic cluster", "content cluster", "cluster plan", "cluster execute", "pil

How do I install it?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-cluster --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going