progressive-jpeg

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

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/progressive-jpeg/SKILL.md

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.

The body is well-structured and correctly defers detail to a real reference file, but it is padded with restated concepts and offers no executable commands inline. Tightening redundancy and inlining one quick check command would raise actionability and conciseness.

Suggestions

Remove the conceptual restatement in the intro or the Quick Reference so the same point isn't made twice; keep only what Claude doesn't already know.

Inline one executable check (e.g. `identify -verbose image.jpg | grep Interlace` or `file image.jpg`) in the Check section so the body is actionable without opening the reference.

Collapse the near-duplicate Check/Fix/Explain/Code Review phrasing into a single concise procedure to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but the intro is restated by the Quick Reference bullets and the Check/Fix/Explain/Code Review sections restate the same idea several times, adding padding Claude doesn't need.	3 / 5
Actionability	Guidance like 'Check if JPEG images are saved in progressive format' and 'Convert baseline JPEGs to progressive format' is concrete in intent but lacks any executable command or code in the body, deferring all specifics to references/rule.md.	3 / 5
Workflow Clarity	Check/Fix/Explain/Code Review sections provide a loose sequence but no validation checkpoints; acceptable for a non-destructive review task, so it lands at the middle anchor.	3 / 5
Progressive Disclosure	A simple, well-sectioned skill that clearly signals a single one-level-deep reference (references/rule.md) which exists in the bundle, giving easy navigation.	5 / 5
	Total	14 / 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 with explicit trigger guidance and concrete, multi-faceted actions. Trigger terms could include more natural synonyms and file extensions to reduce overlap and improve recall.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — reviewing image assets, markup, CDN/build transforms, and checking encoded size, rendered size, loading strategy, and above-the-fold impact — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (check encoded size, rendered size, loading strategy, above-the-fold impact together) and when via a clear 'Use when reviewing ...' trigger clause.	5 / 5
Trigger Term Quality	Good keyword coverage with 'image assets', 'markup', 'CDN or build transforms', and 'progressive JPEG', but missing natural synonyms like 'JPEG', 'photo', or '.jpg' that a user would say.	4 / 5
Distinctiveness Conflict Risk	The progressive-JPEG niche is distinct, but the broad 'image assets, markup, CDN or build transforms' framing has minor overlap risk with other frontend image skills.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/progressive-jpeg/SKILL.md
Commit: 30756a7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.