CtrlK
BlogDocsLog inGet started
Tessl Logo

input-image-alt

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

63

Quality

75%

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/input-image-alt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 skill body is a well-structured, concise overview that defers detail to a single one-level-deep reference file, with actionable Check/Fix guidance. The main improvement areas are minor redundancy in the Quick Reference and a verification checkpoint that is only hinted at rather than explicit.

Suggestions

Collapse the Quick Reference bullets into the Check/Fix sections to remove the restatement and tighten the body further.

Promote the verification step into an explicit '## Verify' section (e.g., 'Confirm the alt text appears as the accessible name in the browser accessibility tree') rather than burying it in the Code Review prose.

Add one inline correct/incorrect code snippet in the Fix section so the actionable guidance is copy-paste ready without requiring a jump to the reference.

DimensionReasoningScore

Conciseness

The body is lean and sectioned, but the Quick Reference bullets restate the Check/Fix content and the opening line explains a concept Claude already knows ('Without alt text, screen readers may read the file name…'), minor padding that could be trimmed.

4 / 5

Actionability

Gives concrete, executable guidance ('Add an alt attribute to <input type="image"> that describes the action… e.g., Search, Submit'); no inline code block, but as an instruction-only skill the guidance is actionable with only minor gaps.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear for a simple single-purpose skill, and the Code Review section hints at verification ('note how to verify the fix with browser accessibility tooling'), though the verification checkpoint is only weakly stated and deferred to references.

4 / 5

Progressive Disclosure

The body is a concise overview with a clearly signaled one-level-deep reference ('see references/rule.md') for full details and code examples; the referenced file exists and navigation is straightforward.

5 / 5

Total

17

/

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 clearly states when to use the skill and what to inspect, with concrete natural-language triggers. Its main weakness is distinctiveness: the broad opening trigger phrase could fire for sibling accessibility skills in the same family.

Suggestions

Lead with the rule-specific trigger (e.g., 'Use when reviewing <input type="image"> buttons for missing or non-action alt text') before the generic review phrasing to reduce overlap with sibling accessibility skills.

Tighten the 'what' into a capability statement (e.g., 'Audits image-button alt text for presence and action-orientation') rather than only an inspection checklist.

Add common synonyms users might say ('image submit button', 'form image button', 'alt attribute') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete inspection actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'when' ('Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide alt text for image buttons') and 'what' (the inspection checklist), though the 'what' is a process list rather than a capability summary.

4 / 5

Trigger Term Quality

Includes natural terms a reviewer would say ('alt text', 'image buttons', 'rendered HTML', 'accessible names', 'screen-reader'); a few synonyms or phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

It narrows to image buttons, but the opening trigger ('reviewing rendered HTML, interactive components, or design-system patterns') is generic boilerplate likely shared across a family of accessibility skills, creating real overlap risk.

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.

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.