CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

avif-format

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

Quality

75%

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/avif-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 body is a lean, well-structured overview with exemplary progressive disclosure — one clear pointer to a real reference file holding all executable detail. However, judged on its own it is padded with a thrice-repeated compression statistic and its Check/Fix/Explain sections carry only vague one-line directives with no concrete verification steps.

Suggestions

Remove the redundant 50%-smaller-than-JPEG statistic from the Quick Reference and Explain sections (it already appears in the intro) and delete the Check section that merely restates the skill's purpose, tightening conciseness toward the lean anchor.

Add one concrete check to the body, e.g. a specific DevTools procedure ('Network tab → filter by image → confirm content-type: image/avif and compare transferred sizes vs the JPEG fallback'), to lift actionability from named-mechanism to executable guidance.

Make the Code Review workflow's validation explicit: list the verification steps (confirm AVIF served, fallback renders in Safari < 16, encoded size delta) as a short checklist instead of the vague 'describe how to confirm the fix in DevTools'.

DimensionReasoningScore

Conciseness

The body is short but noticeably repetitive: the '50% better compression than JPEG' claim appears in the intro, again in Quick Reference ('AVIF offers 50% better compression than JPEG'), and a third time in Explain ('Explain how AVIF provides 50% better compression than JPEG'), and the Check section restates the skill's purpose. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'. Not a 2 because there is no padding of concepts Claude already knows and the overall length is lean; not a 4 because the triple-repeated statistic and the redundant intro/Quick-Reference overlap are clear trim candidates.

3 / 5

Actionability

One concrete mechanism is named ('Use picture element with WebP and JPEG fallbacks') and browser support is enumerated ('Chrome, Firefox, Safari 16+, Edge'), but the Check, Fix, and Explain sections are single vague sentences ('Implement AVIF support with proper fallbacks for browsers that don't support it') with all executable detail deferred to references/rule.md. This matches 'some concrete guidance but incomplete... missing key details' rather than the mostly-executable anchor 4, since the body contains no command, code snippet, or specific DevTools check to run.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections provide a recognizable sequence for a review task, but each step is a one-line directive with no explicit validation checkpoints — verification is only implicitly gestured at ('describe how to confirm the fix in DevTools'). This fits 'steps listed but validation gaps; checkpoints missing or implicit'. Not a 4 because no concrete verification command or DevTools procedure is given in the body itself.

3 / 5

Progressive Disclosure

The body is a clear overview that appropriately delegates full implementation detail to a single, well-signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which exists and contains exactly that material. Sections are well-organized and navigation is trivial, matching the top anchor. Not a 4 because there is no misplaced content, buried reference, or organization gap.

5 / 5

Total

14

/

20

Passed

Description

83%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 enumerated check dimensions, and good natural keyword coverage. Its main weaknesses are the awkwardly embedded rule title and missing common synonyms (WebP, image optimization, .avif).

DimensionReasoningScore

Specificity

Names concrete review targets ("image assets, markup, and CDN or build transforms") and specific check actions ("encoded size, rendered size, loading strategy, and above-the-fold impact"), matching the 'several specific actions with minor gaps' anchor. Not a 5 because it omits parts of the rule's actual scope (fallback verification, picture-element markup review) and the embedded rule title 'related to Use AVIF format for modern browsers' reads awkwardly rather than as a crisp capability statement.

4 / 5

Completeness

Both what and when are explicit: the 'what' is the concrete check list ('Check encoded size, rendered size, loading strategy, and above-the-fold impact together') and the 'when' is an explicit trigger clause ('Use when reviewing image assets, markup, and CDN or build transforms related to...'). This matches the top anchor — clear, explicit answers to both questions with concrete trigger phrases. Not a 4 because the when-clause is specific and enumerated rather than merely present.

5 / 5

Trigger Term Quality

Includes strong natural terms a user would say — 'AVIF', 'image assets', 'markup', 'CDN', 'build transforms', 'loading strategy', 'above-the-fold' — giving good keyword coverage. Not a 5 because common synonyms like 'WebP', 'image optimization', 'file format', or '.avif' extensions are missing, which the top anchor expects.

4 / 5

Distinctiveness Conflict Risk

The AVIF anchor plus the enumerated check dimensions create a mostly distinct niche with minimal wrong-skill trigger risk. Not a 5 because 'reviewing image assets, markup, and CDN or build transforms' overlaps with sibling image-optimization rules (e.g., WebP conversion, lazy loading, responsive images checklists), so minor overlap risk with closely related skills remains.

4 / 5

Total

17

/

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