CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

invalid-links

Use when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use `<a href>` tags, or checking that dynamically generated links have valid href values.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/invalid-links/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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, highly actionable skill body: precise detection criteria, concrete before/after fix examples, and exemplary progressive disclosure with one clearly signaled reference file. The weaknesses are redundancy — the crawlability rationale is repeated across three sections — and the absence of an explicit post-fix verification loop for what is effectively a batch edit operation.

Suggestions

Merge the Quick Reference bullets and the Explain section into one statement of the crawlability rationale; the intro already states it, so two of the three repetitions can be cut.

Add an explicit validation step after Fix, e.g., 'Re-run the Check on the modified DOM and confirm zero flagged links before reporting', turning Code Review into a true fix-verification pass rather than a restatement of the Check criteria.

Reconcile the Check and Code Review flag lists (mailto:/tel: and dangling fragments appear only in Check) so the two passes apply consistent criteria.

DimensionReasoningScore

Conciseness

The core fact (invalid <a href> links are not crawlable by Googlebot) is restated three times — in the intro, the Quick Reference bullets, and the Explain section — so those sections could be collapsed. Otherwise the body is lean with no filler or explanations of basic concepts, keeping it above anchor 2.

3 / 5

Actionability

The Check section enumerates five precise, concrete flag conditions (empty href, javascript:, mailto:/tel:, dangling fragment, absent href) and the Fix section provides copy-paste-ready before/after HTML covering the common cases. As an instruction-only skill, the guidance is fully actionable with specific examples.

5 / 5

Workflow Clarity

A rough Check → Fix → Explain → Code Review sequence is present, but validation is implicit: there is no 're-run the check after fixing' feedback loop, and the Code Review section largely restates the Check criteria (minus mailto/tel and fragments) instead of serving as a distinct post-fix verification step. For a batch operation (fixing many links per page), the missing explicit verification caps this at 3.

3 / 5

Progressive Disclosure

The body is a compact 43-line overview with well-organized sections, and implementation details (code examples, framework-specific guidance) are appropriately split into a single one-level-deep reference, clearly signaled: 'For full implementation details… see references/rule.md' (verified the file exists and matches). Navigation is easy with no nesting.

5 / 5

Total

16

/

20

Passed

Description

75%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 well-crafted trigger-focused description with three specific, natural use scenarios and a distinct niche. Its main weakness is that the capability ('what') is only implied inside the 'Use when' clauses and the audit scope omits the fix side of the skill, plus a few obvious synonyms (SEO, broken links) are absent.

DimensionReasoningScore

Specificity

Names three concrete actions — 'auditing a page's link elements for crawlability', 'reviewing JavaScript-heavy SPAs', 'checking that dynamically generated links have valid href values' — each tied to specific objects. Not 5 because coverage is audit-only; fixing/repairing invalid links is never mentioned, leaving a minor gap.

4 / 5

Completeness

The 'when' is explicit and strong via three 'Use when…' trigger scenarios, and the 'what' (auditing/checking link crawlability) is stated, but it is embedded inside the when-clauses rather than a standalone capability statement. Matches anchor 4 ('when' present, 'what' could be more explicit); not 3 because both elements are clearly present.

4 / 5

Trigger Term Quality

Includes natural terms users would say: 'crawlability', 'link elements', 'href', 'SPAs', 'navigation', 'dynamically generated links'. A few common variations are missing — e.g., 'SEO', 'broken links', 'anchor tags' — which keeps it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (crawlable-link validity, SPA navigation without <a href>) with distinct triggers and minimal conflict risk. Not 5 because it could mildly overlap with closely related link-audit or general SEO skills whose descriptions also mention links and crawling.

4 / 5

Total

16

/

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

thedaviddias/Front-End-Checklist

Path

skills/invalid-links/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.