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.
74
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/seo-optimizer/skills/seo-optimizer/SKILL.mdQuality
Discovery
100%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 concisely covers specific capabilities, includes natural trigger terms users would employ, and clearly delineates both what the skill does and when to use it. The SEO domain is well-defined with distinctive terminology that minimizes conflict risk with other skills. The description uses appropriate third-person voice and avoids vague fluff.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: keyword analysis, readability assessment, technical validation, content quality. These are distinct, identifiable capabilities rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what (SEO optimization with keyword analysis, readability assessment, technical validation, content quality) and when ('Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'search rankings', 'blog posts', 'content audits', 'keyword density', 'readability scores', 'meta tags', 'schema markup'. These cover a good range of terms a user working on SEO would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | SEO optimization is a clear niche with distinct triggers like 'keyword density', 'meta tags', 'schema markup', and 'readability scores' that are unlikely to conflict with general content writing or web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is comprehensive in coverage but suffers significantly from verbosity — it explains many standard SEO concepts that Claude already understands, inflating the token cost without adding proportional value. The actionability is moderate: it provides useful checklists and target ranges but lacks truly executable code or concrete tool-based workflows. The structure would benefit from moving detailed content into reference files and keeping the main skill lean.
Suggestions
Cut 50-60% of the content by removing explanations of concepts Claude already knows (what E-A-T is, what meta descriptions are, basic SEO philosophy) and focus only on the specific workflow, target metrics, and output format.
Move the full report template and detailed technical SEO table into the referenced files (references/output-templates.md and references/analysis-framework.md) to keep SKILL.md as a concise overview.
Replace the illustrative JavaScript object with either a concrete calculation formula or remove it entirely — a static object literal showing example values adds no actionable guidance.
Add explicit validation/feedback loops to the analysis flow, e.g., 'If keyword density exceeds 2%, identify and remove forced keyword insertions, then recalculate' to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~180+ lines, explaining many concepts Claude already knows (what E-A-T is, what meta descriptions are, what readability scores mean, basic SEO philosophy). The 'Core Philosophy' quote and extensive explanations of standard SEO concepts waste tokens. Much of this is general SEO knowledge that doesn't need to be taught. | 1 / 3 |
Actionability | The skill provides structured checklists, target ranges, and a report template, which is somewhat concrete. However, the JavaScript code example is illustrative rather than executable (just a static object literal), there are no real executable tools or commands, and much guidance remains at the level of 'check X' rather than showing exactly how to compute or implement it. | 2 / 3 |
Workflow Clarity | The 'Example Analysis Flow' provides a 9-step sequence, and priority levels are clearly defined. However, there are no validation checkpoints or feedback loops — no step says 'verify your density calculation is correct' or 'if readability score is below threshold, iterate on these specific changes.' For a multi-step analytical process, the lack of explicit verification steps is a gap. | 2 / 3 |
Progressive Disclosure | The skill references two external files (references/analysis-framework.md and references/output-templates.md) with clear descriptions, which is good. However, the main file itself contains a massive amount of inline content (the full report template, detailed tables, extensive best practices) that should arguably be in those reference files, making the SKILL.md itself bloated rather than serving as a concise overview. | 2 / 3 |
Total | 7 / 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
88da5ff
- 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.