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.

63

Quality

75%

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

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 content is a well-organized, concise overview that delegates detailed code to a real one-level-deep reference file, scoring strongly on progressive disclosure and actionability. Minor improvements could make validation checkpoints more explicit and trim the small amount of framing prose.

DimensionReasoningScore

Conciseness

The body is lean with tight Quick Reference bullets and clearly scoped sections; only mild framing in the opening sentence and the 'Explain' section could be trimmed, so it sits just below a 5.

4 / 5

Actionability

Gives concrete, actionable guidance ('Zoom the browser to 400% and verify content reflows...', 'Use responsive CSS with relative units (rem, em, %)'), with executable code deferred to the reference file; minor gaps in body-level test commands keep it at 4.

4 / 5

Workflow Clarity

The Check/Fix/Explain/Code Review sections provide a clear review sequence with a verification procedure, but validation checkpoints are implicit rather than explicit validate-fix-retry loops.

4 / 5

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md') which exists and holds the detailed code examples, matching the well-structured overview anchor.

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 has an explicit 'Use when...' trigger and lists concrete review actions, scoring well on specificity and completeness. Its main weakness is a mismatch between the described actions (generic a11y inspection) and the rule's actual reflow-at-400%-zoom focus, which raises conflict risk with other accessibility skills.

Suggestions

Rewrite the 'what' clause to describe reflow-specific actions (e.g., 'verify content reflows to a single column with no horizontal scrolling at 400% zoom, check for fixed-pixel widths and non-wrapping grids') instead of generic keyboard/focus/screen-reader inspection.

Add natural trigger synonyms such as 'responsive layout', 'horizontal scrolling', and 'zoom level' alongside '400% zoom'.

Tighten distinctiveness by foregrounding the reflow/zoom niche so the description does not read like a general accessibility review skill.

DimensionReasoningScore

Specificity

Lists several concrete review actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), though those actions are somewhat off-topic for a zoom/reflow rule, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (the inspection actions) and 'when' ('Use when reviewing rendered HTML...'), but the 'what' describes general a11y inspection rather than the rule's actual reflow focus, keeping it just below a 5.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('rendered HTML, interactive components, or design-system patterns', '400% zoom') with good coverage, but misses common synonyms like 'responsive' or 'horizontal scroll'.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'Support content reflow at 400% zoom' gives it a niche, but the listed review actions (keyboard, focus, screen-reader) overlap heavily with sibling accessibility skills and could trigger the wrong one.

3 / 5

Total

15

/

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.

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.