landmark-one-main

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use exactly one main landmark. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/landmark-one-main/SKILL.md

Quality

Content

78%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 content is a well-structured, lean overview that delegates detail to a single real reference file with clear navigation, fitting a simple single-purpose accessibility rule. Actionability and workflow clarity are strong, with only minor validation/checkpoint gaps since verification steps sit in the reference rather than the body.

Dimension	Reasoning	Score
Conciseness	The body is terse and sectioned, with only minor over-explanation (the one-sentence rationale intro and slight redundancy between Quick Reference and the Check/Fix sections) that could be trimmed.	4 / 5
Actionability	Concrete, specific guidance is given ('Count the number of <main> elements or elements with role=\'main\'', 'Combine multiple main content areas into a single <main> element'), with full code examples appropriately deferred to references/rule.md.	4 / 5
Workflow Clarity	A clear Check -> Fix -> Explain -> Code Review sequence is present for this simple single-purpose skill, but explicit verification checkpoints live only in the reference file rather than the body, leaving a minor validation gap.	4 / 5
Progressive Disclosure	The body is a concise overview with a clearly signaled one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and references/rule.md exists and holds the bulk detail.	5 / 5
	Total	17 / 20 Passed

Description

63%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 answers both what and when with concrete review actions, but the trigger phrasing is somewhat generic and the rule name 'Use exactly one main landmark' is awkwardly pasted mid-sentence rather than surfaced as a natural keyword. Distinctiveness is moderate given the broad review framing.

Suggestions

Reword the trigger so the rule-specific phrase reads naturally, e.g. 'Use when reviewing pages for the one-main-landmark accessibility rule' instead of 'related to Use exactly one main landmark'.

Add natural synonyms users would say such as 'accessibility', 'a11y', 'main element', and 'landmark navigation' to improve trigger-term coverage.

Narrow the when-clause to the landmark check specifically to reduce overlap with general accessibility or design-system review skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') rather than vague language, with only minor coverage gaps.	4 / 5
Completeness	Both 'what' (review/inspect semantics, keyboard, focus, names, SR output) and 'when' ('Use when reviewing rendered HTML, interactive components, or design-system patterns') are present, but the when-clause could be more explicit and cleanly tied to the rule.	4 / 5
Trigger Term Quality	Relevant keywords exist ('rendered HTML', 'interactive components', 'design-system patterns', 'screen-reader output') but the most natural rule-specific phrases ('main landmark', 'accessibility', 'a11y') are absent and the embedded 'Use exactly one main landmark' reads as a pasted title rather than a natural trigger.	3 / 5
Distinctiveness Conflict Risk	The trigger 'reviewing rendered HTML, interactive components, or design-system patterns' is broad and overlaps with many other accessibility/frontend review skills; only the awkwardly embedded rule name narrows it.	3 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/landmark-one-main/SKILL.md
Commit: 30756a7

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.