CtrlK
BlogDocsLog inGet started
Tessl Logo

optimized

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

62

Quality

74%

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

Quality

Content

61%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 actionable with specific encoder settings and a clean reference split, but it explains concepts Claude already knows and lacks an explicit validation checkpoint for a batch/de destructive re-encoding workflow.

Suggestions

Remove or trim the 'Explain' section (DCT/DEFLATE/EXIF fundamentals) — Claude already knows these; keep only any non-obvious project-specific nuance.

Add an explicit validation step to the Fix workflow, e.g. verify the re-encoded image has no visible quality loss and correct dimensions before replacing the original, with a retry-on-failure loop.

Convert the prose encoder specs into executable commands or a short code block in the body (or ensure rule.md's examples are surfaced as the primary fix recipe) so guidance is copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly efficient in the Quick Reference/Check/Fix sections, but the 'Explain' section restates concepts Claude already knows (DCT/DEFLATE compression, what EXIF metadata is) and the intro carries motivational padding ('A DSLR-quality JPEG... can be 8MB').

3 / 5

Actionability

Provides concrete tools and parameters (mozjpeg quality 80 progressive=true, pngquant 65-80, AVIF quality 60 effort 6, SVGO), but gives them as prose specs rather than copy-paste commands or code in the body, with execution deferred to references/rule.md.

4 / 5

Workflow Clarity

Numbered Check and Fix steps give a clear sequence, but this is a batch operation over all image assets with effectively destructive re-encoding and no explicit validation checkpoint (e.g. verify visual quality / confirm no upscale before replacing), which caps the score at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organised sections (Quick Reference, Check, Fix, Explain, Code Review) with a clearly signalled one-level-deep reference to a real references/rule.md for implementation details; the inline 'Explain' concept material is a minor organisation gap.

4 / 5

Total

14

/

20

Passed

Description

87%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, well-structured description that explicitly covers both what to do and when to use it, with concrete actionable checks and a distinct niche. Its only weakness is slightly limited verb variety and a few missing common synonyms.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions ('Check encoded size, rendered size, loading strategy, and above-the-fold impact'), but verbs are limited to 'reviewing'/'check' rather than varied concrete operations, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both: 'what' via 'Check encoded size, rendered size, loading strategy, and above-the-fold impact together' and 'when' via the concrete 'Use when reviewing image assets, markup, and CDN or build transforms...' trigger phrase.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('image assets', 'markup', 'CDN', 'build transforms', 'loading strategy', 'above-the-fold'), but common synonyms like 'compress', 'WebP', or 'lazy load' are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (web image optimisation for performance) with distinct, specific triggers ('above-the-fold impact', 'CDN or build transforms') that minimise overlap with other skills.

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

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.