CtrlK
BlogDocsLog inGet started
Tessl Logo

orientation

Use when reviewing mobile-first layouts, tablet experiences, fullscreen flows, forms, dashboards, or media interfaces. Check rendered behavior in both portrait and landscape and separate genuine layout constraints from unnecessary orientation assumptions.

75

Quality

93%

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

92%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 well-organized, lean overview that delegates implementation detail to a one-level-deep reference. It is actionable and clearly sequenced for a simple review skill, with only minor inline-code gaps.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; the brief wheelchair/stand rationale earns its place and every section is tight.

5 / 5

Actionability

Concrete, specific guidance ('Rotate the page between portrait and landscape', 'Flag any use of orientation locks, rotate-device overlays') with minor gaps since executable code lives in the reference rather than inline.

4 / 5

Workflow Clarity

Clear sequenced sections (Quick Reference, Check, Fix, Explain, Code Review) for a single-purpose review skill with no destructive or batch operations, satisfying the simple-skill exception.

5 / 5

Progressive Disclosure

Body is a concise overview with a well-signaled one-level-deep reference to references/rule.md (verified to exist) for full implementation details, with easy navigation.

5 / 5

Total

19

/

20

Passed

Description

95%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 well-constructed with an explicit 'Use when...' trigger, concrete natural keywords, and a clear niche. It answers both what the skill does and when to invoke it without verbosity.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('Check rendered behavior in both portrait and landscape', 'separate genuine layout constraints from unnecessary orientation assumptions'), with minor coverage gaps relative to the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both 'what' (check rendered behavior in both orientations, separate genuine constraints from assumptions) and 'when' via a concrete 'Use when...' clause listing trigger scenarios.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms users would say — 'mobile-first layouts', 'tablet experiences', 'fullscreen flows', 'forms', 'dashboards', 'media interfaces', 'portrait and landscape'.

5 / 5

Distinctiveness Conflict Risk

Clear accessibility-orientation niche with distinct triggers (orientation locks, portrait/landscape checks) and minimal overlap with other skills.

5 / 5

Total

19

/

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.

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.