CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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", "cluster map".

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally operational orchestration skill: concrete schemas, commands, and exact strings; explicit validation gates, bounded retries, and batch-stop feedback loops; and a well-signaled on-demand reference layer. The main defects are a dangling reference to a nonexistent "orchestration-details.md" at the top of the body, near-verbatim duplication of the keyword-expansion list between the body and semantic-clustering.md, and some marketing-flavored padding in the differentiation section.

Suggestions

Fix the dangling reference: "Read the main reference `orchestration-details.md`" names a file absent from references/ — either add the file to the bundle or repoint the instruction at one of the three existing references (likely execution-workflow.md), since this pointer sits on the critical pre-execution path.

Deduplicate Plan Phase Step 1: replace the five inlined keyword-expansion bullets with a one-line pointer to references/semantic-clustering.md ("expand the seed per the four-step process in semantic-clustering.md"), keeping the body's 30-to-50 phrase target as the only local constraint.

Trim the Differentiation section: drop the "general contractor" closing line and compress the five-row table to the rows that affect routing decisions (blog-strategy, blog-write, blog-cannibalization), moving the rest to a reference if needed.

DimensionReasoningScore

Conciseness

The body is dense and operational almost everywhere — path canonicalization rules, XSS escaping specifics, a one-time cost-consent protocol — with essentially no explanation of concepts Claude already knows. It falls short of anchor 5 because Plan Phase Step 1's five-item keyword-expansion list duplicates references/semantic-clustering.md nearly verbatim, and the closing differentiation table carries marketing padding ("blog-cluster is the general contractor: it analyzes the topic, draws the data-driven plan, and builds the entire structure").

4 / 5

Actionability

The instruction-only guidance is fully concrete: a complete cluster-plan.json schema, an exact output-directory tree, exact commands ("blog_preflight.py --draft <post folder> --reset-iterations"), an exact marker format ("[INTERNAL-LINK: anchor -> filename.md]"), exact error strings ("No cluster plan found. Run `/blog cluster plan <seed-keyword>` first."), and a verbatim cost question to ask the user. This matches anchor 5's copy-paste-ready standard with common cases covered; it is not anchor 4 because there are no meaningful gaps in executable specificity.

5 / 5

Workflow Clarity

Both phases have numbered, well-sequenced steps with explicit validation checkpoints throughout: user approval gates ("Ask for confirmation... Wait for explicit user approval. Do not auto-execute"), a quality-gate table with per-gate fail actions, a stop-the-batch feedback loop on gate failure with bounded retries ("at most 3 failed gate runs"), resume-on-next-invocation detection, and a scorecard link audit. As a batch operation it fully satisfies the batch-validation requirement, matching anchor 5 rather than anchor 4.

5 / 5

Progressive Disclosure

Structure is good: a dedicated "Key references (load on demand)" section plus per-phase "Reference:" signals, and all three named bundle files (semantic-clustering.md, cluster-architecture.md, execution-workflow.md) exist and are one level deep. It misses anchor 5 because "Read the main reference `orchestration-details.md`" names a file that does not exist in references/ (a dangling pointer on the critical pre-execution path), and because the Step 1 expansion list is inlined in the body where it duplicates the reference. It is still clearly above anchor 3, whose signature defects (buried, unclear references; large inlined reference content) are mostly absent.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete, and comprehensive on capabilities, with an explicit trigger-phrase clause and an explicit boundary statement against the closest related skill (blog-strategy). The only meaningful gap is a handful of missing natural synonyms (hub-and-spoke, pillar page) in the trigger list, and a slight over-claim of "interactive" for a no-JavaScript static SVG map.

DimensionReasoningScore

Specificity

The description lists five-plus concrete actions — "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" — giving comprehensive capability coverage. It exceeds anchor 4 because coverage is comprehensive rather than having minor gaps; the only quibble is that "interactive" slightly overstates the CSS-hover-only map, but that is not enough to drop a level.

5 / 5

Completeness

It clearly answers both questions: the "what" is a multi-action capability list (research, clustering, architecture, map, execution) and the "when" is an explicit "Use when user says" clause with concrete trigger phrases. This mirrors the anchor-5 exemplar structure exactly; anchor 4 would require the when-clause to be less explicit than it is.

5 / 5

Trigger Term Quality

The explicit trigger list — "blog cluster", "topic cluster", "content cluster", "cluster plan", "cluster execute", "cluster map" — covers six natural phrases a user would plausibly say. It falls short of anchor 5 because natural synonyms such as "hub and spoke", "pillar page", or "content silo" are missing, but is well above anchor 3 since the core cluster phrasings are thoroughly and naturally covered.

4 / 5

Distinctiveness Conflict Risk

The boundary sentence "Fills the strategy-to-execution gap: blog-strategy plans the blueprint, blog-cluster builds the house" explicitly differentiates it from the nearest sibling skill, and action-oriented triggers ("cluster execute", "cluster plan") are distinct from sibling-skill triggers. Conflict risk is minimal, matching anchor 5 rather than anchor 4's "minor overlap risk with closely related skills".

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

AgriciDaniel/claude-blog

Path

skills/blog-cluster/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.