text-in-images

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

Quality

75%

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

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 body is a clean, concise overview that appropriately pushes code examples and detail into references/rule.md while keeping actionable Check/Fix guidance inline. Minor gains are possible by adding a brief inline verification checkpoint and removing the small intro/Quick-Reference redundancy.

Dimension	Reasoning	Score
Conciseness	Lean, well-sectioned body that assumes competence and avoids explaining basic concepts; minor redundancy where the opening paragraph and Quick Reference bullets restate the same accessibility limitations.	4 / 5
Actionability	Concrete instruction-only guidance ('Identify images that contain text content', 'Replace text images with real HTML text styled with CSS', 'provide equivalent text in alt attributes', 'Consider using SVG with embedded text'); executable examples are appropriately deferred to references/rule.md.	4 / 5
Workflow Clarity	Clear Check → Fix → Explain → Code Review sequence for a simple single-purpose skill, with a light verification cue ('note how to verify the fix with browser accessibility tooling'); no explicit validation checkpoint in the body itself.	4 / 5
Progressive Disclosure	Concise overview with well-signaled one-level-deep reference ('see references/rule.md'), and the referenced file exists and holds the detailed examples; easy to navigate.	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 includes an explicit trigger and several concrete actions, but it reads like a generic accessibility-review template applied to the images-of-text rule rather than tailored to that specific topic. Tightening the actions to match the rule (real text vs images, alt text, logos/exceptions) would improve specificity and distinctiveness.

Suggestions

Replace the generic a11y-review actions (keyboard behavior, focus flow, accessible names) with rule-specific actions like 'identify images containing text, verify they could be real HTML text, check alt text, and confirm logo/decorative exceptions'.

Add natural synonyms users might say, e.g. 'text in images', 'text as image', or 'image of text', to broaden trigger coverage.

Narrow the 'when' clause so it triggers specifically on images-of-text concerns rather than any rendered-HTML or design-system review.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), though the actions are generic accessibility-review steps rather than tailored to images-of-text.	4 / 5
Completeness	Has an explicit 'Use when reviewing...' trigger and a concrete 'what' via the listed inspection actions; the 'when' could be more specific to the images-of-text scenario rather than generic a11y review.	4 / 5
Trigger Term Quality	Includes natural terms a user might say ('rendered HTML', 'interactive components', 'design-system patterns', 'images of text') with good coverage, but misses common synonyms like 'text in images' or 'text as image'.	4 / 5
Distinctiveness Conflict Risk	Naming 'Avoid images of text' gives it a niche, but the keyboard/focus/semantics/screen-reader language is generic accessibility-review phrasing that would overlap with many other a11y skills.	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/text-in-images/SKILL.md
Commit: 30756a7

Reviewed: 22 days 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.