seo-keyword-cluster-builder
SEO keyword clustering with topic organization, content hub architecture, internal linking strategies. Use for content strategy, keyword research, pillar page structures, or encountering cluster organization, hub architecture, internal linking errors.
54
59%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/seo-keyword-cluster-builder/skills/seo-keyword-cluster-builder/SKILL.mdQuality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities in SEO content architecture and provides explicit trigger guidance via a 'Use for...' clause. The trigger terms are natural and cover multiple user phrasings. The only minor weakness is that some terms like 'content strategy' are broad enough to potentially overlap with other marketing or SEO skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'SEO keyword clustering', 'topic organization', 'content hub architecture', 'internal linking strategies'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (SEO keyword clustering, topic organization, content hub architecture, internal linking strategies) and 'when' with an explicit 'Use for...' clause listing trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'content strategy', 'keyword research', 'pillar page structures', 'cluster organization', 'hub architecture', 'internal linking'. These cover common variations of how users would describe SEO content planning tasks. | 3 / 3 |
Distinctiveness Conflict Risk | While SEO keyword clustering and hub architecture are fairly niche, terms like 'content strategy' and 'keyword research' could overlap with broader SEO or content marketing skills. The description is specific enough to reduce most conflicts but 'content strategy' is quite broad. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is excessively verbose, explaining many SEO concepts Claude already understands while providing mostly template-level guidance rather than truly actionable instructions. The content would benefit enormously from being split into a concise overview with references to detailed templates, and from removing explanations of basic concepts like search intent types and what constitutes good anchor text.
Suggestions
Cut the content by 60-70%: remove explanations of basic SEO concepts (search intent, anchor text best practices, what pillar pages are), the 'Common Trigger Phrases' section, the 'Philosophy' section, and the 'Best Practices' section — Claude already knows these things.
Extract the detailed output template, content calendar template, and common clustering patterns into separate referenced files to improve progressive disclosure and reduce the main file to an actionable overview.
Add validation checkpoints: include criteria for evaluating cluster quality (e.g., minimum keyword overlap threshold, intent consistency check) and a feedback loop for refining clusters that don't meet quality standards.
Replace placeholder-heavy templates with one fully worked-out end-to-end example using real keywords, showing the complete input-to-output transformation rather than generic '[keyword]' placeholders.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Explains basic SEO concepts Claude already knows (what a pillar page is, what search intent means, what anchor text is). Includes unnecessary sections like 'Common Trigger Phrases', 'Philosophy', and extensive explanations of basic concepts. The 'Best Practices' section tells Claude to 'be specific' and 'include examples' — generic advice that wastes tokens. | 1 / 3 |
Actionability | Provides templates and structural examples (markdown architecture diagrams, content calendar template, output formats), which are somewhat actionable. However, most content is placeholder-heavy (e.g., '[keyword]', '[Title]', '[Specific actionable step]') rather than truly executable. There's no code or concrete tooling — it's all conceptual guidance with template shells rather than copy-paste ready artifacts. | 2 / 3 |
Workflow Clarity | Steps 1-3 of the clustering process are reasonably sequenced, and the 'Example Workflow' section outlines a 7-step process. However, there are no validation checkpoints — no way to verify cluster quality, no feedback loops for when clustering doesn't work well, and no criteria for evaluating whether the output meets quality standards before delivering to the user. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Everything is inlined — the detailed output template, content calendar, linking guidelines, success metrics, and common patterns could all be separate reference files. With no bundle files provided, this massive single document fails to organize content for efficient consumption. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
5e92b71
- 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.