CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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-structured body with a clear single-purpose workflow and excellent one-level-deep reference handling (details correctly deferred to references/rule.md). The main weakness is redundancy — the low-vision rationale appears twice and the Quick Reference bullets duplicate Check/Fix content — and Fix guidance that stays directional rather than concrete at point of use.

Suggestions

Merge the intro paragraph and the Explain section into one statement of the low-vision rationale; stating it twice is redundant padding.

Fold the Quick Reference bullets into Check/Fix (or keep the bullets and trim the sections) so the same criteria (single column, no horizontal scrolling, relative units) are not repeated three times.

Add one minimal inline bad/good CSS snippet in the Fix section (e.g., width: 1200px vs. width: 100%; max-width: 1200px) or point to references/rule.md there, so the fix guidance is concrete at the point of use instead of purely directional.

DimensionReasoningScore

Conciseness

The body is short but noticeably redundant: the intro ('Users with low vision zoom to 400%... horizontal scrolling... makes it impossible to track lines') and the Explain section repeat the same rationale, and the Quick Reference bullets overlap heavily with the Check and Fix sections. Mostly efficient but could be tightened by merging these, matching the 'some unnecessary explanation or could be tightened' anchor rather than 4's 'minor instances'.

3 / 5

Actionability

The Check section gives an executable procedure ('Zoom the browser to 400% and verify content reflows to a single column without horizontal scrolling, truncation, or overlapping elements') and the Fix section names specific techniques ('relative units (rem, em, %) instead of fixed pixels', 'CSS media queries'). As an instruction-only skill the absent inline code is acceptable per scoring notes, but the Fix guidance stays directional with no inline example or pointer at point-of-use, keeping it just below fully copy-paste-ready.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines with an unambiguous flow: Quick Reference (criteria) → Check (verification procedure at 400%) → Fix → Explain → Code Review. No destructive or batch operations, so no validation cap applies, and the check itself serves as the verification checkpoint. The simple-skill exception applies since the single action is unambiguous.

5 / 5

Progressive Disclosure

The body is a concise overview and the single bundle file `references/rule.md` (which exists, 225 lines, containing the CSS code examples) is referenced exactly once, clearly signaled at the end with what it contains ('full implementation details, code examples, and framework-specific guidance'). One level deep, appropriately split, easy navigation — matches the top anchor.

5 / 5

Total

17

/

20

Passed

Description

83%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 strong description with an explicit 'Use when...' trigger clause, concrete review actions, and a distinctive 400% zoom reflow niche. Its main weakness is that the enumerated actions emphasize generic accessibility inspection rather than the skill's actual reflow/responsive-CSS focus, slightly broadening conflict risk and leaving capability coverage incomplete.

DimensionReasoningScore

Specificity

Concrete actions are named: 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — several specific review actions, matching the anchor for several specific actions with minor gaps. Not 5 because the listed actions skew toward generic accessibility review and omit the skill's core capability (responsive CSS fixes with relative units), leaving coverage incomplete.

4 / 5

Completeness

Both parts are explicit: the 'what' is 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' and the 'when' is an explicit 'Use when reviewing rendered HTML, interactive components, or design-system patterns related to Support content reflow at 400% zoom' with concrete trigger phrases. This matches the anchor for clearly answering both what and when; a 4 would require the when to be less explicit than it is.

5 / 5

Trigger Term Quality

Natural trigger phrases include 'content reflow at 400% zoom', 'reviewing rendered HTML', 'interactive components', and 'screen-reader output' — good keyword coverage a user would plausibly say. Not 5 because common variations like 'horizontal scrolling', 'responsive layout', 'viewport', 'magnification', or 'low vision' are missing.

4 / 5

Distinctiveness Conflict Risk

The niche 'Support content reflow at 400% zoom' is distinct with a clear primary trigger, but the secondary action list ('keyboard behavior, focus flow, accessible names, and screen-reader output') overlaps with dedicated keyboard/focus/screen-reader accessibility skills, creating minor conflict risk. Not 3 because the 400% zoom reflow trigger remains the dominant, distinguishing signal.

4 / 5

Total

17

/

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/zoom-reflow/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.