CtrlK
BlogDocsLog inGet started
Tessl Logo

zoom-reflow

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Support content reflow at 400% zoom. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

60

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/zoom-reflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized and properly delegates detail to a real reference file, but the core guidance is abstract and lacks an explicit validation loop after fixing. Tightening redundancy and adding a concrete re-test step would lift the weakest dimensions.

Suggestions

Add an explicit verify-after-fix step (e.g., re-zoom to 400% and confirm no horizontal scroll) to close the Check→Fix loop and raise workflow_clarity.

Replace vague fixes like "Test with CSS media queries" with a concrete, executable example or specific tooling command to improve actionability.

Trim the redundant rationale between the opening sentence, Quick Reference, and Explain section so each token earns its place.

DimensionReasoningScore

Conciseness

Mostly efficient with organized sections, but the opening low-vision rationale and the Quick Reference bullets restate content from the Check/Fix sections, and the Explain section repeats the why — minor redundancy a tighter version would drop, fitting the score-2 anchor.

2 / 3

Actionability

Concrete direction exists ("Zoom the browser to 400%", "Use relative units (rem, em, %)") but it stops short of executable, copy-paste-ready steps or specific tooling commands; "Test with CSS media queries" is vague, matching the score-2 anchor of some concrete but incomplete guidance.

2 / 3

Workflow Clarity

Check/Fix/Explain/Code Review imply a loose sequence but lack numbered steps or an explicit verify-after-fix checkpoint — the "note how to verify the fix" line is not an actionable validation loop, matching the score-2 anchor of sequence present but checkpoints missing.

2 / 3

Progressive Disclosure

Short, well-organized body with clearly signaled one-level-deep reference to references/rule.md (verified to exist), matching the score-3 anchor for a simple skill with clear navigation.

3 / 3

Total

9

/

12

Passed

Description

85%

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 clause and a clear niche, answering both what and when. It loses a point on trigger-term quality for technical phrasing that some users would not naturally say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "reviewing rendered HTML, interactive components, or design-system patterns", "Check native semantics first", "inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — matching the score-3 anchor of several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (reviewing rendered HTML/components, checking semantics, keyboard, focus, accessible names, screen-reader) and when via the "Use when reviewing..." clause, matching the score-3 anchor of clearly answering both with explicit triggers.

3 / 3

Trigger Term Quality

Relevant accessibility terms appear ("400% zoom", "content reflow", "keyboard behavior", "screen-reader output") but phrasing leans technical ("native semantics", "accessible names", "design-system patterns") and lacks common lay variations, fitting the score-2 anchor of some relevant keywords with missing variations.

2 / 3

Distinctiveness Conflict Risk

Scoped to "Support content reflow at 400% zoom" — a clear niche with distinct accessibility triggers unlikely to fire for unrelated skills, matching the score-3 anchor.

3 / 3

Total

11

/

12

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.