CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

77%

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

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 body for a simple accessibility rule, with an excellent one-level reference split to references/rule.md. Its weakness is redundancy: the alt-attribute instruction is repeated across Quick Reference, Check, and Fix, and the Code Review paragraph restates the frontmatter description as boilerplate rather than adding guidance.

Suggestions

Collapse the Quick Reference / Check / Fix overlap into a single Check-and-Fix statement (verify non-empty alt on every <input type='image'>; describe the action, e.g. 'Search', 'Submit').

Replace the Code Review boilerplate paragraph with a concrete example of a flagged violation (e.g. <input type="image" src="go.png"> missing alt) or delete it, since it restates the frontmatter description.

Trim or move the opening screen-reader rationale to references/rule.md — it explains a concept Claude already knows.

DimensionReasoningScore

Conciseness

The same instruction appears three times — "Add an `alt` attribute to `<input type='image'>`" (Quick Reference), "Verify that all <input type='image'> elements have a non-empty 'alt' attribute" (Check), and the Fix section restating it — and the Code Review paragraph ("Review the rendered markup and interactive states that affect Provide alt text for image buttons...") duplicates the frontmatter description almost verbatim. Mostly efficient, but the redundancy across Quick Reference/Check/Fix plus the boilerplate paragraph goes beyond the 'minor instances that could be trimmed' of a 4, while the body is still far from the padded verbosity of a 2.

3 / 5

Actionability

Concrete, executable guidance is present: "Verify that all <input type='image'> elements have a non-empty 'alt' attribute" and "Add an 'alt' attribute ... that describes the action performed when the button is clicked (e.g., 'Search', 'Submit')", with markup examples correctly deferred to references/rule.md (no penalty for absent code in an instruction-only skill per the scoring note). Not 5 because the 'Explain' and 'Code Review' sections give process-generic direction ("Flag exact elements, roles, labels...") with no inline concrete example of a flagged violation.

4 / 5

Workflow Clarity

For this simple single-purpose rule the Check -> Fix flow is unambiguous, and verification is addressed ("note how to verify the fix with browser accessibility tooling or assistive tech", expanded by the Verification section in references/rule.md). Not 5 because the trailing 'Code Review' section re-describes the whole review process after Fix, blurring whether it precedes or follows the fix step, and no explicit validation checkpoint links Check to Fix.

4 / 5

Progressive Disclosure

The ~30-line body is well organized into labeled sections and points to exactly one clearly-signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — which exists, contains the code examples and verification steps, and itself contains no further nested local references. The split (check/fix overview in SKILL.md, examples and detail in the reference) is appropriate for a simple skill under 50 lines.

5 / 5

Total

16

/

20

Passed

Description

75%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.

A solid description with an explicit 'Use when' trigger and several concrete inspection actions anchored to a specific accessibility rule. Its main weakness is that the 'what' is generic review-process boilerplate — it never states the skill's core capability of verifying and fixing the alt attribute on image buttons, and it omits the word 'accessibility' and the input type='image' trigger term.

Suggestions

State the core capability explicitly, e.g. "Verifies and fixes the alt attribute on <input type='image'> elements so the button's action is announced to assistive technology."

Add missing natural trigger terms: "accessibility", "input type='image'", and "form buttons" as synonyms for image buttons.

Trim the generic inspection list (keyboard behavior, focus flow) to what this rule actually involves, since this is a single-rule alt-text check, not a broad a11y audit.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — alongside a named domain ("Provide alt text for image buttons"). It falls short of 5 because the core remediation capability (adding/verifying a descriptive alt attribute on <input type='image'>) is never stated, but it exceeds 3's '1-2 concrete actions' bar.

4 / 5

Completeness

Both halves are explicit: 'when' via "Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide alt text for image buttons" and 'what' via "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output". Not 5 because the 'what' describes a generic review process rather than the skill's actual fix (add action-describing alt text), and the 'when' leans on boilerplate triggers.

4 / 5

Trigger Term Quality

Natural user phrases are present — "alt text", "image buttons", "rendered HTML", "screen-reader" — giving good keyword coverage. Not 5: common variations are missing, including the word "accessibility" itself, the selector "input type='image'", and synonyms like "form button" or "accessible name" as a trigger term.

4 / 5

Distinctiveness Conflict Risk

The named rule ("Provide alt text for image buttons") carves a clear niche with minimal conflict risk against unrelated skills. Not 5: the broad when-clause ("reviewing rendered HTML, interactive components, or design-system patterns") is shared boilerplate that would also fire for sibling accessibility-rule skills (e.g., decorative-image alt rules), so minor overlap risk remains.

4 / 5

Total

16

/

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/input-image-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.