Loading
>
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add AgriciDaniel/claude-blog --skill blog-cluster -a cursor -y
>
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).
Adapted from the semantic-cluster-engine submission by Lutfiya Miller (winner, AI Marketing Hub Pro Challenge, March 2026, 95/100 Exemplary). Original repository: https://github.com/Drfiya/semantic-cluster-engine This port keeps the Plan + Execute architecture and the cluster context innovation, removes brand-specific (ScienceExperts.ai) styling and image prompts, and routes through claude-blog's existing sub-skills.
| 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. |
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)| Skill | When this skill calls it |
|---|---|
/blog strategy | Upstream planning. plan --from strategy consumes its Cluster Build Plan tables. |
/blog write | Per-post execution. Each spoke and the pillar are produced by blog-write with a prepended cluster-context block. |
/blog chart | Invoked internally by blog-write for inline SVG charts. No direct call from this skill. |
/blog image | Optional hero image generation per post. Model selection is delegated to blog-image; prefer current Gemini image models when available. |
/blog seo-check | Recommended after execution for per-post on-page validation. |
/blog cannibalization | Recommended after execution to confirm zero keyword overlap across the cluster. |
/blog schema | Recommended after execution to add BreadcrumbList, ItemList, and Article schema. |
This skill never modifies files belonging to other skills. It calls them via the Task tool or as orchestrated sub-skills.
/blog cluster, ask: "Would you like to plan a new cluster or execute an existing plan?"plan <keyword> to the Plan Phase (below)plan --from strategy [path] to the Strategy Import flow (below)execute [path], build, or run to the Execute Phase (below)/blog cluster plan <seed-keyword>Reference: references/semantic-clustering.md
Use WebSearch to expand the seed into a keyword universe of 30 to 50 phrases:
<seed> to capture related searches and "People also ask".<seed> guide, <seed> tips, <seed> tools, <seed> examples, <seed> vs, best <seed>, how to <seed>.what is <seed>, how does <seed> work, why <seed>, <seed> for beginners.<seed> 2026.Group the expanded keywords using the priority rules in references/semantic-clustering.md:
Reference: references/cluster-architecture.md
Build the hub and spoke:
pillar-page. Links down to every spoke.Cluster formation rules:
For each spoke S:
S to Pillar (always; anchor text uses the pillar's primary keyword).S (always; anchor text uses S's primary keyword).S to other spokes in the same cluster (2 to 3 links each, contextual anchors).S to spokes in adjacent clusters (0 to 1 links, only when semantically relevant).Verify every spoke has at least 2 incoming links. Count total planned interlinks.
All plan and execute artifacts go into a single subdirectory of the current working directory. Canonicalize the output directory, refuse symlinks, and reject writes outside the cluster directory. Slugs must match lowercase letters, numbers, and hyphens only; reject absolute paths, .., path separators inside slugs, and hidden control characters.
<cwd>/
└── cluster-<seed-keyword-slug>/
├── cluster-plan.json
├── cluster-map.html
├── pillar-<slug>.md (Execute Phase)
├── <spoke-slug>.md (Execute Phase, one per spoke)
└── cluster-scorecard.md (Execute Phase)
cluster-plan.json schema{
"seed_keyword": "<seed>",
"generated_at": "YYYY-MM-DDTHH:MM:SSZ",
"pillar": {
"id": "P",
"title": "Title of the pillar",
"primary_keyword": "broadest keyword",
"secondary_keywords": ["..."],
"search_volume_estimate": "high|medium|low",
"template": "pillar-page",
"word_count_target": 3000,
"cluster": "pillar"
},
"clusters": [
{
"name": "Cluster A: Theme",
"intent": "informational|commercial|transactional",
"color": "#2563eb",
"posts": [
{
"id": "A1",
"title": "Post title",
"primary_keyword": "long-tail keyword",
"secondary_keywords": ["..."],
"search_volume_estimate": "high|medium|low",
"template": "how-to-guide",
"word_count_target": 1500,
"links_to": ["P", "A2"],
"links_from": ["P", "A2"]
}
]
}
],
"total_posts": 9,
"total_interlinks": 23,
"estimated_total_words": 18000
}
Note: volume estimates are relative indicators (high, medium, low) derived from SERP signals, not absolute search volumes. For precise data, the user should consult Ahrefs, SEMrush, or DataForSEO (claude-blog provides the seo-dataforseo companion sibling).
cluster-map.html (XSS-safe)A static, self-contained HTML file with an embedded SVG visualization. Hard rules for the writer:
<script> blocks. No onclick, onmouseover, or any on* event attributes anywhere in the document.<src> references.& with &, < with <, > with >, " with ", and ' with ' before insertion.:hover only. No JavaScript.<title> child elements inside SVG nodes for accessible tooltips (browser native, no script).The map shows: a central pillar node, color-coded cluster groups radiating outward, spoke nodes within each cluster, and link lines connecting related nodes.
Show a summary table of clusters and posts, total interlinks, estimated words, and the file paths. Ask for confirmation before proceeding to execution. Wait for explicit user approval. Do not auto-execute.
/blog cluster plan --from strategy [path]Bridges blog-strategy output into a cluster plan.
Cluster Build Plan table with the columns # | Spoke Topic | Template | Target Keyword | Word Count | Internal Links (the format produced by /blog strategy).P), the spoke rows, template assignments, target keywords, word counts, and link relationships.cluster-plan.json and cluster-map.html using the same outputs as the standard Plan Phase./blog cluster execute [path-to-plan]Reference: references/execution-workflow.md
Read cluster-plan.json from the user-specified path or the most recent cluster-*/cluster-plan.json in the working directory. Validate JSON structure. If no plan exists, return: "No cluster plan found. Run /blog cluster plan <seed-keyword> first."
Before reading a user-supplied plan path, canonicalize it relative to the current working directory. Reject absolute paths, .., symlinks, non-cluster-plan.json filenames, and any path outside the selected cluster directory. Constrain all generated post, image, map, and scorecard outputs to that cluster directory.
(cluster priority, search_volume_estimate desc, post id alphabetical). Cluster priority is the sum of estimated volumes within the cluster (highest first).blog-writeConstruct the cluster context block (full schema in references/execution-workflow.md) and prepend it to the topic prompt passed to the Task tool invoking blog-write. The context tells blog-write the cluster name, the post's role (pillar or spoke), the primary and secondary keywords, the chosen template, the word count target, the list of already-written posts (link to these), the list of upcoming posts (use [INTERNAL-LINK] placeholders), and the linking requirements for this post.
FLOW evidence triple propagation (required). The cluster context must include this directive for every spoke and the pillar: "Apply the FLOW evidence triple to every public statistic. Year anchor in prose ('In 2026,'), inline citation with publisher and title, URL with retrieval date in the source block. Drop unverifiable stats. Replace contradicted ones."
This cascade is required because cluster execution is a high-leverage operation (5 to 15 posts at once). Without explicit propagation, individual spokes could silently skip evidence discipline. See skills/blog/references/flow-alignment.md.
The context also instructs blog-write to run autonomously: skip topic clarification, skip outline approval, do not auto-detect template, do not pause.
Output format: standard markdown (.md) by default, matching blog-write's default. If the user explicitly requests HTML, set the platform target accordingly. Do not impose any brand-specific CSS or wordmark; that is the user's responsibility downstream.
If blog-image is available, call /blog image generate via the Task tool to produce a 16:9 hero image for the post and place it in cluster-<slug>/images/<post-slug>-hero.png. Delegate provider selection to blog-image, prefer current Gemini image models when available, and record the model ID in the scorecard. If image generation is unavailable or fails, log a warning and continue without images. Image generation is non-blocking.
After each post is written:
[INTERNAL-LINK: keyword -> filename.md] markers that reference the just-written post.[keyword](filename.md).cluster:, cluster_role:, cluster_group:).If blog-write returns a quality-gate failure for any post, stop the batch immediately. Save progress, mark the failed post and all remaining posts as skipped, and tell the user to inspect or retry the failed post manually before continuing. Do not keep generating 5 to 15 posts after a quality failure, because that can create scaled-content-abuse risk.
If blog-write fails before content is generated because of a timeout or runtime error, log the failure in the scorecard and stop unless the user explicitly resumes after checking the cause.
If the user cancels mid-execution, save progress and note completed posts. On the next /blog cluster execute, detect already-written files and resume from the next unwritten post.
cluster-scorecard.mdAfter all attempted posts complete, produce a markdown scorecard covering:
/blog analyze on each in parallel via Task) and the cluster average.references/execution-workflow.md).[INTERNAL-LINK] markers./blog cannibalization for a deeper pass./blog schema), per-post SEO validation (/blog seo-check), repurposing (/blog repurpose).Return a concise summary to the user with totals, the scorecard path, and the next-action commands.
| File | Phase | Format |
|---|---|---|
cluster-plan.json | Plan | JSON |
cluster-map.html | Plan | Static HTML + inline SVG, no JavaScript |
pillar-<slug>.md | Execute | Markdown (or platform-detected format) |
<spoke-slug>.md | Execute | Markdown (or platform-detected format) |
images/<post-slug>-hero.png | Execute (optional) | PNG via blog-image |
cluster-scorecard.md | Execute | Markdown |
| Gate | Check | Action on fail |
|---|---|---|
| Cluster minimum | At least 2 clusters with at least 2 posts each | Warn during plan; suggest expansion |
| Cannibalization | No two posts share primary keyword | Block execution; require plan adjustment |
| Link completeness | Every post has 2 or more incoming internal links | Warn in scorecard |
| Word count | Pillar at least 2,500 words; spokes at least 1,200 words | Pass to blog-write as a hard constraint |
| Intent diversity | At least 2 distinct intents across clusters | Warn in scorecard |
| Template diversity | At least 3 distinct templates across the cluster | Warn in scorecard |
| Scenario | Action |
|---|---|
| Seed keyword too broad (more than 50 keyword variants) | Suggest narrowing the focus before clustering. |
| Seed keyword too narrow (fewer than 5 keyword variants) | Offer a smaller cluster (pillar plus 2 to 3 spokes) or suggest broadening. |
| WebSearch unavailable | Produce a draft plan only and require user confirmation, imported keyword data, or SERP data before execution. |
blog-write fails a quality gate or content generation | Stop the batch, save progress, mark remaining posts as skipped, and require manual inspection or explicit resume. |
blog-write not installed | Return: "blog-cluster requires claude-blog. Install it before running this skill." |
cluster-plan.json malformed | Validate JSON and report parse errors with line numbers. |
| User cancels execution | Save progress; resume on next invocation with already-written posts auto-detected. |
| Optional image generation unavailable or failed | Skip hero image generation; warn once at start of execute, not per post. |
| Skill | Role | What blog-cluster adds |
|---|---|---|
blog-strategy | Plans 3 to 5 content pillars and draws hub-and-spoke diagrams as a strategic exercise | Performs SERP-based semantic clustering, then executes the plan into real, interlinked posts. |
blog-calendar | Schedules publication dates around topic clusters | Does not build clusters or write posts; this skill does both. |
blog-cannibalization | Detects keyword overlap in existing content | Diagnostic only. blog-cluster prevents cannibalization at the planning stage. |
blog-write | Writes one post at a time | blog-cluster orchestrates many blog-write calls with shared cluster context and bidirectional linking. |
blog-outline | Generates a single SERP-informed outline | blog-cluster generates an outline-equivalent across an entire cluster, then writes the posts. |
blog-cluster is the general contractor: it analyzes the topic, draws the data-driven plan, and builds the entire structure from a single seed keyword.