lazy-above-fold

Use when auditing slow page loads, heavy assets, or rendering delays related to Disable lazy loading for above-the-fold content. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

67%

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/lazy-above-fold/SKILL.md

Quality

Content

65%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 is lean and well-structured with excellent progressive disclosure into a real references/rule.md bundle, but it lacks in-body executable examples and explicit verification checkpoints, leaving actionability and workflow clarity in the mid-range. The detailed code examples it points to do exist in the referenced file.

Suggestions

Add one short in-body HTML snippet (e.g. the loading="lazy" → fetchpriority="high" swap) so the skill is executable without opening the reference.

Make the verification checkpoint explicit in the body (e.g. a 'Validate' step pointing to Lighthouse/PageSpeed confirmation that the LCP image changed) to strengthen workflow clarity.

The Explain/Code Review sections overlap with the Quick Reference; consolidate to tighten conciseness toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is short and largely free of padding, using terse sections (Quick Reference, Check, Fix, Explain) that assume Claude's competence; it is not a full 5 because a few lines restate the obvious ('Lazy loading above-the-fold images delays the LCP') that could be trimmed.	4 / 5
Actionability	Guidance is concrete at the attribute level (e.g. 'Remove loading="lazy"', 'consider fetchpriority="high"') but the body itself has no executable code or command examples — those live in references/rule.md, so it is more instructive than copy-paste ready, sitting at 3 with minor gaps rather than fully executable at 5.	3 / 5
Workflow Clarity	The body lays out a loose Check → Fix → Explain → Code Review sequence, but there are no explicit validation checkpoints or feedback loops in the body itself; while the skill is not destructive, the verification step is only implied via the description, so it lands at 3 ('steps present but checkpoints missing or implicit').	3 / 5
Progressive Disclosure	The SKILL.md is a concise overview with well-organized sections and a single clearly-signaled one-level-deep reference ('see references/rule.md'), which is a real bundle file containing the detailed examples; navigation is easy and content is appropriately split.	5 / 5
	Total	15 / 20 Passed

Description

70%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.

The description has a clear 'Use when' trigger with natural performance-audit keywords and a reasonably distinct niche, but it leans on a single verification action and under-specifies the concrete remediation actions. It is solid but not exemplary.

Suggestions

Add concrete remediation actions to the 'what' (e.g. 'Remove loading="lazy" from above-the-fold images and apply fetchpriority="high"') so the description lists multiple specific actions rather than a single verify step.

Include a few common synonyms/file-adjacent trigger terms (e.g. 'LCP', 'Core Web Vitals', 'hero image') to improve keyword coverage toward a 5 on trigger terms.

Tighten phrasing so the rule name reads as a capability rather than repeating the rule title verbatim, which slightly dilutes specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ('lazy loading for above-the-fold content') and one concrete action ('Verify the actual bottleneck in DevTools, Lighthouse, or field data'), but it is framed as a single verification step rather than a list of specific actions, so it sits between 'domain + 1-2 actions' (3) and 'several specific actions' (4); closer to 3 because the only explicit action is 'verify the bottleneck'.	3 / 5
Completeness	It explicitly answers 'when' via 'Use when auditing slow page loads...' and the 'what' is the audit/verification of the lazy-above-fold bottleneck plus 'recommending changes'; both are present but the 'what' could be more explicit about the actual remediation, so it is not a full 5.	4 / 5
Trigger Term Quality	It includes natural phrases users would say ('slow page loads', 'heavy assets', 'rendering delays', 'DevTools', 'Lighthouse') which are good triggers; a few obvious synonyms (e.g. 'page speed', 'LCP', 'Core Web Vitals') are missing, placing it just below comprehensive coverage at 5.	4 / 5
Distinctiveness Conflict Risk	It targets a narrow, named performance rule (lazy loading above-the-fold) with a clear niche, distinct from generic performance skills; minor overlap risk exists with broader 'audit page performance' skills, keeping it just below a 5.	4 / 5
	Total	15 / 20 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/lazy-above-fold/SKILL.md
Commit: 30756a7

Reviewed: 20 days 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.