CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dimensions

Use when reviewing image assets, markup, and CDN or build transforms related to Set explicit width and height on images. Check encoded size, rendered size, loading strategy, and above-the-fold impact together. Separate real CLS risks from tiny decorative SVGs or ornament-only assets that are unlikely to move surrounding content.

Quality

73%

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/dimensions/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 a well-organized overview with a genuine Check/Fix workflow and a properly signaled one-level reference file. Its weaknesses are redundancy (a verbatim-duplicated CLS paragraph and an Explain section covering what Claude already knows), no inline before/after HTML despite the Fix section requiring it, and verification appearing only as an implicit mention.

Suggestions

Cut the "Explain" section and the duplicated CLS threshold paragraph — Claude already knows this; keep one pointer to the reference's rationale instead.

Add one inline before/after HTML snippet in the Fix section so the demanded output format is demonstrated in the body, or point explicitly to the reference's Code Examples section for it.

Make verification an explicit step in the workflow (e.g. "Verify: enable Layout Shift Regions in DevTools and confirm no movement after the fix") rather than a side mention in the Code Review section.

DimensionReasoningScore

Conciseness

The intro explains CLS thresholds ("A CLS score above 0.1 is considered 'needs improvement'") and the entire "Explain" section teaches browser placeholder behavior Claude already knows ("when a browser parses HTML, it does not yet know an image's dimensions"), while Quick Reference bullets duplicate Fix steps ("Pair with height: auto", "do not set arbitrary"). Mostly efficient, but the unnecessary explanation and duplication mean it could be tightened.

3 / 5

Actionability

Concrete, executable guidance exists ("Report each image missing dimensions with its file path and line number", "width=\"800\" height=\"450\"", "CSS max-width: 100% and height: auto", "use the CSS aspect-ratio property as a fallback") with an explicit low-risk example ("<img src=\"/divider.svg\" alt=\"\" aria-hidden=\"true\">"). The minor gap is that the demanded before/after HTML output has no inline example — all full snippets live in the reference file — which fits mostly-executable guidance with minor gaps rather than the pseudocode/missing-details anchor below.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is present and Fix is numbered 1–5 with skip conditions, but verification is only a side mention ("describe how to confirm the fix in DevTools") rather than an explicit checkpoint in the flow — checkpoints are implicit, matching the anchor for steps listed with validation gaps.

3 / 5

Progressive Disclosure

The bundle structure is sound: the body is a sectioned overview and "see `references/rule.md`" points to an existing file one level deep, clearly signaled at the end. However, the body's intro paragraph is duplicated verbatim in the reference's "Why It Matters" and the Explain section overlaps the reference's "How Browsers Use These Attributes", a minor organization gap that keeps it from a clean split.

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

The description is a solid, third-person, trigger-equipped summary with several concrete review actions and good keyword coverage. Its main weaknesses are an awkward scope clause, a missing statement of the core fix action, and absent common synonyms like "image dimensions" and "layout shift".

Suggestions

State the central capability explicitly, e.g. "Flags and fixes <img> elements missing width and height attributes" instead of only describing review checks.

Add natural trigger synonyms such as "image dimensions", "layout shift", and "Core Web Vitals/CLS" that users would actually say.

Rewrite the opening scope clause so the rule name is integrated naturally rather than appearing as a mid-sentence title ("related to Set explicit width and height on images").

DimensionReasoningScore

Specificity

"Check encoded size, rendered size, loading strategy, and above-the-fold impact together" and "Separate real CLS risks from tiny decorative SVGs" list several concrete review actions, but the opening clause "reviewing image assets, markup, and CDN or build transforms related to Set explicit width and height on images" describes scope awkwardly and the core fix action (adding width/height attributes) is never stated — minor gaps keep it below comprehensive.

4 / 5

Completeness

Both parts are present: the when-clause "Use when reviewing image assets, markup, and CDN or build transforms" is explicit, and the what is given as the check/separate actions. However, the what describes review checks without naming the skill's central capability of flagging and fixing images missing width/height attributes, so the what/when pair is solid but not fully concrete.

4 / 5

Trigger Term Quality

Natural terms like "image assets", "markup", "width and height", "CLS risks", "decorative SVGs", and "above-the-fold" are present, but common synonyms users would say — "image dimensions", "layout shift" (only implied via "move surrounding content"), "aspect ratio", "Core Web Vitals" — are missing, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (image dimension/CLS review) with concrete differentiators ("tiny decorative SVGs or ornament-only assets"), but phrases like "loading strategy" and "CDN or build transforms" overlap with sibling image-optimization skills such as format choice or lazy loading — mostly distinct with minor overlap risk.

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