CtrlK
BlogDocsLog inGet started
Tessl Logo

html-resource-hints

Use when reviewing templates, rendered HTML, or shared components related to Add resource hints (preload, prefetch, dns-prefetch). Validate the final browser-facing markup, not just the source framework abstraction.

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/html-resource-hints/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The skill is well-structured with a clean overview and a well-signaled single reference file, but the body explains concepts Claude already knows and offers direction rather than inline executable guidance with validation. It is a competent but not maximally tight or action-ready review skill.

Suggestions

Trim the intro paragraph and Quick Reference definitions of preload/prefetch/dns-prefetch/preconnect, since Claude already knows these; keep only the non-obvious motivation or move it to references/rule.md.

Add one inline executable example (e.g., a <link rel="preload" ...> snippet) to the Fix section so guidance is copy-paste ready rather than delegated entirely to the reference.

Add a verification checkpoint to the workflow (e.g., 'Confirm the preload request appears in the Network tab / Lighthouse audit before finishing') to lift workflow clarity above the steps-without-validation level.

DimensionReasoningScore

Conciseness

The body is reasonably lean, but the intro paragraph ('The browser's HTML parser discovers resources sequentially — a font referenced in a CSS file won't be fetched until the CSS is parsed') and Quick Reference restate browser-parsing/hint concepts Claude already knows, so it is mostly efficient rather than fully lean.

2 / 3

Actionability

Check/Fix/Code Review give concrete direction ('fonts referenced in CSS, hero images, and key scripts', 'Add preconnect for third-party domains'), but there is no inline executable code and 'Add appropriate preload hints' is somewhat loose; specifics are delegated to references/rule.md, fitting the 'some concrete guidance but incomplete' anchor.

2 / 3

Workflow Clarity

The Check/Fix/Explain/Code Review sections provide a loose sequence, but they read as parallel modes rather than a tightly sequenced workflow and there are no validation checkpoints (e.g., verifying the hint fires in the Network tab), matching the 'steps listed but validation gaps' anchor.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview that clearly signals a one-level-deep pointer ('see references/rule.md') for full implementation details and code examples, and the referenced file exists, matching the clear-overview anchor; it is not the monolithic or deeply-nested level below.

3 / 3

Total

9

/

12

Passed

Description

90%

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 an explicit 'Use when' trigger, strong natural trigger terms, and a distinctive narrow niche, with only minor weakness in action breadth. It is third-person/imperative in voice with no first- or second-person phrasing.

DimensionReasoningScore

Specificity

Quotes 'reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup' name the domain and concrete actions, but only two verbs (review, validate) are present rather than a comprehensive set, matching the 'names domain and some actions' anchor.

2 / 3

Completeness

Explicit 'Use when reviewing templates, rendered HTML, or shared components' answers when, and 'Validate the final browser-facing markup, not just the source framework abstraction' answers what, satisfying the explicit-trigger anchor; the missing-'Use when' cap at 2 does not apply.

3 / 3

Trigger Term Quality

Includes natural terms a frontend user would say — 'preload, prefetch, dns-prefetch', 'rendered HTML', 'templates', 'shared components', 'markup' — giving good coverage rather than the missing-variations level below.

3 / 3

Distinctiveness Conflict Risk

The narrow niche 'Add resource hints (preload, prefetch, dns-prefetch)' with distinct, specific triggers is unlikely to overlap with sibling skills, matching the clear-niche anchor.

3 / 3

Total

11

/

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.