CtrlK
BlogDocsLog inGet started
Tessl Logo

image-file-size

Use when auditing the image pipeline, static assets in `public/`, CMS-managed media, or image CDN transforms. Separate file-size problems from dimension mismatches so you can tell whether the issue is compression, format choice, or responsive delivery.

60

Quality

71%

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/image-file-size/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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-organized with good progressive disclosure and concrete audit steps, but it leans on background stats and defers all executable code plus the post-optimization verification loop to the reference, leaving workflow and actionability at mid-level.

Suggestions

Move or trim the background performance statistics (HTTP-Archive percentages, mobile-conversion figures) so thresholds and steps aren't competing with context Claude already knows.

Add a short inline re-verification checkpoint after Fix (e.g., re-measure each optimized asset and confirm it is under threshold) so the batch workflow has an explicit feedback loop.

Include one small inline executable snippet (e.g., a single Sharp/Squoosh WebP command) in the body so guidance is copy-paste ready without opening the reference.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but background stats (HTTP-Archive percentages, mobile-conversion figures) and threshold numbers duplicated between Quick Reference and Fix don't all earn their place.

2 / 3

Actionability

Concrete numbered procedures and named tools with quality settings, but no executable inline code in the body — runnable detail is deferred entirely to the reference file.

2 / 3

Workflow Clarity

Check/Fix are clearly sequenced, but the body prescribes batch optimization with no inline validate-after-compress/re-measure feedback loop, which caps workflow clarity for destructive batch operations.

2 / 3

Progressive Disclosure

Clear overview with one well-signaled one-level-deep reference (references/rule.md, verified present) and cleanly organized sections, giving easy navigation.

3 / 3

Total

9

/

12

Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: concrete actions, explicit trigger guidance, and a distinctive scope. Its main weakness is trigger-term naturalness, leaning on technical jargon over the everyday phrases users actually say.

DimensionReasoningScore

Specificity

Lists multiple concrete audit contexts ("image pipeline, static assets in `public/`, CMS-managed media, image CDN transforms") plus a concrete diagnostic action ("Separate file-size problems from dimension mismatches").

3 / 3

Completeness

An explicit "Use when..." clause provides the trigger, and the what (auditing image assets and separating file-size vs dimension issues) is clearly stated.

3 / 3

Trigger Term Quality

Triggers are relevant but jargon-leaning ("image CDN transforms", "CMS-managed media") and omit the common user phrasings like "image file size", "heavy/large images".

2 / 3

Distinctiveness Conflict Risk

The file-size-vs-dimension-mismatch framing and concrete pipeline/CDN triggers carve a clear niche unlikely to conflict with adjacent skills.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.