CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

80%

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

68%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.

The content is well-structured, concise, and actionable with concrete thresholds and templates, but lacks explicit validation/feedback-loops in its workflows, capping workflow clarity. It is appropriately self-contained for a skill of this scope.

Suggestions

Add an explicit validation/checkpoint step to the audit and keyword-mapping workflows (e.g., verify the recommended fix against the real page before reporting) to lift workflow clarity above 3.

Tighten principle rationales such as the mobile-first explanation to remove explanation Claude already knows.

Provide one or two concrete executable commands or tool invocations for common audit tasks (e.g., a curl/robots.txt check or a structured-data validation step) to strengthen actionability.

DimensionReasoningScore

Conciseness

The body is mostly lean checklists and concrete thresholds without explaining basic SEO concepts, but a few principle rationales (e.g. "Mobile-first assumptions matter because indexing is mobile-first") edge slightly toward over-explanation that could be trimmed.

4 / 5

Actionability

Provides concrete, actionable guidance (LCP < 2.5s, INP < 200ms, CLS < 0.1, title 50-60 chars, meta 120-160 chars, JSON-LD template, audit output shape), but as an instruction-only skill it offers few fully executable commands beyond the JSON-LD example.

4 / 5

Workflow Clarity

Keyword mapping is a clear 5-step sequence and checklists are well ordered, but there are no explicit validation checkpoints or feedback loops in the audit or mapping process, matching the anchor with sequence present but checkpoints missing or implicit.

3 / 5

Progressive Disclosure

The skill is self-contained with well-organized sections (When to Use, How It Works, Examples, Anti-Patterns, Related Skills) and no external bundle files; the structure is good though the inlined example templates make it slightly longer than a pure overview.

4 / 5

Total

15

/

20

Passed

Description

92%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.

The description is specific, trigger-rich, and clearly answers both what the skill does and when to use it, with a well-scoped SEO niche and low conflict risk. It is only slightly shy of full trigger-term coverage due to a few missing natural synonyms.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("Audit, plan, and implement SEO improvements") across five enumerated sub-domains (technical SEO, on-page optimization, structured data, Core Web Vitals, content strategy), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly states what the skill does (audit/plan/implement across five SEO areas) and provides a concrete "Use when the user wants..." trigger clause, satisfying both what and when.

5 / 5

Trigger Term Quality

Includes natural user phrases like "better search visibility", "SEO remediation", "schema markup", "sitemap/robots work", and "keyword mapping", but is missing a few common synonyms such as "ranking" or "Google results".

4 / 5

Distinctiveness Conflict Risk

Occupies a clear SEO-specific niche with distinct triggers (schema markup, sitemap/robots, keyword mapping) and minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.