CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

error-images

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

Quality

71%

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/error-images/SKILL.md
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 concise, well-structured overview that correctly defers implementation detail to a real one-level-deep reference file. Its main weakness is actionability: the in-body guidance names techniques but gives no executable specifics, and the Check/Fix sections are one-line directives rather than concrete steps.

Suggestions

Add one minimal executable snippet to the body (e.g. an <img onerror="this.src='/images/placeholder.png'; this.onerror=null;"> example) so the core fix is actionable without opening the reference.

Make the Check section concrete by listing what to look for (onerror handlers, fallback assets, skeleton/loading states, error logging) instead of a single restated directive.

DimensionReasoningScore

Conciseness

The body is lean with no basic-concept explanations, and the single-sentence rationale ("Broken image icons look unprofessional and confuse users") earns its place. Minor over-explanation remains: the one-line "Check", "Fix", and "Explain" sections largely restate their headers, keeping it just below anchor 5.

4 / 5

Actionability

The Quick Reference names concrete mechanisms ("Use onerror to replace broken images with fallbacks", "Consider skeleton loaders", "Log image errors"), but the Check/Fix/Explain sections are vague directives ("Implement fallback images or placeholder content for broken image scenarios") with no executable specifics in the body — all code is deferred to the reference file. This matches anchor 3: some concrete guidance but incomplete.

3 / 5

Workflow Clarity

As a simple single-purpose skill, the Check → Fix → Explain → Code Review structure is clear and unambiguous in intent, with a verification hint ("describe how to confirm the fix in DevTools"). It sits below anchor 5 because the individual steps are single vague sentences with no explicit checkpoints.

4 / 5

Progressive Disclosure

The body is a concise overview with well-signaled, one-level-deep references: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists in the bundle with the full implementation content. The split is clean and navigation is easy, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Description

58%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 has an explicit "Use when..." trigger and concrete-sounding actions, but the actions described (encoded size, rendered size, loading strategy, above-the-fold impact) belong to image-optimization concerns rather than the error-handling this skill covers, and no broken-image or fallback trigger terms appear. The awkward mid-sentence embedding of the rule title further weakens it.

Suggestions

Rewrite the 'what' to describe the skill's actual actions, e.g. "Add onerror fallback images, placeholder content, and skeleton loaders for broken images, and log image load errors for monitoring."

Include natural trigger phrases users would say, such as "broken images", "image fails to load", "fallback image", and "onerror", so the description matches real user phrasing.

Fix the garbled clause "related to Handle image loading errors gracefully" by moving the rule topic into a clean sentence instead of embedding the title mid-clause, and drop the size/above-the-fold metrics that belong to optimization rules.

DimensionReasoningScore

Specificity

The description lists concrete actions ("Check encoded size, rendered size, loading strategy, and above-the-fold impact together"), but these are image-optimization checks rather than the error-handling actions the skill actually performs (onerror fallbacks, placeholder content, error logging). It names the domain with concrete-sounding actions, yet coverage of the skill's real capabilities is absent, matching anchor 3 rather than anchor 4's 'minor gaps'.

3 / 5

Completeness

Both a "what" ("Check encoded size, rendered size, loading strategy, and above-the-fold impact together") and an explicit "Use when..." trigger are present, so it clears the 3 cap. It falls short of anchor 5 because the "what" misdescribes the skill's actual purpose and the when-clause awkwardly embeds the rule title mid-sentence ("related to Handle image loading errors gracefully").

4 / 5

Trigger Term Quality

Some relevant image-domain keywords are present ("image assets", "markup", "CDN or build transforms"), but the natural phrases a user would say when needing this skill — "broken image", "image fails to load", "fallback image", "onerror" — are entirely missing. This matches anchor 3 (some relevant keywords, missing common variations) rather than 2, since the terms are domain-relevant rather than generic.

3 / 5

Distinctiveness Conflict Risk

The stated scope — "reviewing image assets, markup, and CDN or build transforms" plus size and above-the-fold checks — overlaps heavily with sibling image-optimization rules and would likely trigger for the wrong image skill. It is somewhat specific (anchored to the images domain and the named rule) but conflict risk remains, matching anchor 3.

3 / 5

Total

13

/

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/error-images/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.