CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

text-resizing

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Support text resizing to 200%. 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/text-resizing/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 well-structured overview with exemplary progressive disclosure and actionable check/fix guidance for a single-purpose review skill. The main weakness is token efficiency: the same three points (rem/em units, fixed-height containers, 200% testing) are restated across Quick Reference, Check, Fix, and Explain, and the templated Explain/Code Review sections add little text-resize-specific value.

Suggestions

Consolidate Quick Reference, Check, and Fix into a single section — the rem/em, fixed-height-container, and 200% testing guidance is currently stated three to four times in slightly different wording.

Trim or drop the "Explain" section (explaining a fix is a default capability) and rewrite "Code Review" to reference text-resize specifics (relative units, clipping containers, truncation) instead of generic keyboard/screen-reader boilerplate.

Surface the single most commonly missed testing nuance from references/rule.md in the body — that WCAG requires text-only resize, not Ctrl+Plus browser zoom — since it changes how the check is performed.

DimensionReasoningScore

Conciseness

The same guidance is restated across sections: "Use rem/em units for font sizes instead of fixed px" (Quick Reference) vs "Use relative units (rem, em) for font sizes instead of fixed pixels" (Fix), and "Test at 200% zoom—all content should remain visible" vs "Test with browser text-size preferences". This matches anchor 3's "could be tightened"; it is not 2 because there is no explanation of concepts Claude already knows and total length is short.

3 / 5

Actionability

"Resize text to 200% using browser text-only zoom settings and verify no content is clipped, truncated, or overlaps" and "Use relative units (rem, em)... Avoid fixed-height containers that clip overflowing text" are specific, directive instructions with concrete pass criteria, fitting anchor 4 for an instruction-only skill. It is not 5 because the concrete CSS examples and per-browser test steps exist only in the reference, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear sequence with verification criteria ("verify no content is clipped, truncated, or overlaps", "note how to verify the fix with browser accessibility tooling"), matching anchor 4. It is not 5 because there is no explicit re-test/feedback loop after applying fixes, though as a non-destructive review skill no validation cap applies.

4 / 5

Progressive Disclosure

The body is a lean overview and defers detail via a well-signaled one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`". The referenced file exists as the bundle's only reference and itself contains no further nested references, matching anchor 5's clear overview with appropriately split content.

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, well-formed trigger clause and several concrete actions. Its main weakness is that the what-clause describes generic accessibility inspection (keyboard, focus, screen readers) rather than the skill's actual text-resizing function, and it misses natural synonyms such as "zoom" and "font size".

Suggestions

Replace the generic action list with text-resize-specific actions, e.g. "Check font sizes use rem/em instead of fixed px, verify containers grow instead of clipping at 200% text-only zoom, and flag truncation patterns".

Add natural trigger synonyms users would actually say, such as "zoom", "text size", "font size", or "low vision", to improve trigger-term coverage toward anchor 5.

DimensionReasoningScore

Specificity

"Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant" lists several concrete inspection actions, matching anchor 4. It falls short of 5 because none of the actions are specific to text resizing (no rem/em audit or 200% zoom testing), and exceeds 3 because coverage goes beyond 1-2 actions.

4 / 5

Completeness

The explicit when clause ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to Support text resizing to 200%") and a present what clause satisfy anchor 4. It stays below 5 because the what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") is generic accessibility-review boilerplate that does not describe the skill's actual text-resize checks.

4 / 5

Trigger Term Quality

"text resizing to 200%", "rendered HTML", "interactive components", and "design-system patterns" are natural terms a user reviewing accessibility would say, fitting anchor 4's good coverage. It is not 5 because common variations like "zoom", "font size", and "text size" are missing, though coverage is clearly richer than anchor 3's sparse keywords.

4 / 5

Distinctiveness Conflict Risk

"text resizing to 200%" is a clear niche trigger with minimal conflict risk, matching anchor 4's "mostly distinct". The surrounding generic phrasing ("interactive components", "design-system patterns", "screen-reader output") creates minor overlap risk with closely related accessibility skills, keeping it below 5.

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/text-resizing/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.