$npx -y skills add AgriciDaniel/claude-blog --skill blog-clusterSemantic 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 cl
| 1 | # Blog Cluster (Semantic Topic Cluster Engine) |
| 2 | |
| 3 | Plans and executes entire interlinked content ecosystems from a single seed |
| 4 | keyword. Three layers: Semantic Clustering (the brain), Cluster Architecture |
| 5 | (the structure), and Execution Engine (the machine). |
| 6 | |
| 7 | > Adapted from the **semantic-cluster-engine** submission by Lutfiya Miller |
| 8 | > (winner, AI Marketing Hub Pro Challenge, March 2026, 95/100 Exemplary). |
| 9 | > Original repository: https://github.com/Drfiya/semantic-cluster-engine |
| 10 | > This port keeps the Plan + Execute architecture and the cluster context |
| 11 | > innovation, removes brand-specific (ScienceExperts.ai) styling and image |
| 12 | > prompts, and routes through claude-blog's existing sub-skills. |
| 13 | |
| 14 | ## Commands |
| 15 | |
| 16 | | Command | What it does | |
| 17 | |---------|--------------| |
| 18 | | `/blog cluster` | Interactive. Asks whether to plan or execute. | |
| 19 | | `/blog cluster plan <seed-keyword>` | SERP-based semantic analysis. Outputs cluster plan + map. | |
| 20 | | `/blog cluster plan --from strategy [path]` | Imports existing `blog-strategy` cluster build plan and validates against SERP data. | |
| 21 | | `/blog cluster execute [path-to-plan]` | Sequential `blog-write` calls with cluster context and auto-interlinks. | |
| 22 | |
| 23 | ## Key references (load on demand) |
| 24 | |
| 25 | - `references/semantic-clustering.md` (SERP overlap analysis, intent classification, keyword universe expansion) |
| 26 | - `references/cluster-architecture.md` (hub-and-spoke specs, schema strategy, link-density rules) |
| 27 | - `references/execution-workflow.md` (execution order, context injection, scorecard, failure handling) |
| 28 | |
| 29 | ## Cross-references to existing claude-blog skills |
| 30 | |
| 31 | | Skill | When this skill calls it | |
| 32 | |-------|--------------------------| |
| 33 | | `/blog strategy` | Upstream planning. `plan --from strategy` consumes its Cluster Build Plan tables. | |
| 34 | | `/blog write` | Per-post execution. Each spoke and the pillar are produced by `blog-write` with a prepended cluster-context block. | |
| 35 | | `/blog chart` | Invoked internally by `blog-write` for inline SVG charts. No direct call from this skill. | |
| 36 | | `/blog image` | Optional hero image generation per post (graceful fallback if `nanobanana-mcp` is not configured). | |
| 37 | | `/blog seo-check` | Recommended after execution for per-post on-page validation. | |
| 38 | | `/blog cannibalization` | Recommended after execution to confirm zero keyword overlap across the cluster. | |
| 39 | | `/blog schema` | Recommended after execution to add `BreadcrumbList`, `ItemList`, and `Article` schema. | |
| 40 | |
| 41 | This skill never modifies files belonging to other skills. It calls them via the Task tool or as orchestrated sub-skills. |
| 42 | |
| 43 | ## Command Routing |
| 44 | |
| 45 | 1. Parse the user's command to determine the sub-command. |
| 46 | 2. If the user typed only `/blog cluster`, ask: "Would you like to **plan** a new cluster or **execute** an existing plan?" |
| 47 | 3. Route: |
| 48 | - `plan <keyword>` to the Plan Phase (below) |
| 49 | - `plan --from strategy [path]` to the Strategy Import flow (below) |
| 50 | - `execute [path]`, `build`, or `run` to the Execute Phase (below) |
| 51 | |
| 52 | --- |
| 53 | |
| 54 | ## Plan Phase: `/blog cluster plan <seed-keyword>` |
| 55 | |
| 56 | Reference: `references/semantic-clustering.md` |
| 57 | |
| 58 | ### Step 1. Seed keyword expansion |
| 59 | |
| 60 | Use WebSearch to expand the seed into a keyword universe of 30 to 50 phrases: |
| 61 | |
| 62 | 1. Direct search of `<seed>` to capture related searches and "People also ask". |
| 63 | 2. Long-tail expansion: `<seed> guide`, `<seed> tips`, `<seed> tools`, `<seed> examples`, `<seed> vs`, `best <seed>`, `how to <seed>`. |
| 64 | 3. Question mining: `what is <seed>`, `how does <seed> work`, `why <seed>`, `<seed> for beginners`. |
| 65 | 4. Intent variants: add commercial modifiers (best, top, review, comparison, pricing), informational modifiers (guide, tutorial, explained, examples), and transactional modifiers (buy, download, tool, software, service). |
| 66 | 5. Year freshness: `<seed> 2026`. |
| 67 | |
| 68 | ### Step 2. Semantic clustering |
| 69 | |
| 70 | Group the expanded keywords using the priority rules in `references/semantic-clustering.md`: |
| 71 | |
| 72 | 1. **SERP Overlap Analysis** is the primary signal. Two keywords with 5 or more shared top-10 results target the same intent and b |