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

88%

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

Quality

Content

85%

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-organized overview with actionable guidance, a verification checkpoint, and a clean one-level reference to the real references/rule.md file. Its main weakness is redundancy between the Quick Reference and Fix sections plus an off-topic templated Code Review section that dilutes conciseness.

Suggestions

Merge the "Quick Reference" bullets into the Fix section to remove the overlap on rem/em units, fixed-height containers, and 200% testing.

Rewrite the templated "Code Review" section to focus on text-resizing specifics (font-size units, overflow/fixed-height containers, text-only zoom vs Ctrl+Plus) instead of generic roles/labels/keyboard interactions.

Align the Quick Reference wording ("Test at 200% zoom") with the reference's guidance that WCAG requires text resize, not browser zoom, to avoid the zoom-vs-text-resize conflation.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly lean, but the "Quick Reference" bullets and "Fix" section overlap heavily (both cover rem/em units, fixed-height containers, and 200% testing), and the "Code Review" section is templated boilerplate (roles, labels, keyboard interactions) unrelated to text resizing.	2 / 3
Actionability	Provides concrete, executable guidance: "Use rem/em units for font sizes instead of fixed px", "Avoid fixed-height containers that clip text", and "Resize text to 200% using browser text-only zoom settings and verify no content is clipped" — specific units, specific anti-patterns, and a specific test method.	3 / 3
Workflow Clarity	For this simple single-task review skill the Check/Fix/Explain/Code Review sequence is unambiguous, and the Check section provides an explicit verification checkpoint (verify no content is clipped, truncated, or overlaps and that containers expand appropriately).	3 / 3
Progressive Disclosure	The body is a concise overview that clearly signals one-level-deep detail — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that referenced file exists, keeping navigation shallow and easy.	3 / 3
	Total	11 / 12 Passed

Description

92%

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 well-structured with an explicit trigger and concrete actions, scoring high on specificity, trigger quality, and completeness. Its main weakness is that the listed actions are generic accessibility-review boilerplate rather than text-resizing-specific, raising conflict risk with other accessibility skills.

Suggestions

Replace the generic a11y actions (keyboard behavior, focus flow, accessible names, screen-reader output) with text-resizing-specific actions such as checking font-size units (rem/em vs px), fixed-height/overflow containers, and text-only zoom behavior at 200%.

Tighten the trigger so it clearly distinguishes this skill from sibling accessibility rules, e.g. "Use when reviewing CSS font sizing, container sizing, or zoom/reflow behavior for the Support text resizing to 200% rule."

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "reviewing rendered HTML, interactive components, or design-system patterns", "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (review/inspect rendered markup and interactions) and when via the "Use when reviewing rendered HTML... related to Support text resizing to 200%" trigger clause.	3 / 3
Trigger Term Quality	Uses natural terms a user would say when needing this skill — "rendered HTML", "interactive components", "design-system patterns", and "text resizing to 200%" — with good coverage of phrasings.	3 / 3
Distinctiveness Conflict Risk	The rule-specific trigger ("text resizing to 200%") is distinct, but the bulk of the actions — keyboard behavior, focus flow, accessible names, screen-reader output — are generic accessibility-review actions that would apply to many sibling a11y skills, creating overlap risk.	2 / 3
	Total	11 / 12 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-resizing/SKILL.md
Commit: 48405aa

Reviewed: about 7 hours 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.