CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

broken-images

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

Quality

76%

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/broken-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 well-structured overview with strong actionable content: a concrete scan procedure, numbered fixes with an inline copy-paste onerror snippet, a verification method, and an appropriately deferred one-level reference for framework details. Its main weakness is token efficiency — the 'Explain' section and intro duplicate rationale Claude already knows, and the templated 'Code Review' section drifts into optimization concerns foreign to this rule.

Suggestions

Cut or merge the 'Explain' section: the 404/browser-behavior and LCP rationale duplicates the intro paragraph and covers concepts Claude already knows, so the tokens are better spent on the Check/Fix workflow.

Wire the DevTools blocked-request verification into the Fix workflow as an explicit post-fix checkpoint (e.g. 'After applying a fallback, block the image request in DevTools Network tab and confirm the placeholder renders') so the validate-fix-retest loop is a step, not a Quick Reference bullet.

Trim the 'Code Review' section's references to 'format choice, sizing, or loading behavior', which belong to image-optimization rules rather than broken-image detection, and focus it on flagging missing files and missing onerror handlers.

DimensionReasoningScore

Conciseness

The Quick Reference, Check, and Fix sections are tight and high-value, but the 'Explain' section re-explains 404 behavior, console errors, and LCP impact that Claude already knows and duplicates the intro paragraph, and the templated 'Code Review' section adds further padding. Not 4 because a whole section of over-explanation exceeds 'minor instances'; not 2 because the actionable core (~60% of the body) is genuinely lean with no library-tutorial filler.

3 / 5

Actionability

Provides a copy-paste-ready snippet ('onerror="this.src='/images/fallback.png'; this.onerror=null;"'), a fully specified scan procedure with four concrete detection categories and a report format (file path and line number), and a concrete test method (DevTools Network tab blocked requests). Not 5 because the React/Vue ('implement an onError callback') and external-CDN ('consider downloading and self-hosting') cases are direction-level hints rather than executable guidance; not 3 because real executable code and complete procedures are present.

4 / 5

Workflow Clarity

The Check-then-Fix sequence is clear, with numbered identification criteria (1-4) and numbered remediation steps (1-5), and an explicit verification technique ('Test with DevTools Network tab blocked requests to verify fallback behaviour'). Not 5 because verification is not wired into the flow as an ordered post-fix checkpoint with a retest loop; not 3 because the sequence and a concrete validation method are both explicitly present, not merely implicit.

4 / 5

Progressive Disclosure

The ~30-line body is a clear overview with well-organized sections (Quick Reference, Check, Fix), and detailed implementation is split into a single, clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists in the bundle and holds the deferred code examples. This matches the anchor for a clear overview with well-signaled one-level references and easy navigation.

5 / 5

Total

16

/

20

Passed

Description

71%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 clause, the key natural trigger phrase 'broken images', and several concrete actions, placing it solidly above average. Its main weakness is a mismatch between the advertised actions (encoded size, rendered size, loading strategy, above-the-fold impact) and the skill's actual purpose (detecting broken image paths and adding onerror fallbacks), which both weakens accuracy and creates conflict risk with image-optimization skills.

Suggestions

Replace the optimization-check actions ('Check encoded size, rendered size, loading strategy, and above-the-fold impact together') with what the skill actually does, e.g. 'Scan <img> src and CSS background-image URLs for paths pointing to missing files, and add onerror fallbacks that swap to a placeholder image.'

Add natural trigger synonyms such as 'missing images', 'image 404s', or 'images not loading' so users who phrase the problem differently can find the skill.

Rewrite the when clause to reference user situations instead of circularly naming the skill title ('related to Fix broken images'), e.g. 'Use when images fail to load, return 404s, or show the broken-image icon.'

DimensionReasoningScore

Specificity

Lists several concrete actions ('reviewing image assets, markup, and CDN or build transforms', 'Check encoded size, rendered size, loading strategy, and above-the-fold impact together'), matching the score-4 anchor of several specific actions with gaps. Not 5 because the listed actions are image-optimization checks that do not cover the skill's actual capabilities (path validation, onerror fallbacks, broken-image detection); not 3 because well more than 1-2 concrete actions are named.

4 / 5

Completeness

Explicitly answers both 'what' ('Check encoded size, rendered size, loading strategy, and above-the-fold impact together') and 'when' ('Use when reviewing image assets, markup, and CDN or build transforms'). Not 5 because the when clause is circular ('related to Fix broken images' references the skill title rather than user situations) and the what mischaracterizes the skill body; not 3 because both elements are explicitly stated, satisfying the Use-when requirement.

4 / 5

Trigger Term Quality

Contains the natural user phrase 'Fix broken images' plus relevant domain terms ('image assets', 'markup', 'CDN'), giving good keyword coverage. Not 5 because common synonyms users would say are missing ('missing images', 'image 404', 'not loading'); not 3 because the primary natural phrase is present alongside several domain keywords rather than a lone generic term.

4 / 5

Distinctiveness Conflict Risk

The core 'broken images' niche is distinct, but 'Check encoded size, rendered size, loading strategy, and above-the-fold impact together' would plausibly trigger for sibling image-optimization skills (image formats, sizing, lazy loading), creating real overlap. Not 4 because this overlap extends beyond 'closely related skills' to a different task family; not 2 because the broken-images anchor phrase is specific enough to avoid conflict with virtually any skill.

3 / 5

Total

15

/

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/broken-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.