CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

A thorough, highly actionable SEO reference with strong executable examples and a clear audit checklist. Its weaknesses are length/time-sensitive hedging that hurts conciseness and a monolithic structure with no bundle files to offload the extensive catalogs.

Suggestions

Move the full JSON-LD and sitemap XML catalogs into a references/ file (e.g. STRUCTURED-DATA.md) and keep SKILL.md as an overview with one-level-deep links, improving progressive disclosure and conciseness.

Relocate the dated AI-search adoption figures into a clearly marked 'emerging / time-sensitive' subsection so stale specifics do not penalize conciseness.

Trim redundant boilerplate comments inside code blocks where the surrounding guideline list already covers the same advice.

DimensionReasoningScore

Conciseness

The body is mostly lean and example-driven, but it runs long with full inline JSON-LD/sitemap catalogs and includes time-sensitive hedging ("As of 2026 ...", "As of mid-2026 adoption is ~0.015%") that could be tightened or moved to a dated section.

2 / 3

Actionability

It provides copy-paste-ready code for robots.txt, meta robots, canonicals, sitemap XML, title/meta tags, and five JSON-LD schemas, plus concrete guidelines lists and an audit checklist.

3 / 3

Workflow Clarity

Though primarily a pattern catalog, the prioritized "SEO audit checklist" (Critical -> High -> Medium -> Ongoing) with validation links (Rich Results Test, Schema.org Validator, Search Console) supplies clear sequencing and verification; no destructive batch operation triggers the cap.

3 / 3

Progressive Disclosure

There are no bundle files (references/scripts/assets) and all content lives in one ~528-line SKILL.md; the large structured-data/sitemap catalogs are inline rather than split into one-level-deep reference files, and the only cross-links point to sibling skills outside the bundle.

2 / 3

Total

10

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-targeted description with explicit what-and-when structure and natural trigger phrases. Its only weakness is that the capability statement stays general rather than listing the specific concrete actions the skill performs.

Suggestions

Expand the capability clause to name concrete actions, e.g. "Configure robots.txt and sitemaps, set meta tags and canonical URLs, and add JSON-LD structured data."

DimensionReasoningScore

Specificity

The phrase "Optimize for search engine visibility and ranking" names the domain and a general action but does not enumerate concrete actions (e.g. configure robots.txt, add JSON-LD, set canonicals), matching the 'names domain and some actions' anchor rather than the multi-action level 3.

2 / 3

Completeness

It explicitly states what ("Optimize for search engine visibility and ranking") and when ("Use when asked to ...") with concrete trigger phrases, satisfying both halves.

3 / 3

Trigger Term Quality

Triggers like "improve SEO", "fix meta tags", "add structured data", and "sitemap optimization" are natural phrases a user would say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The SEO niche is clear with distinct trigger terms unlikely to fire for sibling skills (e.g. core-web-vitals, web-quality-audit) that address different concerns.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (528 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

14

/

16

Passed

Repository
addyosmani/web-quality-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.