CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

image-cdn

Use when reviewing image assets, markup, and CDN or build transforms related to Serve images from a CDN. 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/image-cdn/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 brief, well-organized overview for a simple single-purpose review rule, with excellent progressive disclosure via a verified one-level-deep reference. Its weaknesses are moderate: the opening explanation and Quick Reference partially restate concepts Claude already knows, and the Check/Fix guidance names vendors and outcomes but omits the specific steps (e.g., what to inspect in DevTools, sample CDN URL parameters) needed to be fully executable.

Suggestions

Trim or merge the intro sentence and Quick Reference bullets that restate what image CDNs do, keeping only the vendor list and URL-parameter note as genuinely new information.

Make the Check section executable: state concretely what to inspect (e.g., image response URLs for CDN hostnames/transform parameters, Network panel content-type and transfer size, cache headers) instead of the generic 'Verify if images are served from a CDN or image optimization service'.

Add one copy-paste-ready example in the Fix section (e.g., a Cloudinary or Imgix URL with width/format/quality parameters, or a next.config image-loader snippet) so the most common fix is actionable without opening the reference.

DimensionReasoningScore

Conciseness

Quotes: 'Image CDNs automatically optimize, resize, and convert images on-the-fly—delivering the smallest file in the best format without manual processing' explains a concept Claude already knows, and Quick Reference bullets like 'Use image CDN for automatic format conversion (WebP, AVIF)' and 'Generate responsive sizes on-the-fly via URL parameters' largely restate it. Mostly efficient overall, but these sections could be tightened or trimmed.

3 / 5

Actionability

Quotes: 'Configure an image CDN like Cloudinary, Imgix, or Cloudflare Images for automatic optimization' and 'Verify if images are served from a CDN or image optimization service' offer some concrete guidance (specific vendor names, DevTools confirmation target) but no executable steps for how to verify or configure. Incomplete rather than purely high-level, matching the anchor-3 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

Quotes: 'Verify if images are served from a CDN or image optimization service' (Check), 'Configure an image CDN...' (Fix), and 'describe how to confirm the fix in DevTools' (validation checkpoint) give a clear Check→Fix→Confirm flow for this simple, single-purpose skill. Not a 5 because the sections read as parallel modes rather than an explicitly sequenced workflow with an if-then structure; not a 3 because sequence and a DevTools confirmation checkpoint are present and unambiguous.

4 / 5

Progressive Disclosure

Quotes: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — a clearly signaled, one-level-deep pointer, and references/rule.md exists (165 lines) with no further nested references. The body is a concise, well-sectioned overview with content appropriately split, matching the anchor-5 'clear overview with well-signaled one-level-deep references'.

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 that explicitly covers both what the skill does (check encoded size, rendered size, loading strategy, and above-the-fold impact together) and when to use it, with an explicit 'Use when...' clause anchored to a specific rule. Trigger terms are natural and the niche is well-delineated, with only minor gaps in synonym coverage and slight overlap risk against adjacent image-performance skills.

DimensionReasoningScore

Specificity

Quotes: '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 specific review actions with concrete dimensions. Not a 5 because coverage has minor gaps (e.g., format conversion, cache/edge delivery checks are not named as actions); not a 3 because it goes beyond 1-2 actions to enumerate four distinct check dimensions.

4 / 5

Completeness

Quotes: 'Use when reviewing image assets, markup, and CDN or build transforms related to Serve images from a CDN' explicitly answers 'when' with concrete trigger phrases, and 'Check encoded size, rendered size, loading strategy, and above-the-fold impact together' explicitly answers 'what'. Both halves are present, concrete, and specific, matching the anchor-5 example's structure.

5 / 5

Trigger Term Quality

Quotes: 'image assets', 'CDN', 'loading strategy', 'above-the-fold' — natural terms a user reviewing image delivery would plausibly say. Not a 5 because common variations like 'image optimization', 'WebP/AVIF', or 'responsive images' are absent; not a 3 because coverage extends beyond a bare domain mention to several natural phrasings.

4 / 5

Distinctiveness Conflict Risk

Quotes: 'related to Serve images from a CDN' anchors the skill to a specific niche with distinct triggers. Not a 5 because phrases like 'reviewing image assets' and 'loading strategy' could also plausibly trigger closely related image-optimization or lazy-loading skills; not a 3 because the CDN anchoring keeps overlap risk minor.

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/image-cdn/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.