CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lazy-loading

Use when auditing slow page loads, heavy assets, or rendering delays related to Implement lazy loading for offscreen content. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes. Absence of `loading='lazy'` is not enough by itself when fold position is unknown.

Quality

77%

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/lazy-loading/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, token-efficient overview with excellent progressive disclosure and a clear check/fix/explain workflow. Its main weakness is actionability: the body itself contains no executable code or commands and defers all implementation specifics to the reference file, so it relies entirely on Claude opening references/rule.md to act.

Suggestions

Add a minimal quick-start snippet to the Fix section (e.g. `<img src="product.jpg" width="400" height="300" loading="lazy">` plus an iframe example) so the overview is immediately actionable without opening the reference file.

Surface the highest-value decision details from rule.md in the body: keep the first 2-4 images or first visible row eager, reserve space with explicit dimensions/placeholders to avoid CLS, and start Intersection Observer rootMargin at 200-400px.

Trim the opening sentence and 'Explain' section that restate what lazy loading is — Claude already knows this and both are pure token cost.

DimensionReasoningScore

Conciseness

The body is lean (~35 lines) with a useful Quick Reference, but the intro sentence 'Lazy loading defers non-critical resources until needed—this reduces initial page weight, speeds up first paint, and saves bandwidth' and the 'Explain how lazy loading defers resource loading until needed' section explain a concept Claude already knows, which anchor 5 penalizes. Otherwise every section earns its place, matching anchor 4 (efficient with minor trimmable over-explanation).

4 / 5

Actionability

Quick Reference gives concrete directives ('Use loading='lazy' for images below the fold', 'Never lazy load LCP/above-fold images', 'Use Intersection Observer for custom lazy loading') but the body contains no code or commands at all — even a minimal `<img loading='lazy' width height>` snippet is absent, and key details (eager first 2-4 images, rootMargin range, placeholder dimensions) are only in references/rule.md. This matches anchor 3: some concrete guidance but incomplete, missing key details, rather than anchor 4's 'concrete code or commands with minor gaps'.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clearly sectioned and unambiguous, with an evidence gate ('Only report this when the code or route context makes offscreen placement clear') and a measurement requirement ('describe the measurement method used to confirm the issue'). However, concrete validation steps (waterfall inspection, PageSpeed verification) live only in references/rule.md, not the body — anchor 4's 'clear sequence with most checkpoints present; minor validation gaps'. Not 5 because the explicit verification checklist is deferred to the reference file; not 3 because the sequence is coherent and a pre-report checkpoint is explicitly stated.

4 / 5

Progressive Disclosure

The body is a well-organized overview under 50 lines that points to `references/rule.md` for 'full implementation details, code examples, and framework-specific guidance'. The bundle matches: references/rule.md exists (108 lines), is exactly one level deep with no nested .md references, and appropriately holds the code examples, decision tables, and verification checklist. This matches anchor 5: clear overview with well-signaled one-level-deep references and appropriate content split.

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 solid description with explicit 'Use when' triggers, natural keywords, named measurement tools, and a useful false-positive guard ('Absence of loading='lazy' is not enough by itself when fold position is unknown'). Its main defect is a template artifact — the rule title 'Implement lazy loading for offscreen content' is pasted mid-sentence, producing a garbled capability statement — plus slightly thin coverage of implementation actions and synonyms.

Suggestions

Rewrite the garbled middle clause into a clean third-person capability statement, e.g. 'Audits and implements lazy loading for offscreen images, iframes, and heavy components. Use when auditing slow page loads, heavy assets, or rendering delays...'.

Add natural synonyms to broaden trigger coverage: 'page speed', 'performance', 'below the fold', and 'images or embeds not loading'.

State the implementation side explicitly (native loading='lazy' and Intersection Observer) so the what is as concrete as the verification guidance.

DimensionReasoningScore

Specificity

It lists several concrete actions with named tools: 'auditing slow page loads, heavy assets, or rendering delays', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data', and (via the embedded title) 'Implement lazy loading for offscreen content'. Gaps are minor (no mention of iframes/videos or Intersection Observer), matching anchor 4 rather than anchor 3's '1-2 concrete actions, not comprehensive'; not 5 because coverage of the implementation side is thin and the capability sentence is garbled.

4 / 5

Completeness

Both parts are explicitly present: an explicit 'Use when auditing slow page loads, heavy assets, or rendering delays...' trigger, and a what ('Implement lazy loading for offscreen content', plus verify-bottleneck-before-recommending). It falls short of anchor 5 because the what is delivered as a pasted rule title inside a broken sentence ('...related to Implement lazy loading for offscreen content.') rather than a clean capability statement, and the when-clause is specific but the what reads awkwardly — anchor 4's 'both present; when/what could be more explicit'.

4 / 5

Trigger Term Quality

Natural phrases a user would actually say are present: 'slow page loads', 'heavy assets', 'rendering delays', plus tool names 'DevTools' and 'Lighthouse' and the concrete token `loading='lazy'`. A few common variations are missing ('page speed', 'performance', 'below the fold', 'images/iframes not loading'), matching anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Distinct niche markers (`loading='lazy'`, 'fold position', Lighthouse/DevTools, offscreen content) pin it to lazy-loading work specifically. It is not 5 because the trigger phrase 'slow page loads, heavy assets, or rendering delays' is broad enough to overlap with general performance-audit skills and sibling frontend performance rules (image optimization, import-on-visibility), matching anchor 4's 'mostly distinct; minor overlap risk with closely related skills'.

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/lazy-loading/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.