CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cumulative-layout-shift

Use when auditing slow page loads, heavy assets, or rendering delays related to Minimize cumulative layout shift. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

68%

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/cumulative-layout-shift/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 compact, well-structured overview that correctly pushes implementation detail to a single real reference file one level deep. The weaknesses are instruct-then-defer actionability (no executable snippets or commands in the body), an implicit rather than explicit verify-after-fix workflow, and a duplicated concept explanation between the intro and the Explain section.

Suggestions

Inline one minimal executable example in the Fix section (e.g., the `<img width height>` or `aspect-ratio` snippet from references/rule.md) so the primary fix is copy-paste ready without opening the reference.

Close the workflow loop: after the Fix steps, add an explicit re-measure checkpoint ("Re-run Lighthouse and confirm CLS < 0.1 before considering the issue resolved").

Cut the duplicated rationale — drop either the intro sentence or the "Explain" section's restatement of accidental clicks and frustration, keeping only one concise why-it-matters note.

DimensionReasoningScore

Conciseness

The body is short, but the intro ("Layout shifts cause accidental clicks, reading disruption, and user frustration—a good CLS score ensures content stays where users expect it") explains motivation Claude already knows, and the "Explain" section ("Explain how CLS measures visual stability and why unexpected layout shifts frustrate users and cause accidental clicks") restates the same accidental-clicks rationale. This is some unnecessary, duplicated explanation — more than the minor trimmable instances of level 4, but not the pervasive padding of level 2.

3 / 5

Actionability

There is concrete guidance — "Measure CLS using Lighthouse or PageSpeed Insights. Verify score is below 0.1" and "Reserve space for images/embeds with dimensions, use font-display strategies" — but no executable code or commands in the body; the working examples live only in references/rule.md. Level 3 fits: specific tools and a threshold are named, yet key executable details (how to run the audit, what markup/CSS to apply) are missing from the instruction text itself.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a rough measure-then-fix sequence with one implicit checkpoint ("Verify score is below 0.1"), but there is no re-measurement after applying fixes and the Explain/Code Review sections read as parallel tasks rather than sequenced steps. Level 3 fits: sequence present, checkpoints implicit; not level 4 because the verify-after-fix loop is absent.

3 / 5

Progressive Disclosure

The body is a lean quick-reference overview and defers depth through a clearly signaled, one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists and contains exactly the promised implementation details and code examples. Structure is well organized with no nested references, matching the clear-overview anchor.

5 / 5

Total

14

/

20

Passed

Description

66%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 serviceable description with an explicit and well-scoped "Use when" trigger and a meaningful verify-before-recommending instruction. Its main weaknesses are a what-that only implies the skill's capabilities and trigger terms that overlap heavily with the general performance-audit category.

Suggestions

State the skill's capabilities directly (e.g., "Measures CLS in Lighthouse/PageSpeed Insights and flags missing image dimensions, unsized embeds, and layout-shifting animations") before the "Use when" clause.

Add distinctive synonyms such as "CLS", "Core Web Vitals", and "visual stability" to the trigger so it fires for users who name the metric rather than the symptom.

DimensionReasoningScore

Specificity

The description names the domain ("Minimize cumulative layout shift") and roughly two concrete actions — "auditing slow page loads, heavy assets, or rendering delays" and "Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes" — but does not enumerate what the skill actually does to fix shifts. This matches the anchor for naming the domain with 1-2 concrete actions; it falls short of level 4 because several capability-level actions (measuring, fixing, reserving space) are absent as explicit capabilities.

3 / 5

Completeness

The "when" is explicit ("Use when auditing slow page loads, heavy assets, or rendering delays...") and a "what" is stated through the actions "auditing" and "Verify the actual bottleneck... before recommending changes". It does not reach level 5 because the what is embedded inside the when-clause rather than framed as a distinct capability statement, and the fixing/optimization half of the skill is not described at all.

4 / 5

Trigger Term Quality

Natural user phrases are present: "slow page loads", "heavy assets", "rendering delays", plus tool names "DevTools, Lighthouse, or field data" and the full term "cumulative layout shift". Coverage is good but common synonyms like "CLS", "Core Web Vitals", "page jumping", or "visual stability" are missing, placing it at good-coverage-with-gaps rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche term "cumulative layout shift" is distinct, but the leading triggers "slow page loads, heavy assets, or rendering delays" are broad performance terms that would equally fire sibling performance skills (image optimization, lazy loading, LCP), leaving real overlap risk with closely related skills. It is not level 4 because most of the trigger surface is shared with the wider performance-audit category.

3 / 5

Total

14

/

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/cumulative-layout-shift/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.