CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

picture-element

Use when reviewing image assets, markup, and CDN or build transforms related to Use <picture> with an <img> fallback. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.

Quality

78%

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

Quality

Content

65%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 well-structured, actionable review skill with excellent progressive disclosure — the body stays an overview and correctly delegates code examples to references/rule.md. The main costs are redundancy between the intro, Quick Reference, and Explain sections (which re-teach HTML Claude already knows), and a missing validation step in the codebase-wide Check→Fix workflow.

Suggestions

Merge the intro paragraph and the Explain section: they repeat the same facts (no <img> means nothing renders in IE11/unsupported formats; alt/width/height belong on <img>; sources are evaluated in order), and the Explain section largely covers HTML knowledge Claude already has — keep only what is specific to this rule.

Add an explicit validation checkpoint at the end of the Fix workflow (e.g. 'after fixing, re-run the Check list and confirm the selected source in DevTools → Network → Img') so the codebase-wide scan-and-fix loop closes; currently Fix ends at 'Show the corrected <picture> markup' with no verification.

Move the six inline numbered conditions in Check to a short bulleted checklist (or reference the Verification section of references/rule.md) so the scan criteria are easier to apply element-by-element than as one run-on sentence.

DimensionReasoningScore

Conciseness

The body is mostly efficient but repeats the same facts across sections: the intro's "A `<picture>` without an `<img>` fallback renders nothing in browsers that don't support `<picture>` (IE11)" and "where `alt`, `width`, `height`, `loading`, and `fetchpriority` attributes live" are restated nearly verbatim in Explain ("The `<img>` element is the fallback for browsers that don't support `<picture>` (IE11)", "The alt attribute must be on the `<img>`"), and the Quick Reference bullet "`<source>` elements are evaluated top-to-bottom; the first match wins" duplicates Explain's "Browsers evaluate `<source>` elements in document order". The Explain section also largely covers standard HTML knowledge Claude already has, which the rubric penalizes. Not a 2 because each section is short and there is no generic filler.

3 / 5

Actionability

Check gives six concrete, verifiable conditions ("Every `<picture>` has an `<img>` as its last child", "Each `<source>` has either a srcset attribute or a media attribute") and Fix gives concrete templates like `<img src="{fallback-url}" alt="{description}" width="{w}" height="{h}">` plus ordering rules. It stops short of 5 because the body contains no complete, copy-paste-ready markup example — the actual HTML examples are deferred to `references/rule.md` — leaving minor gaps in the executable guidance.

4 / 5

Workflow Clarity

A rough sequence exists (Check → Fix → Explain → Code Review), but there is no validation checkpoint: Fix ends with "Show the corrected <picture> markup" without any verify step (e.g. re-run the check or confirm in DevTools). Because the workflow is a batch operation — "Scan all <picture> elements in this codebase" — the rubric's cap for missing validation in batch workflows applies, holding this at 3 even though the individual steps are well defined.

3 / 5

Progressive Disclosure

The body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) with the implementation detail — code examples, use cases, and verification — appropriately split into a single clearly-signaled, one-level-deep reference: "see `references/rule.md`" for "full implementation details, code examples, and framework-specific guidance". That file exists, contains the promised detail, and itself references no further files, matching the 5 anchor.

5 / 5

Total

15

/

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: it explicitly states both what the skill does (review image markup/CDN transforms and check encoded size, rendered size, loading strategy, above-the-fold impact) and when to use it, with mostly natural trigger terms. Weaknesses are cosmetic — the rule title embedded mid-sentence reads awkwardly — and slightly incomplete synonym coverage around responsive-image terminology.

DimensionReasoningScore

Specificity

The description 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 together" — which matches the 'several specific actions; minor gaps in coverage' anchor. It falls short of 5 because the actions are all variations of 'review/check' rather than the comprehensive, distinct action set of the 5-anchor example, and 'related to Use <picture> with an <img> fallback' is an awkwardly embedded rule title rather than a crisp capability statement.

4 / 5

Completeness

Both questions are explicitly answered: the 'what' via "Check encoded size, rendered size, loading strategy, and above-the-fold impact together" plus the review scope, and the 'when' via the explicit "Use when reviewing image assets, markup, and CDN or build transforms related to Use <picture> with an <img> fallback" clause with concrete trigger contexts. It clearly matches the 5 anchor; a 4 would require the 'when' to be vague or only implicit, which it is not.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: "image assets", "markup", "CDN", "build", "<picture>", "<img> fallback", "loading strategy", "above-the-fold" are phrases a frontend reviewer would plausibly say. It is not a 5 because common synonyms a user might naturally say are missing — e.g. "responsive images", "srcset", "AVIF", "WebP", "art direction" — which the referenced material covers.

4 / 5

Distinctiveness Conflict Risk

The <picture>/<img> fallback niche is mostly distinct, with the rule title itself naming the exact markup pattern. Minor overlap risk remains with closely related image-performance skills, since broad phrases like "image assets", "loading strategy", and "above-the-fold impact" could also match a generic image-optimization or lazy-loading skill — the 5 anchor's 'minimal conflict risk' is not quite met.

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/picture-element/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.