Content
81%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A comprehensive, highly actionable SEO skill with excellent code examples, a validated audit workflow, and a clearly signaled reference split for structured data. Its main weakness is conciseness: extensive guideline bullets restate well-known SEO basics and much detailed content remains inline rather than progressively disclosed.
Suggestions
Trim or collapse the per-section "guidelines" bullet lists that restate basics Claude already knows (e.g., "Use hyphens, not underscores", "Lowercase only", "Fix broken links promptly"), keeping only the non-obvious calibration notes.
Move the Mobile SEO and International SEO reference blocks into separate files under references/ and link to them from SKILL.md, mirroring the existing STRUCTURED-DATA.md split, to reduce inline bulk.
Consider consolidating the near-identical title/meta-description "linting proxy" caveats into one statement rather than repeating the framing in each section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with high-value calibrated nuance (title-link rewriting, llms.txt cautions), but the repeated guidelines bullet lists restate SEO basics Claude already knows ("Use hyphens, not underscores", "Lowercase only", "Fix broken links promptly") and the body is long enough to tighten. | 3 / 5 |
Actionability | Copious copy-paste-ready examples (robots.txt, meta robots, canonical, sitemap XML, title/meta/heading/image/link markup, hreflang, viewport, CSS) plus concrete tool invocations (Chrome DevTools MCP `lighthouse_audit`, Lighthouse CLI) cover the common SEO cases fully. | 5 / 5 |
Workflow Clarity | The "Evidence-led audit workflow" is a clearly sequenced four-step process with explicit validation ("Fix the source and re-run the same checks") and a feedback loop, and the SEO audit checklist reinforces the sequence with prioritized checkpoints. | 5 / 5 |
Progressive Disclosure | Structure is good and the one bundle file is well-signaled ("Read [the structured data reference](references/STRUCTURED-DATA.md) when...") at one level deep, but a large amount of technical/on-page/mobile/international detail is inlined in SKILL.md rather than split into further reference files. | 4 / 5 |
Total | 17 / 20 Passed |