CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

74%

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

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 overview with strong progressive disclosure and actionable good/bad examples, but it carries redundant background explanation and lacks explicit verification checkpoints in the workflow.

Suggestions

Remove or trim the '2.2 billion people' stat and the WCAG explanation in the body since they are repeated in the 'Explain' section and the reference; Claude already knows this context.

Add an explicit verification checkpoint step (e.g., run axe/WAVE or confirm in DevTools) to the body's Check/Fix sequence rather than only in the reference.

Consolidate the overlapping decorative/informative/linked-image guidance so each point appears once across Quick Reference, Check, and Fix instead of being restated in Explain.

DimensionReasoningScore

Conciseness

Mostly efficient but includes background Claude already knows (the '2.2 billion people' stat, repeated WCAG/screen-reader explanations) and restates decorative/informative/linked-image guidance across Quick Reference, Check, Fix, and Explain.

3 / 5

Actionability

Provides concrete, specific guidance with good/bad alt examples ('Bar chart showing 40% increase in sales Q3 2024' vs alt='chart') and explicit flagging criteria; minor gaps only.

4 / 5

Workflow Clarity

Check→Fix→Explain→Code Review gives a recognizable sequence, but validation/verification checkpoints are implicit and relegated to the reference rather than stated as explicit steps in the body.

3 / 5

Progressive Disclosure

Concise overview body with a clearly signaled one-level-deep pointer ('see references/rule.md') that resolves to a real file; content is appropriately split and easy to navigate.

5 / 5

Total

15

/

20

Passed

Description

83%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 is explicit and trigger-anchored with concrete review actions, scoring well on completeness and specificity. Its main weakness is mixing alt-text accessibility framing with image-performance concerns, which slightly raises conflict risk.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Check encoded size, rendered size, loading strategy, and above-the-fold impact') alongside a defined review scope, with only minor coverage gaps relative to the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what (review image assets/markup/transforms and check four sizing/loading properties) and when via a concrete 'Use when reviewing...' trigger phrase.

5 / 5

Trigger Term Quality

Includes the key natural term 'alt text' plus 'image assets', 'markup', and 'CDN or build transforms'; good coverage, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Tied to a clear alt-text niche but the image-performance language ('encoded size', 'loading strategy', 'above-the-fold impact') creates minor overlap risk with image-optimization skills.

4 / 5

Total

17

/

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.