CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

73%

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 ./skills/invalid-links/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is concise and well-structured with clean progressive disclosure to a real reference file, but it leans on prose over executable code and lacks a validation feedback loop for a batch audit task.

Suggestions

Convert the Check/Code Review prose into copy-paste executable snippets (e.g., a querySelectorAll selector set or a small script) to raise actionability.

Add an explicit verify-and-re-run step after applying fixes so the audit workflow includes a validation feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no padding about what HTML, SEO, or crawlers are; every section earns its place.

3 / 3

Actionability

It includes concrete before/after HTML snippets and a real DevTools query, but the Check, Fix, and Code Review sections are prose descriptions rather than copy-paste executable code, with most runnable examples living only in the reference file.

2 / 3

Workflow Clarity

A Check→Fix→Explain→Code Review sequence is present, but this batch audit operation has no explicit validation or re-verify feedback loop, which caps workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

The body is a concise overview with a single, clearly signaled one-level-deep reference to references/rule.md, which is a real file, providing easy navigation.

3 / 3

Total

10

/

12

Passed

Description

75%

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 has a clear explicit trigger and a distinct SEO crawlability niche, but its action list is narrow and it misses several natural keyword variations a user would say.

Suggestions

Broaden the action list beyond a single audit task (e.g., add reporting and fixing) to lift specificity.

Add common natural-language trigger terms such as "broken links" or "SEO links" to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and several actions ("auditing a page's link elements for crawlability", "reviewing JavaScript-heavy SPAs", "checking that dynamically generated links have valid href values") but these are variations of one audit task rather than a comprehensive list of distinct concrete actions.

2 / 3

Completeness

It explicitly answers what the skill does and includes an explicit "Use when..." trigger clause covering multiple scenarios, satisfying both the what and the when.

3 / 3

Trigger Term Quality

Relevant terms like "link elements", "crawlability", "SPAs", and "href" appear, but it omits natural variations a user might say such as "broken links", "SEO links", or "Googlebot can't follow links".

2 / 3

Distinctiveness Conflict Risk

The crawlable-link/SEO niche with SPA-specific framing is clearly distinct and unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

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
thedaviddias/Front-End-Checklist
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.