seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization". Do NOT use for accessibility (use web-accessibility), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/skills-catalog/skills/(quality)/seo/SKILL.mdQuality
Discovery
89%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 with excellent trigger term coverage and outstanding completeness, including both positive triggers and explicit negative boundaries with other skills. The main weakness is that the core capability statement could be more specific about concrete actions the skill performs beyond the high-level 'optimize for search engine visibility and ranking'. The 'Do NOT use' clause is a notable strength that significantly reduces conflict risk.
Suggestions
Expand the opening capability statement to list more concrete actions, e.g., 'Analyzes and improves meta tags, heading structure, structured data markup, sitemaps, canonical URLs, and keyword usage for search engine visibility and ranking.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (SEO) and mentions some actions like 'fix meta tags', 'add structured data', 'sitemap optimization', but the primary capability statement 'Optimize for search engine visibility and ranking' is fairly high-level and doesn't list multiple concrete actions the skill performs. | 2 / 3 |
Completeness | Clearly answers both 'what' (optimize for search engine visibility and ranking) and 'when' (explicit 'Use when' clause with multiple trigger phrases). Additionally includes helpful 'Do NOT use' guidance to disambiguate from related skills. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'improve SEO', 'optimize for search', 'fix meta tags', 'add structured data', 'sitemap optimization', 'search engine optimization'. These are phrases users would naturally say when requesting SEO help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-setting via 'Do NOT use' clauses that differentiate it from web-accessibility, core-web-vitals, and web-quality-audit skills. The SEO-specific trigger terms create a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with excellent concrete examples and good/bad comparisons, but it's far too verbose and monolithic for a SKILL.md file. It reads more like a comprehensive SEO reference guide than a concise skill instruction — most of this content (basic HTML best practices, what good URLs look like, font sizing) is knowledge Claude already possesses. The content would benefit enormously from being condensed to key decision points and non-obvious guidance, with detailed examples split into referenced sub-files.
Suggestions
Drastically reduce content to only what Claude doesn't already know — remove basic HTML/CSS guidance (viewport tags, font sizes, heading hierarchy) and focus on project-specific decision logic and non-obvious patterns.
Split structured data examples, mobile SEO, and international SEO into separate reference files (e.g., STRUCTURED-DATA.md, MOBILE-SEO.md) and link to them from a concise overview.
Add an explicit workflow for performing an SEO audit: step 1 run Lighthouse, step 2 check specific issues, step 3 validate fixes, with clear validation checkpoints before moving on.
Convert the audit checklist into the primary workflow structure of the skill, making it the organizing principle rather than an appendix.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is extremely verbose at ~400+ lines. It explains basic concepts Claude already knows (what good URLs look like, what meta descriptions are, basic HTML viewport tags, font sizing). The ranking factors table, extensive guidelines lists, and exhaustive structured data examples for every schema type bloat the content significantly. Much of this is reference material Claude already has knowledge of. | 1 / 3 |
Actionability | The skill provides fully concrete, copy-paste ready code examples throughout — complete HTML snippets, robots.txt configurations, XML sitemaps, JSON-LD structured data, CSS examples, and clear good/bad comparisons. Every section has executable, specific guidance. | 3 / 3 |
Workflow Clarity | The audit checklist at the end provides a prioritized sequence (Critical → High → Medium → Ongoing), but there's no explicit workflow for performing an SEO optimization task — no step-by-step process with validation checkpoints. The structured data section mentions validation tools but doesn't integrate them into a verify-then-proceed workflow. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with everything inline. The extensive structured data examples (Organization, Article, Product, FAQ, Breadcrumbs) and the full mobile SEO and international SEO sections should be split into separate reference files. Only two cross-references exist (Core Web Vitals, Web Quality Audit) and they're at the bottom rather than used to offload content. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (533 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- tech-leads-club/agent-skills
- Commit
81e7e0d
- 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.