CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

technical-seo-checker

Use when the user asks to "technical SEO audit", "check page speed", "crawl issues", "Core Web Vitals", "site indexing problems", "my site is slow", "Google cannot crawl my site", "mobile issues", or "indexing problems". Performs technical SEO audits covering site speed, crawlability, indexability, mobile-friendliness, security, and structured data. Identifies technical issues preventing optimal search performance. For content and heading element issues, see on-page-seo-auditor. For link architecture, see internal-linking-optimizer.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

62%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 body delivers a well-sequenced, highly actionable audit workflow with explicit validation checklists and concrete report templates. However, it is roughly three times longer than it needs to be: the worked example, checklist, severity framework, and CWV quick-reference duplicate or extend content that belongs in the existing references/ bundle, and several sections (skill catalog, Tips for Success) are pure padding.

Suggestions

Move the Technical SEO Checklist, the Severity Framework / Prioritization Matrix, and the Core Web Vitals Optimization Quick Reference into new files under references/ (e.g. references/severity-framework.md, references/cwv-optimization.md), leaving SKILL.md as the workflow plus one canonical set of report templates.

Trim the worked Example to a short excerpt (the Overall Health score plus one critical issue) — the full ~100-line example largely duplicates the templates in the Instructions section.

Delete the generic "Tips for Success" section and the 20-skill catalog details block; the frontmatter description already handles skill-boundary routing, and the Related Skills section already links siblings.

DimensionReasoningScore

Conciseness

The body runs ~750 lines with several padded/duplicated sections: a 20-skill catalog in a details block, a generic "Tips for Success" list ("Document everything", "Regular audits"), a Technical SEO Checklist that restates the audit templates, and a full worked Example that largely repeats the preceding 350 lines of output templates. This is noticeably verbose — much of it should live in the two existing reference files — though it does not explain concepts Claude already knows, so it stays above level 1.

2 / 5

Actionability

Guidance is highly concrete: exact report templates with table schemas, explicit thresholds (LCP <2.5s, INP <200ms), root-cause→detection→fix tables, and a worked example with real numbers ("Uncompressed hero image (2.4MB PNG): Convert to WebP, est. save 1.9MB"). Minor gaps — the ~~web crawler / ~~page speed tool connectors are placeholders rather than named tools — keep it just below the fully-executable level 5.

4 / 5

Workflow Clarity

The Instructions section sequences nine numbered audit steps culminating in report generation, and a dedicated "Validation Checkpoints" section provides explicit input and output checklists ("Every recommendation cites specific data points", "All issues include affected URLs or page counts"). This matches the anchor for clear sequence with explicit validation steps and checklists; the audit is read-only, so destructive-operation feedback loops are not required.

5 / 5

Progressive Disclosure

The two references (robots-txt-reference.md, http-status-codes.md) exist, are one level deep, and are clearly signaled with descriptions — but they cover only a sliver of the material. The checklist, severity framework, prioritization matrix, CWV optimization tables, and the full worked example are all inlined in SKILL.md when they clearly belong in separate reference files, matching the anchor for content that should be separate sitting inline. The ../../CONNECTORS.md link also points outside the bundle and is unverifiable from within it.

3 / 5

Total

14

/

20

Passed

Description

95%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: explicit use-when triggers with natural synonyms and lay phrasing, a clear third-person statement of what the skill does, and explicit boundary guidance to sibling skills. The only weakness is that the capability enumeration is slightly less granular than the body's actual coverage (URL structure, international SEO, redirects are omitted).

DimensionReasoningScore

Specificity

"Performs technical SEO audits covering site speed, crawlability, indexability, mobile-friendliness, security, and structured data" lists six concrete audit areas, matching the anchor for several specific actions with minor gaps. It enumerates coverage domains rather than fully distinct concrete actions (no mention of URL structure or international SEO, which the body actually covers), so it does not reach the comprehensive level 5.

4 / 5

Completeness

It explicitly answers both questions: the trigger list gives concrete "when" phrases ("Use when the user asks to...") and "Performs technical SEO audits covering..." plus "Identifies technical issues preventing optimal search performance" gives the "what". This matches the anchor where both what and when are explicit with concrete trigger phrases.

5 / 5

Trigger Term Quality

The quoted trigger list — "technical SEO audit", "check page speed", "crawl issues", "Core Web Vitals", "site indexing problems", "my site is slow", "Google cannot crawl my site", "mobile issues", "indexing problems" — is comprehensive natural phrasing including lay-user expressions ("my site is slow") and synonyms (crawl issues / indexing problems), which is exactly the level-5 anchor.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (technical SEO, not content) and explicitly deflects adjacent domains: "For content and heading element issues, see on-page-seo-auditor. For link architecture, see internal-linking-optimizer." Trigger terms are technical-SEO-specific, so conflict risk is minimal — the level-5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 27 suspicious

Warning

Total

13

/

16

Passed

Repository

teeclaw/phorm-nft

Path

.agents/skills/technical-seo-checker/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.