CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

viewport-zoom

Use when applies to any `<meta name='viewport'>` element in HTML documents. Check the `content` attribute for `user-scalable=no`, `user-scalable=0`, `maximum-scale=1`, or `maximum-scale` values less than 2. This is a common mistake in mobile-first templates and CSS frameworks.

Quality

82%

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

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.

A tight, highly actionable rule skill with an exemplary progressive-disclosure structure — a short overview deferring code examples to a real, one-level-deep reference file. Its weaknesses are triplicated WCAG rationale across the intro, Quick Reference, and Explain sections, plus a templated Code Review section that adds little.

Suggestions

Merge the intro paragraph, the WCAG bullet in Quick Reference, and the "Explain" section into one rationale section — the SC 1.4.4 justification and the iOS 10 caveat each currently appear twice.

Cut or concretize the "Code Review" section: as written ("Review stylesheets, component styles, and responsive states related to Do not disable pinch zoom") it restates the Check step in vaguer terms; either drop it or fold its one useful detail (checking CSS `touch-action: none`) into Check.

Delete the duplicated URL line at the bottom (it is already in frontmatter metadata) and keep only the `references/rule.md` pointer to trim remaining tokens.

DimensionReasoningScore

Conciseness

The WCAG 1.4.4 rationale is explained three times — in the intro paragraph ("Low-vision users who rely on browser zoom are entirely blocked"), in Quick Reference ("violating WCAG 2.1 SC 1.4.4"), and again across the entire "Explain" section — and the iOS 10 caveat ("iOS 10+ ignores `user-scalable=no` in Safari") is duplicated between Quick Reference and Explain. The body is mostly efficient and does not teach generic concepts, but the redundancy means it could be tightened, matching the 3-anchor rather than the padded 2-anchor or lean 5-anchor.

3 / 5

Actionability

Fully executable guidance: exact flaggable values ("`user-scalable=no`", "`maximum-scale=1.0`", "any `maximum-scale` value below 2"), a copy-paste-ready correct tag ("`<meta name='viewport' content='width=device-width, initial-scale=1'>`"), and a concrete alternative fix ("set form input `font-size: 1rem` (16px)") that covers the common iOS input-zoom case. Matches the 5-anchor for an instruction-only skill.

5 / 5

Workflow Clarity

For a simple single-purpose skill, the Check → Fix → Explain sequence is clear and unambiguous, so it could reach 5 under the simple-skill exception. However, the "Code Review" section is generic boilerplate ("Review stylesheets, component styles, and responsive states related to Do not disable pinch zoom") that vaguely duplicates the Check section without adding a step or checkpoint — a minor gap that holds it at 4.

4 / 5

Progressive Disclosure

The ~35-line body is a well-organized overview (Quick Reference, Check, Fix, Explain) that keeps implementation details in a single one-level-deep reference, clearly signaled at the end ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"). The referenced file exists and contains the code examples, matching the 5-anchor.

5 / 5

Total

17

/

20

Passed

Description

78%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 specific, well-scoped description with concrete check patterns and minimal conflict risk. Its main weaknesses are the malformed "Use when applies to any..." trigger clause and the absence of the natural user terms (zoom, pinch zoom, accessibility) that would most readily evoke this skill.

Suggestions

Fix the garbled trigger clause: replace "Use when applies to any `<meta name='viewport'>` element in HTML documents" with a grammatical scenario, e.g. "Use when reviewing or editing HTML documents that contain a `<meta name='viewport'>` tag".

Add natural trigger synonyms users would actually say — "pinch zoom", "zoom", "pinch-to-zoom", "accessibility", "WCAG" — so the description surfaces when the user phrases the problem in those terms.

State the skill's remediation purpose alongside detection (e.g. "flag and fix viewport tags that disable zoom") so the single "check" action reads as broader capability coverage.

DimensionReasoningScore

Specificity

"Check the `content` attribute for `user-scalable=no`, `user-scalable=0`, `maximum-scale=1`, or `maximum-scale` values less than 2" enumerates four concrete, specific check targets, but the description is built around a single action verb ("check") rather than the multiple distinct actions of the top anchor. It clearly exceeds the 1-2 concrete actions of the score-3 anchor, so it sits between anchors at 4.

4 / 5

Completeness

Both parts are present: a concrete "what" ("Check the `content` attribute for `user-scalable=no`...") and an explicit trigger ("Use when applies to any `<meta name='viewport'>` element in HTML documents"). But the trigger clause is grammatically garbled ("Use when applies to any...") and describes a scope rather than a user scenario, so the "when" could be more explicit and specific — matching the 4-anchor, not the clear concrete trigger phrases of 5.

4 / 5

Trigger Term Quality

Good keyword coverage: "viewport", "`<meta name='viewport'>`", "user-scalable=no", "maximum-scale", "HTML documents", "mobile-first templates" are terms a user reviewing this issue would say. However, the most natural user phrasings — "zoom", "pinch zoom", "pinch-to-zoom", "accessibility" — are absent, so it falls short of comprehensive synonym coverage at 5.

4 / 5

Distinctiveness Conflict Risk

The description targets a clear niche — viewport meta tag attribute values, with exact patterns like `user-scalable=no` and `maximum-scale=1` — that no other plausible skill would trigger on. Minimal conflict risk; matches the 5-anchor.

5 / 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/viewport-zoom/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.