CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

viewport

Use when reviewing templates, rendered HTML, or shared components related to Set the responsive viewport meta tag. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

81%

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

85%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 body is a lean, well-structured single-purpose check with copy-paste-ready fix code, explicit pass/fail criteria, and a clearly signaled one-level reference to references/rule.md that checks out against the actual bundle. Its only weakness is minor padding — background explanation of mobile browser behavior and filler statements covering concepts Claude already knows.

Suggestions

Delete the opening sentence about mobile browsers rendering at 980px then shrinking — Claude already knows this behavior; the Quick Reference carries the actionable content.

Trim the filler bullet 'Essential for mobile-responsive layouts' and the redundant trailing clause 'that controls how the page is displayed on mobile devices' from the Check section.

DimensionReasoningScore

Conciseness

The body is short and its core sections (Quick Reference, Fix, Code Review) are tight, but it includes unnecessary material: the opening sentence explaining 980px desktop-width rendering (a concept Claude already knows), the filler bullet 'Essential for mobile-responsive layouts', and the trailing clause 'that controls how the page is displayed on mobile devices' in the Check section. This matches anchor 3 (mostly efficient, some unnecessary explanation that could be tightened) rather than anchor 4's minor instances.

3 / 5

Actionability

The guidance is copy-paste ready and covers the common cases: 'Add <meta name="viewport" content="width=device-width, initial-scale=1.0">' with its location ('in the head section'), an explicit prohibition ('Never use maximum-scale=1 or user-scalable=no'), and a concrete review directive ('Flag exact elements, attributes, and routes'). This matches anchor 5 (fully executable, specific examples covering common cases).

5 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines whose single action is unambiguous: Quick Reference defines the exact pass criteria (the correct tag content and the prohibited attributes), Check states the verification, and Fix gives the remedy. Per the rubric's simple-skill exception a clear single-action skill with explicit criteria scores 5, and the operation is non-destructive so no validation cap applies.

5 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and references/rule.md exists in the bundle and delivers exactly that content (full HTML example, framework examples, property table). Content is appropriately split, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Description

70%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 a clear explicit 'Use when' trigger clause, good natural keywords, and a concrete validation directive with modest conflict risk against sibling frontend-check skills. Its weaknesses are limited action coverage (review and validate only) and awkward grammar ('related to Set the responsive viewport meta tag') that muddles the capability statement.

Suggestions

Replace 'related to Set the responsive viewport meta tag' with a direct capability statement such as 'Validates that final rendered HTML includes the responsive viewport meta tag', so the 'what' is stated in the skill's own words rather than embedding the rule title.

Broaden action coverage beyond 'reviewing' and 'Validate' — e.g., mention flagging missing or accessibility-hostile viewport tags (maximum-scale=1, user-scalable=no) in server-rendered markup, which would also better distinguish it from sibling skills.

DimensionReasoningScore

Specificity

Names the domain ('viewport meta tag', 'rendered HTML') and two concrete actions — 'reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup' — matching anchor 3 (domain plus 1-2 concrete actions). It falls short of anchor 4 because only two actions are listed, not several.

3 / 5

Completeness

Both parts are present: 'when' via the explicit 'Use when reviewing templates, rendered HTML, or shared components' clause, and 'what' via 'Validate the final browser-facing markup, not just the source framework abstraction'. The 'what' is a terse directive with the rule name awkwardly embedded in the 'when' clause, matching anchor 4 rather than anchor 5's clearly and explicitly stated capability.

4 / 5

Trigger Term Quality

Natural trigger terms are well covered: 'reviewing templates', 'rendered HTML', 'shared components', 'viewport meta tag', 'responsive', 'browser-facing markup'. A few natural terms are missing ('mobile', 'HTML files', '.html'), so it fits anchor 4 (good coverage, a few terms missing) rather than anchor 5's comprehensive synonym and extension coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow (viewport meta tag in rendered markup) and the qualifier 'related to Set the responsive viewport meta tag' separates it from siblings, but the generic lead-in 'Use when reviewing templates, rendered HTML, or shared components' is shared by any frontend-markup check skill. This matches anchor 4 (mostly distinct, minor overlap with closely related skills) rather than anchor 5's minimal conflict risk.

4 / 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.

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