CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

critical-images

Use when reviewing image assets, markup, and CDN or build transforms related to Prioritize loading critical images. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.

Quality

84%

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

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 well-structured, token-efficient overview with concrete fix directives and exemplary use of a single one-level-deep reference file. The main weaknesses are minor: a redundant bullet, a Check section lacking explicit criteria, and validation (DevTools confirmation) left underspecified.

DimensionReasoningScore

Conciseness

The body is lean and directive, but not every token earns its place: the bullet "Critical images directly impact LCP Core Web Vital" restates the opening LCP sentence, and the intro explains a concept (what LCP is) Claude already knows, though the 20-40% statistic is genuinely useful. Efficient with minor trimmable padding — the 4 anchor.

4 / 5

Actionability

The Quick Reference and Fix sections give concrete, executable directives ("Use fetchpriority='high' on LCP images", "Preload hero images in document head", "Remove loading='lazy' from above-the-fold images"). Falls short of 5 because the Check section ("Identify which images are critical for initial render") gives no criteria in the body and no inline code example — the full HTML example lives only in references/rule.md.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear and coherent for this simple, non-destructive review skill, and "describe how to confirm the fix in DevTools" gestures at verification. Minor validation gaps remain: the DevTools confirmation is not specified and no explicit verify step exists, matching the 4 anchor rather than 5.

4 / 5

Progressive Disclosure

The body is a concise overview that cleanly delegates depth to a single, clearly signaled, one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"), which exists in the bundle. Content is appropriately split and easy to navigate — the 5 anchor.

5 / 5

Total

17

/

20

Passed

Description

83%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 that explicitly states both what the skill does and when to use it, with concrete domain-specific actions and natural trigger terms. Minor gaps in synonym coverage and slight overlap with sibling image-rule skills keep it just short of top marks.

DimensionReasoningScore

Specificity

"reviewing image assets, markup, and CDN or build transforms" and "Check encoded size, rendered size, loading strategy, and above-the-fold impact" list several concrete actions with minor gaps (the key mechanisms — fetchpriority, preload, lazy loading — are not named). Not 5 because coverage is not comprehensive; clearly above 3 since more than 1-2 specific actions are given.

4 / 5

Completeness

Both parts are explicit and concrete: the when ("Use when reviewing image assets, markup, and CDN or build transforms related to Prioritize loading critical images") and the what ("Check encoded size, rendered size, loading strategy, and above-the-fold impact together"). The when is more specific than the anchor-4 example's generic "Use when working with PDF files", matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural terms a user would say include "image assets", "markup", "CDN", "build transforms", "above-the-fold", and "loading strategy". Good coverage, but common variations such as hero images, LCP, preload, lazy loading, and image file extensions are missing, so it falls short of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to a single niche rule ("Prioritize loading critical images") with distinct triggers, but broad phrases like "image assets, markup, and CDN or build transforms" overlap with closely related image rules (e.g., formats, lazy loading). Mostly distinct with minor overlap risk — the 4 anchor.

4 / 5

Total

17

/

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/critical-images/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.