CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

73

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, concise instruction skill with actionable guidance, a clear simple workflow, and clean one-level progressive disclosure to a real reference file.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no concept-padding; sections like 'Scan image alt attributes for redundant phrases like image of, photo of' assume Claude's competence and every section earns its place.

3 / 3

Actionability

As an instruction-only skill it provides concrete, specific guidance ('Remove redundant phrases from the alt attribute and ensure the text provides unique, descriptive information'), and the absence of inline code is not penalized because the guidance is actionable.

3 / 3

Workflow Clarity

This is a simple single-purpose rule, and the Check -> Fix -> Explain -> Code Review sequence is clear and unambiguous, so workflow clarity qualifies for 3 under the simple-skills scoring note; no destructive or batch operation requires validation checkpoints.

3 / 3

Progressive Disclosure

The body is a concise overview with well-organized sections that signals a single one-level-deep reference ('see references/rule.md'), which is a real bundle file, giving easy navigation without nested references.

3 / 3

Total

12

/

12

Passed

Description

82%

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 answers both what and when with good natural trigger terms, but loses specificity points for second-person voice and risks conflict with broader accessibility-review skills due to its generic opening triggers.

Suggestions

Rewrite in third person (e.g., 'Reviews rendered HTML...') to avoid the second-person specificity penalty.

Lead with the distinctive trigger ('redundant image alt text' / 'alt text') rather than broad a11y-review phrasing to reduce overlap with general accessibility skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), which would normally anchor at 3, but it uses second-person voice ('Use when reviewing... you inspect...'), which the rubric penalizes by reducing specificity by 1.

2 / 3

Completeness

It explicitly answers both what ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') and when ('Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid redundant image alternative text').

3 / 3

Trigger Term Quality

It covers natural terms a user would say for this accessibility niche ('rendered HTML', 'interactive components', 'design-system patterns', 'image alternative text', 'accessible names', 'screen-reader'), giving good coverage of natural vocabulary.

3 / 3

Distinctiveness Conflict Risk

Although the named rule is a specific niche, the opening triggers ('reviewing rendered HTML, interactive components, or design-system patterns') are broad and would overlap with general accessibility-review skills, so it could still trigger for the wrong skill.

2 / 3

Total

10

/

12

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.