CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

72%

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

70%

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

The body is well-structured with a clean one-level reference, but it carries some restatement and lacks an inline executable markup example, capping conciseness and actionability at level 2.

Suggestions

Add a short, copy-paste-ready HTML breadcrumb snippet in the body so actionability does not depend on the external reference.

Drop or condense the intro 'helps screen reader users... improving SEO' sentence and de-duplicate the Check/Fix sections against the Quick Reference to tighten token use.

DimensionReasoningScore

Conciseness

The body is mostly lean with concise Quick Reference bullets, but the intro sentence explains a concept Claude already knows and the Check/Fix sections restate the bullets, so it could be tightened; not a 1 because it is not padded or verbose overall.

2 / 3

Actionability

Attribute-level guidance is concrete ('nav element with aria-label=\'Breadcrumb\'', 'aria-current=\'page\''), but there is no complete executable markup example inline — examples are deferred to the reference — so it falls short of copy-paste-ready level 3.

2 / 3

Workflow Clarity

This is a simple single-purpose review skill with an unambiguous action sequenced through Check/Fix/Code Review; the simple-skill carve-out allows a 3 without explicit multi-step validation checkpoints.

3 / 3

Progressive Disclosure

Well-organized sections plus a clearly signaled, one-level-deep pointer to a real references/rule.md file match the level-3 anchor; not a 2 because the reference is clearly signaled rather than buried.

3 / 3

Total

10

/

12

Passed

Description

75%

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 has an explicit trigger and a clear, distinctive niche, but its action list and natural-keyword spread are moderate rather than comprehensive.

Suggestions

Replace jargon like 'source framework abstraction' with natural terms a user would say (e.g. 'React/Vue components', 'server-rendered HTML', 'template files').

Expand the action list to name multiple concrete capabilities (e.g. 'Review breadcrumb markup, flag missing aria-current, check structured data alignment') to lift specificity to level 3.

DimensionReasoningScore

Specificity

Names the domain and two actions ('reviewing templates, rendered HTML, or shared components' and 'Validate the final browser-facing markup'), but does not list multiple specific concrete actions, so it stops short of the level-3 anchor.

2 / 3

Completeness

It explicitly states the trigger ('Use when reviewing...') and the action (review/validate breadcrumb markup), clearly answering both what and when; not a 2 because the when clause is explicit rather than implied.

3 / 3

Trigger Term Quality

Natural terms like 'breadcrumb navigation', 'templates', 'rendered HTML', and 'shared components' are present, but jargon ('source framework abstraction') and thin common-variation coverage keep it below a strong level-3 spread.

2 / 3

Distinctiveness Conflict Risk

The 'accessible breadcrumb navigation' markup-validation niche is specific and bound to concrete artifacts, making it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

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.