CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

offscreen-lazy

Use when reviewing image assets, markup, and CDN or build transforms related to Lazy load offscreen images. Check encoded size, rendered size, loading strategy, and above-the-fold impact together. Missing `loading='lazy'` is only a valid finding when you can reasonably tell the image is offscreen or non-critical.

Quality

83%

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

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-organized, actionable review skill with a clean progressive-disclosure structure pointing to a real, appropriately scoped reference file. Its main weakness is redundancy: the intro and 'Explain' sections explain lazy-loading fundamentals Claude already knows, and the uncertainty guardrail is stated twice.

Suggestions

Collapse the intro paragraph and 'Explain' section into a few lines, keeping only non-obvious specifics (e.g., the ~1250px browser preload threshold and the LCP caveat) and dropping the general explanation of how lazy loading works and why bandwidth matters.

State the fold-position guardrail once (e.g., in Check) instead of twice — the Quick Reference bullet and the Check closing sentence are near-duplicates.

Tighten the workflow by specifying what to confirm in DevTools (e.g., verify deferred requests in the Network panel on scroll) or by inlining one minimal bad/good HTML snippet so the fix guidance is copy-paste ready without opening the reference.

DimensionReasoningScore

Conciseness

The intro paragraph and the 'Explain' section both restate how native lazy loading works and why it matters — concepts Claude already knows — and the fold-position guardrail appears nearly verbatim twice ('If fold position is unclear from the snippet, do not invent a lazy-loading defect' vs 'If fold position cannot be inferred from the snippet, do not report missing lazy loading as a defect'). Mostly efficient and tight, but these unnecessary explanations and redundancies could be trimmed; the non-obvious specifics (the ~1250px threshold distance) are worth keeping.

3 / 5

Actionability

Concrete, executable review guidance: 'Add loading="lazy" to all <img> elements below the fold', 'add fetchpriority="high" and remove loading="lazy"' for the LCP image, and 'Ensure all lazy-loaded images have explicit width and height attributes'. Falls short of fully copy-paste ready because no corrected HTML example appears inline (it is delegated to references/rule.md) and the DevTools confirmation is directed but not specified.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear, and the anti-false-positive guardrail ('do not report missing lazy loading as a defect' when fold position is unknown) acts as a validation checkpoint. Minor gap: 'describe how to confirm the fix in DevTools' names a verification step but leaves its content unspecified in the body.

4 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview that clearly signals one-level-deep references: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and references/rule.md exists and contains exactly that (full code examples, rationale, framework guidance). Content is appropriately split with easy navigation.

5 / 5

Total

16

/

20

Passed

Description

88%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 strong description: explicit 'Use when...' trigger guidance, several concrete review actions, and a useful guardrail against false-positive findings. Keyword coverage is good but could add common synonyms like 'below the fold' and performance-metric terms users naturally mention.

DimensionReasoningScore

Specificity

Multiple specific concrete actions with comprehensive coverage of the domain: 'reviewing image assets, markup, and CDN or build transforms' and 'Check encoded size, rendered size, loading strategy, and above-the-fold impact together'. It goes beyond action lists to specify a validity condition ('Missing loading='lazy' is only a valid finding when you can reasonably tell the image is offscreen or non-critical').

5 / 5

Completeness

Both what and when are explicitly answered with concrete triggers: the 'when' opens with 'Use when reviewing image assets, markup, and CDN or build transforms related to Lazy load offscreen images', and the 'what' specifies the checks to perform. Not a 4 because the 'when' clause is explicit and concrete rather than merely present.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: 'lazy load', 'offscreen images', 'image assets', 'above-the-fold', 'loading strategy', and the literal `loading='lazy'` attribute. A few natural terms users might say are missing, such as 'below the fold', 'image loading', 'LCP/CLS', or 'page performance'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (lazy loading of offscreen images) with distinct triggers (`loading='lazy'`, offscreen, above-the-fold). Minor overlap risk: 'image assets' and 'encoded size, rendered size' could also surface sibling image-optimization skills (format choice, sizing rules) in the same family, so it is mostly distinct rather than minimal-conflict.

4 / 5

Total

18

/

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