CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

78%

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-above-fold/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-structured instruction-style body: concrete attribute-level guidance, a clear check-then-fix flow with a measurement checkpoint, and exemplary progressive disclosure via one existing reference file. Only minor trims and an inline HTML example would raise it further.

DimensionReasoningScore

Conciseness

The body is lean with a Quick Reference list and terse Check/Fix sections and no padding or explanations of known concepts, but the 'Explain' section restates the intro and the Code Review section awkwardly repeats the full rule name, leaving minor tokens to trim.

4 / 5

Actionability

Guidance is concrete and executable with real syntax ('Do not use loading="lazy"', 'Remove loading="lazy"... consider using fetchpriority="high"'), though no copy-paste HTML example is included inline to cover the common cases.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear and the Code Review section requires describing 'the measurement method used to confirm the issue' as a checkpoint, but there is no explicit step for confirming which images are actually above the fold.

4 / 5

Progressive Disclosure

The body is a concise overview with a single, clearly signaled one-level-deep pointer ('see references/rule.md') for full implementation details, and that reference file exists in the bundle.

5 / 5

Total

17

/

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.

A well-scoped, third-person description with an explicit trigger clause and concrete verification guidance. Its main weaknesses are incomplete action coverage (the fix itself is unstated) and missing common trigger synonyms like 'page speed', 'LCP', and 'Core Web Vitals'.

Suggestions

State the concrete remediation actions in the description, e.g. 'Remove loading="lazy" from above-the-fold images and apply fetchpriority="high"', so the 'what' is complete rather than stopping at 'recommending changes'.

Add natural trigger synonyms users commonly say — 'page speed', 'LCP', 'Core Web Vitals' — to broaden keyword coverage for activation.

DimensionReasoningScore

Specificity

The description names the domain and a concrete verification action ('Verify the actual bottleneck in DevTools, Lighthouse, or field data'), but omits the actual remediation actions (removing loading="lazy", applying fetchpriority="high"), leaving action coverage incomplete.

3 / 5

Completeness

Both a 'what' ('Verify the actual bottleneck... before recommending changes') and an explicit 'Use when...' clause are present, but the 'what' stops short of stating the concrete fix, so it does not reach the fully explicit anchor 5.

4 / 5

Trigger Term Quality

It includes natural phrases users would say ('slow page loads', 'heavy assets', 'rendering delays', 'lazy loading', 'above-the-fold') plus tool names, but misses common variations such as 'page speed', 'LCP', and 'Core Web Vitals'.

4 / 5

Distinctiveness Conflict Risk

The lazy-loading/above-the-fold niche is well distinguished with specific triggers, with only minor overlap risk against closely related performance skills like image optimization or general LCP tuning.

4 / 5

Total

15

/

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