CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webp-format

Use when reviewing image assets, markup, and CDN or build transforms related to Use WebP format with fallbacks. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.

Quality

72%

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

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 skill body is a clean, well-organized overview with excellent progressive disclosure to a real, one-level-deep reference file. It is dragged down by duplicated WebP-benefit facts Claude already knows, vague imperative sections (Check/Fix/Explain) with no inline commands or markup, and no validation checkpoint in the body for the batch-conversion fix step.

Suggestions

Replace the vague 'Fix' section with one concrete inline example (e.g. a picture-element snippet or a single cwebp/Sharp command) while keeping the rest in references/rule.md.

Deduplicate the 25-35% claim and drop background facts (browser support percentages, transparency/animation support) that Claude already knows; keep only the actionable bullets.

Add an explicit verification step to the body's workflow (e.g. 'Confirm in DevTools that the WebP variant is served with a working fallback'), since the Fix step is a batch conversion and body-level validation is currently absent.

DimensionReasoningScore

Conciseness

The body is short but the 25-35% compression claim is stated twice (intro and Quick Reference) and background facts like '97%+ browser support' and 'Supports transparency (like PNG) and animation (like GIF)' explain concepts Claude already knows. Not 4 because this duplication and background padding are concrete trim targets.

3 / 5

Actionability

'Use picture element for older browser fallbacks' and the explicit pointer to references/rule.md (verified to contain executable cwebp/Sharp/ImageMagick commands) give some concrete guidance, but the body's own imperatives — 'Convert images to WebP format and implement proper fallback strategies' — are high-level with no commands or markup inline. Not 4 because the Check/Fix/Explain sections lack executable specifics.

3 / 5

Workflow Clarity

The Check / Fix / Explain / Code Review sections give recognizable structure, but there is no sequencing between them and no validation checkpoint in the body — verification lives only in the reference. The Fix step ('Convert images...') describes a batch operation with no inline verification, which caps this score at 3 per the feedback-loop guideline.

3 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file exists, is well-organized (Code Example, Converting to WebP, framework sections, Verification), and references nothing further. Content is appropriately split between the overview and the detail file.

5 / 5

Total

14

/

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 strong description with an explicit 'Use when' trigger, concrete review actions, and good natural keywords. Its main gaps are a check-only 'what' that omits the fix/convert capability, slightly awkward phrasing around the embedded rule name, and a few missing common synonyms like '.webp' or 'image optimization'.

Suggestions

State the 'what' as concrete actions covering both check and fix, e.g. 'Reviews and converts images to WebP with picture-element fallbacks; checks encoded size, rendered size, loading strategy, and above-the-fold impact.'

Add a few natural trigger variations users actually say, such as '.webp', 'image optimization', or 'compress images'.

Reword 'related to Use WebP format with fallbacks' into a natural clause so the trigger reads smoothly.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'reviewing image assets, markup, and CDN or build transforms' and 'Check encoded size, rendered size, loading strategy, and above-the-fold impact' — with minor coverage gaps. Not 5 because the actions cluster around review/check and omit the fix/convert side of the skill.

4 / 5

Completeness

Both what ('Check encoded size, rendered size, loading strategy, and above-the-fold impact together') and an explicit when ('Use when reviewing image assets, markup, and CDN or build transforms...') are present. Not 5 because the what is check-only and the 'related to Use WebP format with fallbacks' phrasing is awkward rather than crisply stating the skill's actions.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'WebP', 'fallbacks', 'image assets', 'markup', 'CDN', 'build transforms', 'above-the-fold'. Not 5 because common user phrasings like '.webp', 'image optimization', or 'compress images' are missing.

4 / 5

Distinctiveness Conflict Risk

WebP format review is a clear niche with a distinct trigger ('Use WebP format with fallbacks'). Not 5 because the broad opening 'reviewing image assets, markup, and CDN or build transforms' could overlap with closely related image-optimization or lazy-loading skills.

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/webp-format/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.