CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

retina-display

Use when reviewing image assets, markup, and CDN or build transforms related to Support high-DPI retina displays. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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-structured overview with concrete technical directives and an exemplary one-level-deep reference split into references/rule.md. It is held back by redundant templated sections (Check, Explain) and an intro sentence that re-explains a concept Claude already knows, plus a DevTools verification step that is named but never detailed.

Suggestions

Delete the redundant '## Check' section (it restates the first Quick Reference bullet) and the content-free '## Explain' section, whose instruction adds nothing beyond the intro sentence.

Drop or fold the opening sentence about standard images looking blurry on retina displays; Claude already knows this, and the 'why' already lives in references/rule.md.

Inline a minimal executable example under '## Fix' (a 3-line img srcset snippet) and specify the DevTools verification step (e.g., emulating device pixel ratio in Chrome DevTools and checking the Network tab for the @2x/@3x asset), rather than only deferring to the reference file.

DimensionReasoningScore

Conciseness

The intro "Standard images look blurry on retina displays (2x, 3x pixel density)" explains a concept Claude already knows, "## Check" ("Check if high-resolution images are provided for retina displays (2x, 3x)") duplicates the first Quick Reference bullet, and "## Explain" ("Explain how retina images ensure sharp visuals") is a content-free meta-instruction. Mostly efficient, but several sections could be trimmed. Not 4 because there are three distinct instances of unnecessary or redundant content rather than minor over-explanation.

3 / 5

Actionability

"Use srcset with x descriptors for fixed-size images", "Use srcset with w descriptors for responsive images", and "use image-set() or media queries" give concrete, executable directives, and the Code Review section instructs to "Flag exact files or components where format choice, sizing, or loading behavior violates the rule". Not 5 because no code is inlined in the body and DevTools verification is named but never specified (it lives only in the reference file).

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections provide a rough sequence, and the Code Review section gives the primary workflow: review assets/markup/delivery configuration, flag exact files, and "describe how to confirm the fix in DevTools". Not 5 because how the Check/Fix/Explain sections relate to the Code Review protocol is implicit, and the DevTools verification checkpoint is referenced but unspecified.

4 / 5

Progressive Disclosure

The body is a concise overview (Quick Reference bullets) with a clearly signaled, purpose-stated one-level reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`". The bundle matches this exactly: references/rule.md exists and contains the code examples and framework guidance (React, Next.js, Sharp) with no further nested references. Not 4 because the split, signaling, and actual file structure are all fully appropriate.

5 / 5

Total

16

/

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.

The description explicitly covers both what the skill does and when to use it, with concrete review targets and checking dimensions and natural trigger terms around retina/high-DPI work. Its only real weakness is the awkwardly pasted rule title "related to Support high-DPI retina displays", which slightly muddies the trigger phrasing.

DimensionReasoningScore

Specificity

"reviewing image assets, markup, and CDN or build transforms" and "Check encoded size, rendered size, loading strategy, and above-the-fold impact together" list several concrete actions with named targets. Not 5 because the boilerplate fragment "related to Support high-DPI retina displays" reads as a pasted title rather than a stated action, and follow-up actions (flagging/fixing) are only implied.

4 / 5

Completeness

Both parts are explicit: the "when" ("Use when reviewing image assets, markup, and CDN or build transforms related to ... high-DPI retina displays") and the "what" ("Check encoded size, rendered size, loading strategy, and above-the-fold impact together") with concrete trigger phrases. Not 4 because the when-clause is more specific than anchor 4's generic 'Use when working with X' pattern.

5 / 5

Trigger Term Quality

Natural terms like "retina displays", "high-DPI", "image assets", and "CDN or build transforms" are present, matching what a user would say. Not 5 because common variations such as "srcset", "responsive images", "image-set", or "pixel density" are absent.

4 / 5

Distinctiveness Conflict Risk

"retina displays" and "high-DPI" carve out a clear niche with distinct triggers. Not 5 because the checking metrics ("encoded size, rendered size, loading strategy, above-the-fold impact") look like a shared template that sibling image-rule skills (lazy loading, compression, format choice) would also use, creating minor overlap risk.

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/retina-display/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.