CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

srcset

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

Quality

80%

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

Quality

Content

65%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.

The body is a well-structured, actionable review skill with excellent progressive disclosure into a real reference file. It is dragged down by a redundant Explain section that covers knowledge Claude already has, a Code Review section duplicating the Check/description content, and the absence of a post-fix verification checkpoint for what is a batch fix operation.

Suggestions

Cut or shrink the Explain section: Claude already knows how srcset, width/density descriptors, and sizes work — keep only the one non-obvious rule (density descriptors only for fixed-size images) if it is not already in Quick Reference.

Remove the Code Review section, which restates the frontmatter description and the Check section, and fold the DevTools confirmation hint into a final verification step after Fix.

Add a post-fix validation checkpoint (e.g., re-run the Check criteria and confirm the corrected HTML in the browser's network panel) since applying fixes across all flagged images is a batch operation.

DimensionReasoningScore

Conciseness

The Quick Reference, Check, and Fix sections are lean and earn their tokens, but the Explain section reteaches srcset descriptor mechanics Claude already knows ('the browser combines this with the sizes attribute to calculate which candidate...'), the intro pads with motivational stats, and the Code Review section duplicates the frontmatter description and Check section.

3 / 5

Actionability

Concrete, specific directives ('Flag: 1) Any <img> wider than 100px... that lacks a srcset attribute'; 'Generate multiple width variants: typically 400w, 800w, 1200w') with a defined output format (file path and line number, complete corrected HTML). Minor gaps: no corrected-HTML template and no command or tool for generating the width variants.

4 / 5

Workflow Clarity

The Check → Fix → Explain sequence is clearly ordered, but the Fix step is a batch operation across all images with no post-fix verification step — DevTools confirmation is only name-dropped in the Code Review section rather than specified as a checkpoint, so it fits the sequence-present-but-checkpoints-implicit anchor.

3 / 5

Progressive Disclosure

A ~45-line overview with well-organized sections and a single clearly-signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which exists and genuinely contains the deferred code examples rather than inlining them in the body.

5 / 5

Total

15

/

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: it names a clear niche, enumerates concrete review actions, and pairs an explicit 'Use when' trigger with a specific capability list. Its only weaknesses are a few missing natural synonyms (image optimization, retina) and slight breadth into adjacent image-performance skills.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — 'reviewing image assets, markup, and CDN or build transforms' and 'Check encoded size, rendered size, loading strategy, and above-the-fold impact together' — with comprehensive coverage of the responsive-image review domain, matching the multiple-specific-actions anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

Explicitly answers 'when' ('Use when reviewing image assets, markup, and CDN or build transforms related to Use srcset for responsive images') and 'what' ('Check encoded size, rendered size, loading strategy, and above-the-fold impact together') with concrete trigger phrases, matching the both-clearly-answered anchor.

5 / 5

Trigger Term Quality

Includes the natural phrases a user would say — 'srcset', 'responsive images', 'image assets', 'CDN', 'loading' — but misses common variations like 'image optimization', 'retina', or 'picture element', so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The srcset/responsive-images niche is distinct, but the breadth into 'loading strategy', 'above-the-fold impact', and 'CDN or build transforms' creates minor overlap risk with adjacent image-performance, lazy-loading, or CDN-configuration skills.

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/srcset/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.