CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/breadcrumb-navigation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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, appropriately split skill body: the overview stays lean, concrete attribute-level guidance is inline, and detail is properly deferred to a real one-level-deep reference file. The main improvement area is redundancy — the Check and Fix sections largely duplicate the Quick Reference bullets — plus the absence of an inline correct-markup example and a post-fix re-check step.

Suggestions

Collapse the redundancy between Quick Reference, Check, and Fix — e.g., keep the bullets as the criteria and rewrite Check as 'Verify each bullet against the rendered HTML' and Fix as 'Apply the corresponding markup change', instead of restating the same attributes three times.

Add a short inline example of correct breadcrumb markup (nav[aria-label='Breadcrumb'] > ol > li with aria-current='page' on the last item) so the rule is verifiable without opening the reference file.

In the Fix section, add a re-validation step such as 're-check the rendered HTML against Quick Reference after applying the fix' to close the feedback loop.

DimensionReasoningScore

Conciseness

The body is short, but the 'Check' and 'Fix' sections substantially restate the Quick Reference bullets ('nav element with aria-label, ordered list markup, and aria-current' appears in both), and the opening sentence plus the 'Explain' section add why-oriented text that Claude does not need spelled out. It fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than a 4, where over-explanation would be only minor — the section-level duplication is a clear tightening opportunity.

3 / 5

Actionability

The guidance is concrete and specific — 'Use nav element with aria-label='Breadcrumb'', 'Use ordered list (ol)', 'Mark current page with aria-current='page'', and 'Flag exact elements, attributes, and routes where the rendered HTML violates the rule' give exact element names and attribute values. Per the rubric's scoring note, the absence of code in an instruction-only skill is not penalized, but it is not a 5 because no inline example of correct breadcrumb markup is provided and one bullet ('Keep any structured data aligned with the visible breadcrumb trail') is noticeably vaguer than the others.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure gives a coherent, unambiguous sequence for this simple audit-style skill, with the Quick Reference acting as the criteria list. It misses a 5 because there is no validation loop after 'Fix' (e.g., re-checking the rendered output against the rule) and no guidance on what to do when a template's source looks correct but rendered markup still violates the rule — a minor checkpoint gap.

4 / 5

Progressive Disclosure

The SKILL.md body is a lean overview with well-organized sections, and the 350-line detail (implementation, code examples, framework guidance) is correctly split into references/rule.md, which exists and is referenced exactly once, one level deep, with a clearly signaled pointer: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md'. This matches the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

16

/

20

Passed

Description

70%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 solid trigger-oriented description with an explicit 'Use when...' clause, a clear niche, and a distinctive 'validate the rendered markup, not the abstraction' framing. Its main weaknesses are limited action coverage and awkward phrasing where the rule title 'Implement accessible breadcrumb navigation' is embedded mid-sentence, plus missing natural synonyms like 'accessibility', 'a11y', or 'ARIA'.

Suggestions

Rewrite the embedded title as a natural action, e.g., 'Review and validate breadcrumb markup (nav with aria-label, ordered list, aria-current)' — this both fixes the awkward 'related to Implement accessible breadcrumb navigation' phrasing and raises action specificity.

Add natural trigger synonyms such as 'accessibility', 'a11y', 'ARIA', or 'breadcrumbs' so users who mention accessibility rather than the exact phrase 'breadcrumb navigation' still match the skill.

DimensionReasoningScore

Specificity

The description names the domain ('accessible breadcrumb navigation', 'rendered HTML') and two concrete actions — 'reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup' — but the action coverage is not comprehensive. It does not rise to a 4 because only two actions are listed and 'reviewing' is generic; it is above a 2 because the domain and actions are concrete, not minimal.

3 / 5

Completeness

Both what and when are present: the 'when' is explicit ('Use when reviewing templates, rendered HTML, or shared components related to...') with concrete trigger phrases, and the 'what' states 'Validate the final browser-facing markup, not just the source framework abstraction'. It is not a 5 because the 'what' is muddled by the embedded title phrase 'related to Implement accessible breadcrumb navigation', which reads as a template artifact rather than a clearly stated capability, so the what could be more explicit.

4 / 5

Trigger Term Quality

Good keyword coverage: 'breadcrumb navigation', 'templates', 'rendered HTML', 'shared components', and 'browser-facing markup' are all natural phrases a user would say when needing this skill. It falls short of a 5 because common synonyms and variations are missing — 'accessibility', 'a11y', 'ARIA', 'breadcrumbs' (plural), and 'site hierarchy' never appear; it is clearly above a 3, whose anchor example has only a single keyword.

4 / 5

Distinctiveness Conflict Risk

The 'breadcrumb navigation' niche is clear and the directive to validate rendered markup rather than framework source narrows the trigger further. Minor overlap risk remains with closely related HTML/accessibility review skills that would share the same generic 'reviewing templates, rendered HTML, or shared components' opening; it is well above a 3 (which would overlap with broadly similar skills) and below a 5 because of that shared boilerplate trigger prefix.

4 / 5

Total

15

/

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