CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

navigation-landmark

Use when reviewing templates, rendered HTML, or shared components related to Use navigation landmark regions. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

84%

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.

A well-structured, lean instruction-only skill: a quick-reference summary, concrete check/fix/explain sections, an explicit code-review output contract, and a clean single-level pointer to references/rule.md for implementation depth. The only weaknesses are two minor restatements of accessibility concepts Claude already knows and a couple of concrete details (skip-link markup, single-nav labeling nuance) deferred to the reference file.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with short, purposeful sections (Quick Reference, Check, Fix, Explain, Code Review). Minor over-explanation that could be trimmed: the intro sentence 'without them, users must tab through every link' and the Quick Reference bullet 'Screen reader users navigate by landmarks' restate accessibility concepts Claude already knows — anchor 4 ('efficient; minor instances of over-explanation') rather than anchor 5's every-token-earns-its-place, and clearly better than anchor 3's noticeably padded profile.

4 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill: 'Wrap navigation links in nav elements with descriptive aria-labels like Main navigation or Footer navigation', 'use nav elements with aria-label or aria-labelledby', 'Flag exact elements, attributes, and routes'. Minor gaps keep it at anchor 4 rather than 5: no inline markup example for the skip-link recommendation, and no guidance on when a label is unnecessary (single nav of its kind) — details deferred to references/rule.md.

4 / 5

Workflow Clarity

This is a simple, single-purpose review skill and the single action is unambiguous, so per the rubric's simple-skill exception workflow clarity can score 5. The Check → Fix → Explain → Code Review structure sequences the review task cleanly, ending with explicit output guidance ('Flag exact elements, attributes, and routes where the rendered HTML violates the rule'). No destructive or batch operations are involved, so no validation checkpoint is required.

5 / 5

Progressive Disclosure

The body is a concise overview with clearly signaled, one-level-deep references: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — a real file (342 lines) containing the code examples and framework guidance promised. The split is appropriate (essentials inline, depth in the reference), matching anchor 5's clear overview with well-signaled single-level references.

5 / 5

Total

18

/

20

Passed

Description

78%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.

A strong description that explicitly covers both what the skill does (validate final browser-facing markup, not the framework abstraction) and when to use it (reviewing templates, rendered HTML, or shared components). Its weaknesses are the thin action vocabulary (only reviewing/validating) and the awkward inlined rule title 'related to Use navigation landmark regions', which reads as template-generated rather than natural trigger language.

Suggestions

List the concrete actions the skill performs (e.g., 'Flag nav regions missing aria-label, recommend skip-link markup, explain landmark violations') instead of relying on the generic verbs 'reviewing' and 'validating'.

Add natural trigger terms users would actually say — 'nav element', 'aria-label', 'accessibility', 'screen reader' — alongside 'navigation landmark regions'.

Rewrite the inlined rule title ('related to Use navigation landmark regions') into a direct third-person capability statement, e.g., 'Validates that navigation areas use nav elements with distinguishing aria-labels'.

DimensionReasoningScore

Specificity

The description names the domain (navigation landmark regions, browser-facing markup) and two concrete actions — 'reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup, not just the source framework abstraction' — but is not comprehensive. It matches anchor 3 ('names domain and 1-2 concrete actions'); it falls short of anchor 4 because it does not list several specific actions (no mention of flagging violating elements, suggesting fixes, or validating aria-label usage).

3 / 5

Completeness

Both questions are explicitly answered with concrete trigger phrases: 'Use when reviewing templates, rendered HTML, or shared components related to navigation landmark regions' (when) and 'Validate the final browser-facing markup, not just the source framework abstraction' (what). This matches anchor 5 — a clear 'what' plus an explicit 'Use when...' clause with concrete triggers — rather than anchor 4 where the 'when' would be only implicit or less specific.

5 / 5

Trigger Term Quality

Good keyword coverage with 'templates', 'rendered HTML', 'shared components', and 'navigation landmark regions' — natural terms for a frontend markup review. A few natural terms are missing: 'nav element', 'aria-label', 'accessibility', and 'screen reader', which users would commonly say when needing this skill, so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The topic is a clear niche (navigation landmarks specifically), but the trigger clause 'Use when reviewing templates, rendered HTML, or shared components' would be shared by sibling HTML-rule skills in the same family, with only the rule name differentiating them. This is 'mostly distinct; minor overlap risk with closely related skills' (anchor 4) rather than anchor 5's minimal conflict risk.

4 / 5

Total

16

/

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