seo-optimizer

SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/seo-optimizer/skills/seo-optimizer/SKILL.md

Quality

Content

57%

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

The body is well-structured with specific numeric targets, a report template, and clean progressive disclosure to two real reference files. Its main gaps are redundancy across overlapping sections, a non-executable code sample with unfulfilled before/after examples, and the absence of validation checkpoints in the workflow.

Suggestions

Consolidate the overlapping 'Best Practices', 'Output Guidelines', and 'Core Philosophy' sections to remove redundancy and recover tokens.

Provide at least one concrete before/after example (e.g., a weak vs. optimized meta title and description) to fulfill the Output Guidelines promise and raise actionability.

Add an explicit verification step to the analysis flow (e.g., re-check keyword density and heading hierarchy after proposed edits) so the workflow includes a validation checkpoint.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient with specific numeric targets rather than explaining concepts Claude already knows, but 'Best Practices', 'Output Guidelines', 'Analysis Report Structure', and 'Example Analysis Flow' overlap noticeably and the 'Core Philosophy' quote is padding; it could be tightened to the top level.	2 / 3
Actionability	Concrete numeric targets (density 1-2%, meta title 50-60 chars, Flesch 60-70, grade 7-9, sentence <20, word count 1500+) and a copy-paste report template are strong, but the readability code block is a static data object rather than executable logic and 'Show before/after examples' is promised in Output Guidelines yet none are actually provided.	2 / 3
Workflow Clarity	A clear 9-step 'Example Analysis Flow' with an implementation checklist and priority framework is sequenced well, but there are no explicit validation checkpoints or feedback loops in the analysis process, leaving it at the sequence-present-but-checkpoints-implicit level.	2 / 3
Progressive Disclosure	The body offers a clear overview and points to two real, well-signaled one-level-deep references (references/analysis-framework.md and references/output-templates.md) with bulleted descriptions of their contents, matching the clear-navigation anchor.	3 / 3
	Total	9 / 12 Passed

Description

90%

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 strong: third-person voice, explicit 'Use for' trigger guidance, and good coverage of natural trigger terms tied to a clear SEO niche. Its only weakness is the mixed-concreteness capability list, where 'content quality' and weak verb forms keep specificity from the top level.

Suggestions

Replace the vague 'content quality' with a concrete action (e.g., 'content quality scoring') and use strong verbs (e.g., 'Analyzes keywords, scores readability, validates technical SEO, audits content quality').

Add a couple of common natural variations users say (e.g., 'on-page SEO', 'SERP rankings', 'meta descriptions') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names concrete SEO analysis areas ('keyword analysis, readability assessment, technical validation') but appends the vague noun phrase 'content quality' and uses weak verb forms rather than discrete concrete operations, so it falls short of the fully concrete anchor.	2 / 3
Completeness	Explicitly answers both what ('SEO optimization with keyword analysis, readability assessment, technical validation, content quality') and when via a 'Use for...' clause, matching the top anchor.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered: 'search rankings, blog posts, content audits' plus 'keyword density, readability scores, meta tags, schema markup errors' that a user would actually mention.	3 / 3
Distinctiveness Conflict Risk	SEO-specific triggers (keyword density, meta tags, schema markup, readability scores) define a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Commit: c4889f6

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.