CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

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

67%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.

A well-structured, actionable skill body with a solid verification workflow and a correctly signaled single-level reference. Its main weaknesses are redundant CDN concept restatement across sections and two incomplete code snippets with empty JSX returns.

Suggestions

Remove the redundant 'Why It Matters' restatement of what an image CDN is (already covered in Quick Reference) and trim the 'Benefits of Image CDNs' table to only non-obvious rows.

Fix or remove the empty ProductImage and HeroImage JSX return blocks, which are non-executable placeholders that lower actionability.

Deduplicate between the body and references/rule.md by moving the bulk of the provider/component code examples into the reference and keeping only one quick-start example in SKILL.md.

DimensionReasoningScore

Conciseness

Mostly efficient with sectioned code examples, but it restates the CDN concept in both 'Quick Reference' and 'Why It Matters', and the 'Benefits'/'Popular Image CDNs' tables add tokens that mostly restate what Claude already knows about image CDNs.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready examples (Cloudinary/Imgix URLs, next.config.js, ResponsiveCdnImage, CdnImage), but the ProductImage and HeroImage snippets have empty JSX return blocks that are incomplete and non-executable.

4 / 5

Workflow Clarity

The 'Verification' section gives a clear numbered five-step sequence (check URLs, format negotiation, geo testing, size comparison, cache headers) and the Check/Fix/Explain/Code Review headers order the review work, with only minor checkpoint gaps.

4 / 5

Progressive Disclosure

The body points to a real one-level-deep references/rule.md with a clear 'see references/rule.md' signal and is well sectioned, though substantial code is inlined in the body that overlaps with content in the reference.

4 / 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, specific description with an explicit 'Use when' trigger and concrete review metrics. It is well-scoped to the image-CDN rule with only minor keyword-synonym and overlap gaps.

DimensionReasoningScore

Specificity

Names the domain and several concrete review actions ('Check encoded size, rendered size, loading strategy, and above-the-fold impact together' plus 'reviewing image assets, markup, and CDN or build transforms'), but the actions are all in the review/check family rather than a fully comprehensive action set.

4 / 5

Completeness

Explicitly answers both what (review image assets/markup/CDN transforms and check the four sizing/loading metrics) and when via a concrete 'Use when reviewing... related to Serve images from a CDN' trigger clause.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('image assets', 'markup', 'CDN', 'build transforms', 'loading strategy', 'above-the-fold', 'Serve images from a CDN'), though common synonyms like 'image optimization', 'WebP', 'AVIF', and 'responsive images' are missing.

4 / 5

Distinctiveness Conflict Risk

The image-CDN review niche is clearly scoped and unlikely to fire for unrelated skills, but 'reviewing image assets, markup' has minor overlap risk with general image-optimization or performance skills.

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.

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.