breadcrumb-navigation

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

Quality

83%

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

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 body is a well-structured, concise overview of an accessible-breadcrumb review skill with concrete attribute-level guidance and a clean one-level reference to references/rule.md. Its main weakness is mild redundancy between the Quick Reference, Check, and Fix sections.

Suggestions

Collapse the overlapping nav/ol/aria-current guidance in Quick Reference, Check, and Fix into a single canonical statement to remove redundancy.

Inline a minimal HTML breadcrumb snippet (nav>ol>li with aria-current='page') so the body is actionable without requiring a jump to references/rule.md.

Add an explicit verification step in the Code Review section (e.g., 'confirm every rendered breadcrumb trail has aria-current on the last item') to make the review workflow's checkpoint explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean with short Quick Reference, Check, Fix, Explain, and Code Review sections, but the Check and Fix sections restate the same nav/ol/aria-current guidance already in Quick Reference, a minor redundancy that keeps it just below level 5.	4 / 5
Actionability	Gives concrete, specific guidance naming exact elements and attributes (nav with aria-label='Breadcrumb', ol/li, aria-current='page'), but ships no inline code example — the executable example lives in references/rule.md — leaving a minor gap versus the fully copy-paste-ready level 5.	4 / 5
Workflow Clarity	The Check/Fix/Explain/Code Review structure gives a clear review-oriented flow for a single-purpose validation skill, with the action unambiguous; it lacks an explicit validation checkpoint, but since this is a non-destructive review task the destructive-cap does not apply, placing it at level 4 rather than 5.	4 / 5
Progressive Disclosure	The body is an organized overview that signals a single one-level-deep reference — 'see references/rule.md' (a real bundle file) — for full implementation details and code examples, matching the clear-overview level 5 anchor.	5 / 5
	Total	17 / 20 Passed

Description

87%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-formed: it states a concrete validation action and pairs it with explicit 'Use when' triggers scoped to breadcrumb markup review. It is concise, third-person, and clearly distinguishable from sibling skills.

Dimension	Reasoning	Score
Specificity	Names concrete actions — 'reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive level 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Validate the final browser-facing markup, not just the source framework abstraction') and 'when' ('Use when reviewing templates, rendered HTML, or shared components related to...') with concrete trigger phrases, matching the level 5 anchor.	5 / 5
Trigger Term Quality	Includes natural review-oriented terms ('templates', 'rendered HTML', 'shared components', 'breadcrumb navigation') that a user would plausibly say, though a few common synonyms are missing, so it sits above level 3 but below the comprehensive level 5.	4 / 5
Distinctiveness Conflict Risk	Tied to a clear niche (accessible breadcrumb navigation) with distinct review triggers and minimal overlap risk with other skills, matching the level 5 anchor.	5 / 5
	Total	18 / 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/breadcrumb-navigation/SKILL.md
Commit: 30756a7

Reviewed: 13 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.