CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

77%

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

Quality

Content

71%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 concise, well-structured overview that points cleanly to a real one-level-deep reference file, but the body itself lacks executable specifics — how to detect or convert progressive JPEGs lives entirely in the reference. Checkpoint guidance (DevTools confirmation) is named but not elaborated.

Suggestions

Inline one concrete detection command in the Check section (e.g. `identify -verbose image.jpg | grep Interlace` or `file image.jpg` showing "progressive") so the core action is executable without opening the reference.

Inline one conversion command in the Fix section (e.g. `convert input.jpg -interlace Plane output.jpg`) to make the fix actionable from the body.

Merge the redundant preview-performance statement (intro / Quick Reference / Explain) into a single statement and use the freed space for the detection snippet.

DimensionReasoningScore

Conciseness

The body is lean with clear sections, but the "low-quality preview improves perceived performance" fact is stated three times (intro, Quick Reference bullet, and the Explain section). Efficient overall with minor trimming opportunities, so not 5; not 3 because there is no padded explanation of concepts Claude already knows.

4 / 5

Actionability

The body gives high-level directives ("Check if JPEG images are saved in progressive format"; "Convert baseline JPEGs to progressive format") with no commands or detection method inline — the specifics are deferred to references/rule.md. Some concrete guidance (named artifacts, DevTools confirmation) but incomplete on its own, matching the 3 anchor rather than 4.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is coherent and the single review action is unambiguous (simple-skill case), with a named verification step ("describe how to confirm the fix in DevTools"). Not 5 because the actual detection/verification mechanics are only implied and deferred to the reference file.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and a single 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 holds the code examples. Matches the clear-overview anchor exactly.

5 / 5

Total

16

/

20

Passed

Description

75%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 solid description with an explicit trigger clause and several concrete, review-oriented actions, but the awkwardly embedded rule title ("related to Use progressive JPEG encoding") degrades readability and the natural-term coverage is incomplete. It distinguishes itself reasonably well within the image-optimization space.

Suggestions

Rewrite the garbled clause, e.g. "Review image assets, markup, and CDN or build transforms for progressive JPEG encoding; check encoded size, rendered size, loading strategy, and above-the-fold impact together. Use when auditing image loading performance or when the user mentions JPEGs, image optimization, or perceived load time."

Add missing natural synonyms such as "baseline JPEG", "image optimization", "perceived performance", and ".jpg/.jpeg" to trigger-term coverage.

State the fix-side capability (converting baseline JPEGs to progressive) alongside the review actions to round out the 'what'.

DimensionReasoningScore

Specificity

Names several concrete review actions ("reviewing image assets, markup, and CDN or build transforms"; "Check encoded size, rendered size, loading strategy, and above-the-fold impact together"), with minor gaps: no fix/convert action is named and the embedded rule title garbles the sentence. Not 5 because coverage is not comprehensive; not 3 because it goes beyond 1-2 actions.

4 / 5

Completeness

Both what and when are present: an explicit "Use when reviewing..." trigger clause plus concrete checking actions. Not 5 because the duplicated mid-sentence phrase "related to Use progressive JPEG encoding" obscures the core action and trigger phrases are not crisply enumerated; not 3 because the 'Use when' clause is explicit, so the cap does not apply.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "image assets", "markup", "CDN", "progressive JPEG", "loading strategy", "above-the-fold". Missing common synonyms and extensions like "baseline JPEG", "image optimization", "perceived performance", or ".jpg", so it falls just short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The progressive JPEG niche is distinct, but the broad triggers "reviewing image assets, markup, and CDN or build transforms" overlap with sibling image-delivery/optimization skills. Mostly distinct with minor overlap risk, matching the 4 anchor rather than the minimal-conflict 5.

4 / 5

Total

16

/

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/progressive-jpeg/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.