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.

72

Quality

90%

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

87%

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

A well-organized, lean review skill with actionable guidance and clean one-level-deep progressive disclosure. The main gap is the absence of an explicit re-verification feedback loop after fixes are applied.

Suggestions

Add an explicit re-verification checkpoint to the Fix section, e.g. "After fixing, re-rotate through portrait and landscape and confirm all content and controls remain usable," to close the validation gap in workflow_clarity.

Frame the workflow as a rotate → flag → fix → re-verify feedback loop so the review cycle has a clear validation step rather than an implicit one.

Trim the mild redundancy between the Quick Reference bullets and the Check/Fix sections to keep the already-lean body fully token-efficient.

DimensionReasoningScore

Conciseness

The body is a lean, under-35-line overview with tightly written Quick Reference, Check, Fix, Explain, and Code Review sections; it avoids explaining basic concepts Claude already knows.

3 / 3

Actionability

As an instruction-only review skill it gives concrete, specific guidance — "Verify all primary content, navigation, forms, and interactive controls remain available" and "Flag exact selectors, components, or route states" — with code appropriately deferred to the reference.

3 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clearly sectioned, but there is no explicit re-verification checkpoint after applying fixes, leaving a validation gap.

2 / 3

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference ("see references/rule.md"), which exists and holds the detailed code/examples, with no nested references.

3 / 3

Total

11

/

12

Passed

Description

92%

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 strong, well-structured description with an explicit trigger clause, concrete actions, and natural keywords. Its only weakness is that the broad list of target interfaces slightly raises overlap risk with general layout-review skills.

DimensionReasoningScore

Specificity

The description lists concrete actions — "Check rendered behavior in both portrait and landscape" and "separate genuine layout constraints from unnecessary orientation assumptions" — rather than vague language, matching the multi-action anchor.

3 / 3

Completeness

It explicitly answers both: what (check rendered behavior, separate constraints from assumptions) and when via an explicit "Use when reviewing ..." trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

It covers natural terms a user would say — "mobile-first layouts, tablet experiences, fullscreen flows, forms, dashboards, or media interfaces" and "portrait and landscape" — giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

The orientation/portrait-landscape focus is a clear niche, but the broad surface list ("forms, dashboards, or media interfaces") could overlap with general responsive/layout-review skills and trigger for the wrong skill.

2 / 3

Total

11

/

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.