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

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/viewport-zoom/SKILL.md

Quality

Content

71%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-structured, actionable instruction skill with clean progressive disclosure to a real reference file. It would benefit from tightening the redundant Quick Reference/Check/Explain material and trimming the motivational intro.

Suggestions

Consolidate the overlapping Quick Reference and Check sections to remove redundancy, and trim the motivational opening paragraph to the essential accessibility impact.

Fold the repeated WCAG 1.4.4 explanation so it appears once rather than across both the Explain section and the intro.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but carries redundancy (Quick Reference overlaps Check; Explain repeats the WCAG rationale) and a padded motivational intro paragraph about why zoom matters.	3 / 5
Actionability	It gives concrete checks with exact attribute values, the precise correct viewport tag, and a specific fix (set input `font-size: 1rem`); code examples live in the reference, but the in-body guidance is actionable with only minor gaps.	4 / 5
Workflow Clarity	Sequenced sections (Check, Fix, Explain, Code Review) lay out a clear review workflow; this flagging skill is not a destructive or batch operation, so the missing explicit validation loop only costs a minor gap.	4 / 5
Progressive Disclosure	The short body is well-organized into labeled sections and points to a single, clearly signaled one-level-deep reference (`references/rule.md`, verified to exist) for full details and code examples.	5 / 5
	Total	16 / 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 is specific, well-scoped, and clearly answers both what and when, with strong distinctiveness. Its main weakness is trigger phrasing that relies on technical attribute names rather than the natural terms (zoom, pinch-to-zoom) users would say.

Suggestions

Add natural-language trigger terms such as "pinch-to-zoom" or "zoom" so the skill matches how users actually phrase the need.

Rephrase the "Use when" clause to describe the reviewing scenario (e.g., "Use when reviewing mobile HTML for accessibility") rather than the self-referential "applies to any viewport element".

Dimension	Reasoning	Score
Specificity	"Check the `content` attribute for `user-scalable=no`, `user-scalable=0`, `maximum-scale=1`, or `maximum-scale` values less than 2" enumerates several concrete detection targets, though it is essentially one checking action with listed values rather than multiple distinct actions.	4 / 5
Completeness	Both the what (check these attribute values) and the when ("Use when applies to any `<meta name='viewport'>` element in HTML documents") are present, but the when clause is technical and somewhat self-referential rather than a crisp user-facing trigger.	4 / 5
Trigger Term Quality	It surfaces relevant technical terms (viewport, user-scalable, maximum-scale, mobile-first) but omits the natural phrasings a user would actually say such as "zoom" or "pinch-to-zoom".	3 / 5
Distinctiveness Conflict Risk	The description is tightly scoped to the viewport meta tag accessibility rule, a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	16 / 20 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/viewport-zoom/SKILL.md
Commit: 30756a7

Reviewed: 4 days 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.