CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

53

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/seo-keyword-cluster-builder/skills/seo-keyword-cluster-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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.

The body is comprehensive and well-sectioned but bloated: it over-explains fundamentals and inlines templates/patterns that would be better split into reference files. Workflows have sequence but lack validation checkpoints, and templates lean on placeholders rather than worked examples.

Suggestions

Trim sections that restate SEO fundamentals Claude already knows (search intent definitions, internal-linking basics) to roughly halve the token budget.

Move the detailed output templates, clustering patterns, and KPI lists into separate reference files under ./references/ and link to them one level deep from SKILL.md.

Add explicit validation/feedback steps to the clustering workflow (e.g., verify cluster coherence and check for orphan keywords before finalizing the architecture) and replace placeholder templates with at least one fully worked end-to-end example.

DimensionReasoningScore

Conciseness

At ~470 lines the body is noticeably verbose, restating basics Claude already knows (search intent, internal-linking fundamentals) and duplicating templates/patterns across multiple sections.

2 / 5

Actionability

Provides concrete templates, tree diagrams, and word-count guidance, but most templates are placeholder-heavy ('[keyword]', '[title]') and lack fully worked examples for the common cases.

3 / 5

Workflow Clarity

Sequenced steps appear in 'Response Approach' and 'Example Workflow', but validation checkpoints and error-feedback loops are absent, leaving the sequence implicit rather than gated.

3 / 5

Progressive Disclosure

Section headers give reasonable structure, but the skill is a single monolithic file with no bundle references; content that belongs in separate files (templates, patterns, KPI lists) is inlined.

3 / 5

Total

11

/

20

Passed

Description

75%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.

The description is well-constructed: third person, concrete actions, an explicit 'Use for' trigger clause, and a clear SEO niche. It is just short of the top anchor because the trigger phrases lean slightly technical and a few natural synonyms are absent.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'keyword clustering', 'topic organization', 'content hub architecture', 'internal linking strategies' — giving clear capability coverage with only minor gaps.

4 / 5

Completeness

Explicitly states what it does and provides a 'Use for...' when-clause with concrete triggers, though the trigger list could be slightly more specific.

4 / 5

Trigger Term Quality

Includes natural terms a user would say ('keyword research', 'content strategy', 'pillar page structures', 'internal linking'); a few synonyms like 'topic clusters'/'SEO' variations are thin but coverage is good.

4 / 5

Distinctiveness Conflict Risk

Scoped to SEO content architecture with distinct triggers (pillar pages, hub architecture); minor overlap risk with broad 'content strategy' skills but largely distinct.

4 / 5

Total

16

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
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.