CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

80%

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/viewport/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with copy-paste-ready guidance, a clear simple-skill workflow, and clean one-level progressive disclosure. The main weakness is mild verbosity from explaining a known concept in the intro and restating in the Check/Explain sections.

Suggestions

Trim the opening paragraph and the Check/Explain sections to remove restating of concepts Claude already knows, improving token efficiency.

Make the Check step concrete by tying verification explicitly to the disallowed attributes (maximum-scale=1, user-scalable=no) rather than the generic 'proper viewport meta tag'.

DimensionReasoningScore

Conciseness

The Quick Reference and Fix sections are lean and actionable, but the opening paragraph explains the viewport concept (which Claude already knows) and the Check/Explain sections add some restating that could be tightened.

2 / 3

Actionability

It provides the exact, copy-paste-ready meta tag and an explicit prohibition ('Never use maximum-scale=1 or user-scalable=no'), giving fully executable guidance.

3 / 3

Workflow Clarity

This is a simple single-action skill with an unambiguous Check -> Fix -> Code Review sequence supported by the concrete Quick Reference; the simple-skill allowance applies since it is not a destructive or batch operation.

3 / 3

Progressive Disclosure

The body is a well-organized overview with clearly signaled, one-level-deep navigation to references/rule.md (a real file), keeping detail appropriately separated.

3 / 3

Total

11

/

12

Passed

Description

75%

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 clearly answers both what and when with an explicit trigger and a distinct, narrow niche. It could be strengthened by listing more concrete actions and adding common natural terms like 'responsive' or 'mobile'.

Suggestions

Add more concrete actions (e.g., 'add, verify, and correct the viewport meta tag') to lift specificity toward the level-3 anchor.

Include natural terms users would say such as 'responsive', 'mobile', or 'mobile-friendly' alongside 'viewport meta tag'.

DimensionReasoningScore

Specificity

Names a clear domain ('templates, rendered HTML, or shared components') and one concrete action ('Validate the final browser-facing markup'), but does not list multiple specific actions, so it stops short of the comprehensive level-3 anchor.

2 / 3

Completeness

It states what the skill does ('Validate the final browser-facing markup, not just the source framework abstraction') and includes an explicit 'Use when...' trigger, answering both what and when.

3 / 3

Trigger Term Quality

Relevant keywords like 'rendered HTML', 'shared components', and 'viewport meta tag' are present, but common natural variations users would say ('responsive', 'mobile', 'mobile-friendly') are missing.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific ('Set the responsive viewport meta tag', 'final browser-facing markup'), with triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.