CtrlK
BlogDocsLog inGet started
Tessl Logo

technical-seo-checker

Technical SEO audit: Core Web Vitals, crawl, indexing, mobile, speed, architecture, redirects. 技术SEO/网站速度

62

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/technical-seo-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a well-structured, reference-backed audit skill with strong progressive disclosure and actionable templates, but the large inline fill-in templates and repeated boilerplate make it noticeably verbose rather than lean, and its validation checkpoints are output-shape checks rather than true feedback loops.

Suggestions

Move the big inline crawlability/indexability template blocks (Steps 1–2) into references/technical-audit-templates.md alongside Steps 3–9, leaving only a concise pointer and key checks inline to tighten conciseness toward level 5.

Replace or reduce the repeated cross-skill boilerplate (Skill Contract, State Model, Data Sources placeholders, library banner) that does not advance this specific audit, since it competes with context budget.

Add a true validate-then-fix feedback loop (e.g. 're-run the affected check after applying a fix and only proceed when the score improves') so workflow_clarity can reach level 5.

DimensionReasoningScore

Conciseness

The body is mostly task-focused but runs long: large inline fill-in template blocks for crawlability/indexability (roughly 100+ lines) plus repeated boilerplate around the Skill Contract, Data Sources, and multi-skill library banners add padding that could be trimmed or pushed to references; it is not severely verbose but noticeably above lean.

3 / 5

Actionability

It supplies concrete, copy-paste-ready markdown templates with check tables, status symbols, and exact robots.txt/sitemap fields for the common cases; minor gaps are that placeholders like [X]/[URL] require user/Claude to fill rather than fully executable commands, and some steps rely on manual data provision.

4 / 5

Workflow Clarity

Steps 1–9 are clearly sequenced and there are explicit Input/Output Validation Checkpoints with checkboxes, plus a Save Results handoff; however the validation is mostly output-shape checks rather than true validate-then-fix feedback loops, so it sits just below the level-5 explicit-feedback-loop anchor.

4 / 5

Progressive Disclosure

Excellent one-level-deep structure: SKILL.md keeps steps 1–2 inline and points each later step to references/technical-audit-templates.md, with a Reference Materials section listing four real, existing reference files (robots-txt-reference, http-status-codes, technical-audit-templates, technical-audit-example) and clear navigation; no nested/2+-level reference chains.

5 / 5

Total

16

/

20

Passed

Description

78%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, well-scoped, and clearly distinct, but it names audit categories rather than concrete actions and omits an explicit 'Use when...' trigger clause inside the description field itself (relegated to when_to_use). It is a strong but not maximal description.

Suggestions

Convert category nouns into concrete verbs in the description (e.g. 'Audits Core Web Vitals, crawlability, indexability, mobile-friendliness, site speed, URL architecture, and redirects') to reach the level-5 'multiple specific concrete actions' anchor.

Add an explicit 'Use when ...' clause directly inside the description field (currently only present in when_to_use) so completeness can score 5.

Include a couple of high-frequency user phrases/file references such as 'robots.txt' and 'sitemap.xml' to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete audit domains ('Core Web Vitals, crawl, indexing, mobile, speed, architecture, redirects') rather than vague actions, but these are nouns/categories rather than explicit actions the skill performs, leaving minor gaps versus the level-5 'multiple concrete actions' anchor.

4 / 5

Completeness

It clearly answers 'what' (technical SEO audit across listed dimensions), and a 'when' is implied by the audit-triggering domains, but the description field itself lacks an explicit 'Use when...' clause; explicit trigger guidance lives in the separate when_to_use field rather than the description, so it sits just below level 5.

4 / 5

Trigger Term Quality

Good natural-term coverage including 'Core Web Vitals', 'crawl', 'indexing', 'site speed' plus multilingual variants ('技术SEO', '网站速度'), but misses common synonyms and specific file extensions (e.g. 'robots.txt', 'sitemap.xml') that users frequently cite.

4 / 5

Distinctiveness Conflict Risk

The technical-SEO-infrastructure niche (Core Web Vitals, crawl, redirects, architecture) is clearly distinct from on-page/content SEO skills, with minimal overlap risk for the wrong skill triggering.

5 / 5

Total

17

/

20

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

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
MODSetter/SurfSense
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.