CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

image-redundant-alt

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid redundant image alternative text. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

73%

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-redundant-alt/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.

A lean, well-structured single-purpose skill with concrete check/fix instructions and exemplary progressive disclosure through a real, well-signaled reference file. Its weaknesses are modest redundancy: the Explain section covers knowledge Claude already has and the generic Code Review paragraph restates the Check section.

Suggestions

Drop or fold the "Explain" section into the reference file — the fact that screen readers pre-announce 'graphic' is knowledge Claude already has and is duplicated in references/rule.md's "Why It Matters".

Replace the generic "Code Review" boilerplate paragraph with rule-specific review guidance (e.g. what element/attribute to flag and how), since it currently restates the "Check" section in vaguer terms.

Add one inline before/after alt attribute example in the body so the common cases are covered without opening the reference.

DimensionReasoningScore

Conciseness

The body is short and mostly lean, but the "Explain" section ("screen readers already announce 'graphic' or 'image'") teaches a concept Claude already knows and duplicates the reference file's "Why It Matters", and the "Code Review" paragraph is generic boilerplate overlapping the "Check" section.

3 / 5

Actionability

"Scan image alt attributes for redundant phrases like 'image of', 'photo of', or text that duplicates surrounding content" and "Remove redundant phrases from the alt attribute" are concrete, executable instructions with exact patterns named; the minor gap is that before/after examples live only in the reference file.

4 / 5

Workflow Clarity

The Check → Fix → Explain sequence is clear for a single-task skill and verification is mentioned ("note how to verify the fix with browser accessibility tooling"), but explicit validation steps are delegated to the reference rather than stated inline, matching 'clear sequence with minor validation gaps' rather than anchor 5.

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and one clearly signaled, one-level-deep reference ("see `references/rule.md`") that exists and contains the promised code examples and framework guidance — no nested references.

5 / 5

Total

16

/

20

Passed

Description

63%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 several concrete actions, but the actions are generic accessibility-review boilerplate misaligned with the rule's actual purpose, and the most natural trigger terms (alt text, alt attribute) are absent. It reads like a template applied across many a11y rules rather than a description tailored to this one.

Suggestions

Add natural trigger terms users would say, e.g. "Use when the user mentions alt text, image alt attributes, or accessibility review of images".

State the core capability of this specific rule, e.g. "Flags and fixes redundant image alt text such as 'image of...' or alt text duplicating adjacent content", instead of only generic inspection actions.

Trim the generic keyboard/focus/screen-reader action list, which overlaps heavily with sibling accessibility-rule skills and raises conflict risk.

DimensionReasoningScore

Specificity

Lists several concrete inspection actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") but never states the core action for this rule — flagging or fixing redundant alt text — leaving a coverage gap that keeps it below anchor 5.

4 / 5

Completeness

An explicit "Use when..." trigger is present, and the 'what' is stated through concrete inspection actions, though those actions are generic a11y-review steps rather than the rule's core capability, so it does not reach the fully explicit anchor 5.

4 / 5

Trigger Term Quality

Domain keywords like "reviewing rendered HTML", "interactive components", and "screen-reader output" are present, but the natural phrases a user would actually say ("alt text", "image alt attribute", "accessibility review") are missing, matching the 'missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The boilerplate action list ("keyboard behavior, focus flow, accessible names") would equally trigger sibling accessibility skills; only the embedded rule name "Avoid redundant image alternative text" distinguishes it, matching the 'somewhat specific but could still overlap' anchor.

3 / 5

Total

14

/

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-redundant-alt/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.