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

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/image-redundant-alt/SKILL.md

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.

A well-structured, single-purpose accessibility rule skill that cleanly defers detail to a real references/rule.md file; its main weaknesses are generic boilerplate in the Code Review section and the lack of inline executable examples.

Suggestions

Trim the generic 'Code Review' paragraph to alt-text-specific review cues (e.g., inspect <img> alt values and adjacent captions) to reduce token bloat.

Inline one short incorrect/correct alt snippet in the body so the core guidance is actionable without opening the reference file.

Add an explicit verification step such as 'Confirm the fix with an accessibility tree inspection or screen-reader pass' to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with a tight Quick Reference and short Check/Fix/Explain sections, but the 'Code Review' paragraph is generic accessibility boilerplate ('roles, labels, focus behavior, or keyboard interactions') that adds little alt-text-specific value and could be trimmed.	3 / 5
Actionability	Gives concrete directional guidance ('Scan image alt attributes for redundant phrases like image of, photo of') but no inline code or specific review commands; the executable examples are deferred to references/rule.md rather than shown here.	3 / 5
Workflow Clarity	A clear Check -> Fix -> Explain -> Code Review sequence is present, and the Code Review section notes verifying 'with browser accessibility tooling or assistive tech', giving a light validation checkpoint; not a 5 because verification is only briefly mentioned.	4 / 5
Progressive Disclosure	The body is a concise overview that clearly signals a single one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and that file exists with the detailed content, so navigation is easy.	5 / 5
	Total	15 / 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 gives an explicit 'Use when...' trigger and lists concrete inspection actions, but the actions are generic accessibility boilerplate shared across many rules rather than specific to redundant alt text.

Suggestions

Replace the generic inspection checklist with alt-text-specific actions (e.g., 'Scan <img> alt attributes for redundant phrases like image of/photo of and for alt text that duplicates adjacent captions').

Add natural trigger terms users actually say, such as 'alt text', 'alt attribute', and 'image accessibility'.

Tighten the 'when' clause so it triggers specifically on alt-text concerns rather than broad design-system reviews.

Dimension	Reasoning	Score
Specificity	Lists several concrete inspection actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), though these are generic accessibility actions rather than alt-text-specific ones, keeping it below a 5.	4 / 5
Completeness	Explicitly answers both what (review/inspect semantic and accessibility properties) and when ('Use when reviewing rendered HTML, interactive components, or design-system patterns related to...'), with the trigger phrasing slightly generic rather than sharply specific.	4 / 5
Trigger Term Quality	Includes some relevant terms ('rendered HTML, interactive components, or design-system patterns', 'redundant image alternative text') but misses natural variations users would say such as 'alt text', 'alt attribute', or 'accessibility'.	3 / 5
Distinctiveness Conflict Risk	The rule title anchors a niche, but the generic inspection boilerplate ('keyboard behavior, focus flow, accessible names, and screen-reader output') overlaps heavily with sibling accessibility skills, so conflict risk remains.	3 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/image-redundant-alt/SKILL.md
Commit: 30756a7

Reviewed: 23 days ago

Table of Contents

Discovery Implementation Validation

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.