performance-resource-hints

Use when auditing slow page loads, heavy assets, or rendering delays related to Use resource hints for faster loading. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/performance-resource-hints/SKILL.md

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 body is a well-structured overview with excellent progressive disclosure to references/rule.md, but it relies on a templated Check/Fix/Explain/Code Review structure that is mildly redundant and defers all executable guidance to the reference file. Adding a brief inline example and an explicit measure-verify sequence would improve actionability and workflow clarity.

Suggestions

Consolidate the templated Check/Fix/Explain/Code Review sections, which restate the same task, into a single concise procedure.

Add one small inline HTML snippet (e.g. a preload example) in the body so guidance is actionable before the reader jumps to references/rule.md.

Express an explicit sequence with a validation checkpoint — measure the bottleneck in Lighthouse/DevTools, apply the hints, then re-measure to confirm the improvement.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept explanations, but the Check/Fix/Explain/Code Review template sections restate the same task in slightly different ways and could be consolidated.	2 / 3
Actionability	The Quick Reference names which hint suits each scenario, but the body provides no executable HTML and defers all code examples to references/rule.md, leaving the guidance high-level.	2 / 3
Workflow Clarity	The Check/Fix/Code Review sections imply a measure-then-recommend flow and the Code Review section requires describing a measurement method, but there is no explicit sequenced workflow with validation checkpoints in the body.	2 / 3
Progressive Disclosure	The body is a concise overview that clearly signals a single one-level-deep reference, references/rule.md (a verified file), for full implementation details, code examples, and framework guidance.	3 / 3
	Total	9 / 12 Passed

Description

50%

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 covers a clear performance niche with an explicit 'Use when' trigger and concrete verification actions, but every dimension lands at the mid-level because the 'what' is muddled by an embedded title phrase and the trigger terms are generic. Tightening the wording and adding resource-hint-specific vocabulary would lift it.

Suggestions

Remove the duplicated title fragment ('related to Use resource hints for faster loading') and state the skill's purpose cleanly, e.g. 'Audits and recommends preload, prefetch, and preconnect resource hints to speed up page loading.'

Add resource-hint-specific trigger terms users would say — 'preload', 'prefetch', 'preconnect', 'LCP', 'Core Web Vitals' — alongside the generic performance terms.

Sharpen the 'what' by listing the concrete actions (audit existing hints, verify the bottleneck, recommend hint changes) so the skill's capability is unambiguous.

Dimension	Reasoning	Score
Specificity	Names the performance domain and concrete actions ('auditing slow page loads, heavy assets, or rendering delays' and 'Verify the actual bottleneck in DevTools, Lighthouse, or field data'), but lists only two actions rather than a comprehensive set.	2 / 3
Completeness	Has an explicit 'Use when...' trigger and describes the verify-before-recommend action, but the 'what' is muddled by the awkwardly embedded title fragment 'related to Use resource hints for faster loading'.	2 / 3
Trigger Term Quality	Includes natural terms ('slow page loads', 'heavy assets', 'rendering delays') but omits resource-hint-specific vocabulary (preload, prefetch, preconnect, LCP, Core Web Vitals) that users would say.	2 / 3
Distinctiveness Conflict Risk	Targets a specific performance niche, but the trigger terms (slow page loads, heavy assets, rendering delays) are generic enough to overlap with other performance skills like image optimization or caching.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/performance-resource-hints/SKILL.md
Commit: 48405aa

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.