alt-text

Use when reviewing image assets, markup, and CDN or build transforms related to Provide meaningful alt text for images. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.

Quality

68%

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/alt-text/SKILL.md

Quality

Content

65%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 body is a well-structured, actionable overview with exemplary progressive disclosure into references/rule.md, but it is held back by duplicated motivation content between the intro and 'Explain' sections and by the absence of an explicit verification step for what is a batch codebase-editing workflow.

Suggestions

Deduplicate the accessibility motivation: the opening paragraph and the 'Explain' section repeat the same 2.2-billion and WCAG 1.1.1 content — keep it in one place only.

Add an explicit verification checkpoint after 'Fix' (e.g., 'Verify: run axe DevTools or Lighthouse accessibility audit; re-scan for any <img> without meaningful alt'), since the workflow edits many files across a codebase.

Provide a concrete scan command (e.g., a grep pattern for <img> tags) in the 'Check' section so the audit step is fully executable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight Quick Reference / Check / Fix sections, but the opening paragraph and the 'Explain' section are near-duplicates (both repeat the 2.2-billion statistic and WCAG 1.1.1 wording), and 'Check' and 'Fix' enumerate overlapping cases. Matches the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Concrete, specific guidance throughout: exact flag patterns (alt="photo1.jpg", alt="image") and concrete fix examples (alt="Bar chart showing 40% increase in sales Q3 2024", alt="", aria-describedby). As an instruction-only skill the absence of code blocks is not penalized; minor gaps (no grep/scan command) keep it below fully-executable.	4 / 5
Workflow Clarity	Check → Fix → Explain → Code Review is a clear sequence, but the workflow involves scanning and editing images across a codebase (a batch operation) with no explicit validation/verification step in the body — only the vague 'describe how to confirm the fix in DevTools'. Per the batch-operation cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The body is a well-organized overview with clear sections and a single, clearly signaled one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that points to a real file. Content is appropriately split between overview and details.	5 / 5
	Total	15 / 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 has an explicit 'Use when...' trigger and names concrete actions with the key term 'alt text', but its second sentence (encoded size, rendered size, loading strategy, above-the-fold impact) is off-topic for an alt-text skill, creating overlap risk with image-optimization skills and blurring the 'what'. Dropping or rewording that sentence would lift all four dimensions.

Suggestions

Remove or reframe the 'Check encoded size, rendered size, loading strategy, and above-the-fold impact' sentence — it describes image performance optimization, not alt text, and creates conflict risk with image-optimization skills.

Add natural trigger synonyms such as 'accessibility', 'screen reader', 'a11y', or 'WCAG' so users phrasing the need in accessibility terms match this skill.

Make the 'what' explicit and on-topic, e.g. 'Audit <img> elements for meaningful alt text (decorative, informative, linked, and complex images). Use when reviewing image markup or accessibility.'

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("reviewing image assets, markup, and CDN or build transforms", "Check encoded size, rendered size, loading strategy, and above-the-fold impact together"), matching the several-specific-actions anchor. Not 5 because the size/loading checks drift off-topic from alt text, muddying the action set.	4 / 5
Completeness	Explicitly answers both what ("reviewing image assets, markup, and CDN or build transforms related to Provide meaningful alt text for images") and when ("Use when reviewing..."). The 'what' is weakened by the off-topic "Check encoded size..." sentence, so the fully-explicit-concrete anchor (5) is not met.	4 / 5
Trigger Term Quality	Contains the core natural terms users would say ("alt text", "images", "markup", "CDN or build transforms") with good coverage. Missing common synonyms like "accessibility", "screen reader", "a11y", or "WCAG", so it falls short of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	The alt-text framing is distinct, but "Check encoded size, rendered size, loading strategy, and above-the-fold impact together" reads like an image-optimization/performance skill description and would overlap with such skills. It is somewhat specific yet still invites conflicts with closely related skills, matching anchor 3 rather than 4.	3 / 5
	Total	15 / 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/alt-text/SKILL.md
Commit: 7bfd868

Reviewed: 1 day 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.