CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

58

Quality

67%

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/retina-display/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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, lean overview that appropriately delegates detail to one reference file, but it leans on concept restatement and named techniques without executable examples or an explicit validation checkpoint in the workflow.

Suggestions

Add at least one minimal executable srcset/image-set snippet in the body so the core fix is actionable without opening the reference.

Replace the generic Check/Explain restatements with a concrete verify step (e.g., toggle DPR in DevTools and confirm the 2x/3x asset loads) to give the workflow an explicit checkpoint.

Drop the "Standard images look blurry…" sentence, which explains a concept Claude already knows.

DimensionReasoningScore

Conciseness

The body is short, but it restates a concept Claude already knows ("Standard images look blurry on retina displays…") and the Check/Explain sections are redundant restatements rather than new information.

2 / 3

Actionability

It names concrete techniques (srcset with x/w descriptors, image-set()) but provides no executable markup or code in the body—all examples are deferred to references/rule.md, leaving the guidance incomplete on its own.

2 / 3

Workflow Clarity

A Check/Fix/Explain/Code Review sequence is present, but there is no explicit validation checkpoint; DevTools confirmation is only loosely mentioned rather than a concrete verify-then-proceed step.

2 / 3

Progressive Disclosure

The SKILL.md is a concise overview that clearly signals a single one-level-deep reference (references/rule.md, verified present) for full implementation details and code examples.

3 / 3

Total

9

/

12

Passed

Description

77%

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 specific and complete with an explicit Use-when trigger and concrete review actions, but its trigger terms are somewhat technical and its broad performance framing creates overlap risk with general image-optimization skills.

Suggestions

Add natural trigger terms users would actually say, e.g. "retina images", "srcset", or "blurry images on high-DPI screens".

Narrow the scope language so it clearly targets retina/high-DPI asset provisioning rather than general image performance (CDN, loading strategy, above-the-fold).

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions—"Check encoded size, rendered size, loading strategy, and above-the-fold impact"—rather than vague language, matching the anchor for listing several specific actions.

3 / 3

Completeness

It explicitly answers both what (check encoded/rendered size, loading strategy, above-the-fold impact) and when via an explicit "Use when reviewing…" trigger clause.

3 / 3

Trigger Term Quality

It includes relevant terms ("high-DPI retina displays", "image assets") but omits common variations a user would naturally say (srcset, retina images, blurry images) and leans technical ("CDN or build transforms", "above-the-fold impact").

2 / 3

Distinctiveness Conflict Risk

The retina/high-DPI niche is identifiable, but the broad framing around image assets, CDN/build transforms, loading strategy, and above-the-fold impact could overlap with general image-performance skills.

2 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.