CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo

Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.

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

76%Weight 40%Scale 1-5

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

A tight, well-structured skill body with excellent token efficiency and mostly concrete guidance. The main gap is workflow: there is no explicit audit-to-fix sequence with validation checkpoints (e.g., validate structured data after adding it, re-measure Core Web Vitals after performance fixes).

Suggestions

Add an explicit end-to-end workflow section (e.g., crawl/inspect -> diagnose -> fix technical blockers -> validate -> move to content), with validation checkpoints such as re-running a CWV measurement after performance fixes and validating JSON-LD with a schema validator after adding structured data.

Include concrete tool commands for the audit phase (e.g., Lighthouse or PageSpeed Insights invocation for Core Web Vitals, a structured-data validator for schema markup) so the audit output is directly executable.

Move per-page-type structured-data templates into a one-level-deep reference file (e.g., references/schema-templates.md) to keep SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

The body is lean checklist-style guidance with no concept explanations Claude already knows — every line states a rule, threshold, or format (e.g., "LCP < 2.5s", "aim for roughly 50-60 characters", "one clear H1"). It matches the 5 anchor 'every token earns its place'; there is no padded prose that would justify a 4.

5 / 5

Actionability

Concrete, specific guidance throughout: numeric CWV thresholds ("INP < 200ms"), title/meta character ranges, a title formula, a JSON-LD example, and an audit output format with location/issue/fix. It stops short of 5 because there are no executable commands or tool invocations (e.g., Lighthouse, PageSpeed Insights, Rich Results Test) for actually performing the audit or validation.

4 / 5

Workflow Clarity

Sequencing exists in fragments ("Fix technical blockers before content optimization", the numbered keyword-mapping process) but there is no end-to-end audit-to-fix workflow, and validation checkpoints are absent — no step to re-verify CWV after fixes or validate structured data after adding it. This matches the 3 anchor 'sequence present but checkpoints missing'.

3 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clear sections (checklists, on-page rules, examples, anti-patterns table) with no bundle files and no nested references, so nothing is buried. It stays at 4 rather than 5 because at ~150 lines the structured-data templates and per-page-type examples could live in one-level-deep reference files, and the under-50-line exception in the guidelines does not apply.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

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 strong description with third-person voice, an explicit 'Use when' trigger clause, and good domain enumeration. Minor improvements possible: more specific action verbs and additional natural synonyms like 'search ranking' or 'rank higher on Google'.

DimensionReasoningScore

Specificity

The description lists several concrete action verbs ("Audit, plan, and implement") across five named subdomains ("technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy"), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the verbs themselves are generic compared to the fully enumerated action list in the top anchor, and it is clearly above the 3 anchor (only 1-2 concrete actions).

4 / 5

Completeness

It explicitly answers both questions: 'what' via "Audit, plan, and implement SEO improvements across..." and 'when' via an explicit "Use when the user wants..." clause with concrete trigger phrases. This matches the 5 anchor exactly; the 4 anchor's 'when could be more explicit' caveat does not apply since the triggers are concrete and specific.

5 / 5

Trigger Term Quality

The 'Use when' clause surfaces good natural keywords users would say: "better search visibility", "SEO remediation", "schema markup", "sitemap/robots work", "keyword mapping". It sits at 4 rather than 5 because common synonyms like 'rank higher on Google', 'search ranking', or 'meta tags' are missing.

4 / 5

Distinctiveness Conflict Risk

SEO is a clear niche with distinct triggers, but phrases like "Core Web Vitals" and "content strategy" create minor overlap risk with performance-tuning and content-writing skills. Mostly distinct with minor overlap — the 4 anchor; it does not reach 5's 'minimal conflict risk' given the breadth of subdomains.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/seo/SKILL.md

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.