CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

71%

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/text-in-images/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-sectioned overview (Quick Reference / Check / Fix / Explain / Code Review) that appropriately defers code examples to a single, clearly signaled, one-level-deep reference file. The weaknesses are the accessibility rationale stated three times across sections and a generic Code Review section whose steps (keyboard, focus) are irrelevant to a text-versus-image rule.

Suggestions

State the accessibility rationale once — keep the intro or the Quick Reference bullet and cut the Explain section that restates the same three facts.

Rewrite the Code Review section for this rule (flag <img> or CSS-background elements rendering readable text, check alt equivalents) instead of generic keyboard/focus boilerplate.

Mention the exceptions (logos, decorative typography, essential visual rendering) in one place only — they currently appear in both Quick Reference and Check.

DimensionReasoningScore

Conciseness

The same rationale is stated three times: the intro ("Text in images can't be resized by users with low vision, translated automatically, read by screen readers without alt text, or reflowed when zoomed"), a Quick Reference bullet ("Images of text can't be resized, translated, or read by screen readers"), and the Explain section ("Explain how images of text cannot be resized by users, are not readable by screen readers without alt text, cannot reflow on zoom" — restating the same facts). The Code Review section is also boilerplate unrelated to this rule. Mostly efficient but should be tightened; not 2 because the body is short (~35 lines) and not heavily padded, not 4 because the triple redundancy and generic Code Review section are real waste.

3 / 5

Actionability

Concrete, executable directives for an instruction-only skill: "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". Minor gaps: no inline example markup (deferred to references/rule.md) and "Verify the text could not be presented as real HTML text" gives no method. Not 3 because the guidance is specific and actionable rather than pseudocode or vague; not 5 because what a violation looks like is only covered in the reference file.

4 / 5

Workflow Clarity

A coherent Check → Fix → Explain → Code Review sequence for a simple review task, with "Verify the text could not be presented as real HTML text" acting as a checkpoint inside Check. Not a destructive or batch operation, so no validation cap applies. Not 5 because the Code Review section's steps ("keyboard interactions", "focus behavior") do not apply to this rule and muddy the sequence; not 3 because the flow is clearly ordered and unambiguous for the core task.

4 / 5

Progressive Disclosure

The body is a lean overview that defers detail via a clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists, contains exactly the promised code examples and framework guidance, and references no further files. Fits anchor 5 (clear overview, well-signaled one-level-deep references, appropriate split); not 4 because there are no organization gaps for a skill this size.

5 / 5

Total

16

/

20

Passed

Description

58%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 clause and concrete inspection actions, satisfying basic completeness. However, the actions are generic accessibility-review boilerplate that never states what the skill actually does about images of text, and natural trigger terms for this rule are missing. Distinctiveness from sibling accessibility skills relies solely on the awkwardly injected rule name.

Suggestions

Replace the generic boilerplate actions ('inspect keyboard behavior, focus flow, accessible names') with the rule's actual capabilities: identify images containing text and replace them with real HTML text styled with CSS.

Add natural trigger phrases a user would actually say, e.g. 'text in an image', 'image of text', 'banner text rendered as an image', 'alt text for text images'.

Narrow the when-clause to this rule's contexts (images rendering readable text, logos, stylized typography) so it does not compete with every sibling accessibility-review skill.

DimensionReasoningScore

Specificity

Concrete actions are listed ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), but they are generic accessibility-review boilerplate — the skill's own capabilities for this rule (identifying images containing text, replacing with real HTML text, alt attributes) are never stated. Not a 4 because the coverage gap is major rather than 'minor'; not below 3 because the stated actions are specific rather than vague.

3 / 5

Completeness

Both parts are explicit: the when ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid images of text") and the what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"). Not a 5 because the stated 'what' describes generic accessibility inspection misaligned with the rule's actual purpose, and the trigger phrasing is awkward; clearly above 3 since the 'when' clause is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Relevant keywords exist ("reviewing rendered HTML", "interactive components", "design-system patterns", "screen-reader"), but "Avoid images of text" is a rule title, not a phrase a user would naturally say, and common variations like "text in images", "image of text", or "alt text" are missing. Fits anchor 3 ('some relevant keywords but missing common variations or synonyms'); not 4 because key natural terms are absent, not 2 because several relevant terms are present.

3 / 5

Distinctiveness Conflict Risk

The framing ("rendered HTML, interactive components, or design-system patterns" plus "keyboard behavior, focus flow, accessible names, and screen-reader output") would match virtually any sibling accessibility-rule skill; only "related to Avoid images of text" distinguishes it. Fits anchor 3 ('somewhat specific but could still overlap with similar skills'); not 2 because the images-of-text topic provides some specificity, not 4 because the overlap with the broader accessibility-review family is large.

3 / 5

Total

13

/

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