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.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A well-organized, token-efficient instruction skill with concrete templates, thresholds, and a structured audit-output shape. Its main gap is workflow clarity: the audit process lacks an explicit end-to-end sequence with validation checkpoints before recommendations are issued.

Suggestions

Add a numbered audit workflow (e.g., 1. crawl/index review → 2. on-page review → 3. structured-data check → 4. performance check → 5. emit page-specific findings) so the overall process is sequenced, not just keyword mapping.

Insert a validation checkpoint requiring the auditor to read the actual page/asset before emitting a finding, mirroring the anti-pattern 'content advice without checking the actual page'.

Gate the audit-output step on confirming each issue against the real source (Location path) before promoting it from a suspicion to a [HIGH]/[LOW] finding.

DimensionReasoningScore

Conciseness

The body is lean — tight checklists, specific thresholds (LCP < 2.5s, INP < 200ms, CLS < 0.1), and formula templates — with no padding explaining what SEO is or how search works, assuming Claude's competence throughout.

3 / 3

Actionability

For an instruction-only audit skill it gives concrete, copy-paste-ready artifacts: a JSON-LD block, title/meta formulas, character-count targets, per-page schema-type mapping, and a structured audit-output template with Location/Issue/Fix.

3 / 3

Workflow Clarity

Keyword mapping is a clear numbered sequence (define intent → gather variants → prioritize → map → avoid cannibalization), but the overall audit workflow has no explicit sequence or validation checkpoints confirming findings before recommending fixes.

2 / 3

Progressive Disclosure

The skill is self-contained with no bundle files and no external references, and is organized into clear, well-signaled sections (When to Use, How It Works, Examples, Anti-Patterns, Related Skills) with no nested reference chains.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person description that names concrete capabilities and provides an explicit, naturally-worded "Use when" trigger clause covering the main SEO request shapes. It is concise without fluff and clearly distinguishable from adjacent skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — "technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy" — paired with the concrete verbs "Audit, plan, and implement," matching the multiple-specific-actions anchor.

3 / 3

Completeness

It explicitly answers both what ("Audit, plan, and implement SEO improvements across...") and when ("Use when the user wants better search visibility..."), with an explicit trigger clause.

3 / 3

Trigger Term Quality

The "Use when" clause surfaces natural user phrasing — "better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping" — giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The SEO niche is clearly bounded by domain-specific triggers (schema markup, sitemap/robots, Core Web Vitals) that are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.