CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sprite-generation

Use when reviewing image assets, markup, and CDN or build transforms related to Use image sprites where appropriate. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.

Quality

69%

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/sprite-generation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 well-structured and defers implementation detail to a single clearly signaled reference, but the visible content is padded and vague: one known-to-Claude fact is restated in three sections, and the Check/Fix guidance lacks any concrete steps or tools. The result reads as a template wrapper around the reference rather than a lean, actionable overview.

Suggestions

Delete the 'Quick Reference' section and fold the 'Explain' section into one line — both restate the intro's sprites-vs-HTTP/2 fact, which Claude already knows.

Make 'Check' concrete: specify how to detect the problem (e.g., DevTools Network tab — count separate requests for small images/icons, flag icon sets >3-4 individual files), instead of just restating the rule.

Surface the verification checkpoints from references/rule.md (single sprite request in Network tab, correct background positions, retina rendering) directly into the Check→Fix workflow so the sequence has explicit validation steps.

DimensionReasoningScore

Conciseness

The same single fact — sprites reduce HTTP requests, HTTP/2/SVG reduced the need — is restated three times: in the intro sentence, in the four-bullet 'Quick Reference' section, and again in the 'Explain' section, all concepts Claude already knows. This is several unnecessary explanations/padded sections (not just 'some', so not 3), though the body is short and not severely verbose (not 1).

2 / 5

Actionability

The body gives only high-level hints: 'Create CSS sprites for icons and small images, or migrate to SVG icons' and 'Check if small images and icons are combined into sprites' — no steps, tool names, commands, or code; even the anchor-2 example names a tool. All concrete material (sprite CSS, spritesmith script, DevTools verification) is deferred to references/rule.md, leaving minimal executable guidance in the body itself.

2 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections list a rough sequence, but validation is only gestured at ('describe how to confirm the fix in DevTools') with the actual checkpoints living in references/rule.md's Verification section, so checkpoints are missing/implicit in the body. Not 4 (no explicit checkpoints present); not 2 (each step is defined per section, not poorly defined).

3 / 5

Progressive Disclosure

The short, well-sectioned body cleanly defers detail through one clearly signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — which exists, contains the implementation material, and introduces no further nested references. Appropriate split and easy navigation.

5 / 5

Total

12

/

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' clause, concrete trigger contexts, and four specific check dimensions. Its main flaw is the awkward run-on embedding of the rule title ('related to Use image sprites where appropriate') in place of a cleanly phrased capability statement, plus missing common synonyms like 'CSS sprite' or 'SVG icons'.

DimensionReasoningScore

Specificity

The description names 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' — but coverage is review/check-only and the embedded rule title 'related to Use image sprites where appropriate' garbles the action statement, so it is not fully comprehensive (not 5).

4 / 5

Completeness

Both parts are explicit: 'Use when reviewing image assets, markup, and CDN or build transforms...' states when with concrete trigger contexts, and 'Check encoded size, rendered size, loading strategy, and above-the-fold impact together' states what. Not 4, because the 'when' clause is explicit and specific rather than weakly implied or generic.

5 / 5

Trigger Term Quality

Natural terms users would say are present: 'image assets', 'markup', 'CDN or build transforms', 'image sprites', 'above-the-fold', 'loading strategy'. Common variations like 'CSS sprite', 'sprite sheet', 'SVG icons', or 'HTTP requests' are missing, keeping it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The sprite-review niche is stated ('Use image sprites where appropriate'), but broad phrases like 'loading strategy' and 'above-the-fold impact' overlap with closely related image-performance skills (lazy loading, format optimization). Not 5 due to this shared trigger phrasing; not 3 because the sprite focus clearly distinguishes it.

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/sprite-generation/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.