CtrlK
BlogDocsLog inGet started
Tessl Logo

breadcrumb

Use when auditing metadata, crawlability, structured data, or indexability related to Implement valid BreadcrumbList schema. Verify the rendered HTML and HTTP response rather than relying only on source files.

55

Quality

62%

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/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The skill is well-structured with a clean overview pointing to a real one-level-deep reference, but the body leans on descriptive guidance rather than executable examples and lacks an explicit validation checkpoint in its workflow.

Suggestions

Remove the opening explanatory sentence about what breadcrumbs are (Claude already knows this) and start directly with the Quick Reference.

Inline a minimal copy-paste JSON-LD BreadcrumbList snippet in the Fix section so the guidance is executable without opening the reference.

Add an explicit validation step after Fix (e.g. 'Validate JSON-LD with the Rich Results Test / Schema Markup Validator, then re-check the rendered HTML') as a workflow checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly lean with tight directive sections, but the opening sentence ('Breadcrumbs help search engines understand your site's structure and often appear in search results, improving navigation and click-through rates.') explains a concept Claude already knows.

2 / 3

Actionability

Guidance names concrete artifacts ('BreadcrumbList structured data', 'JSON-LD script', 'ListItem properties', 'rendered HTML and HTTP response') but the body contains no executable code or commands, deferring all examples to the reference.

2 / 3

Workflow Clarity

The Check / Fix / Explain / Code Review sections imply a loose sequence, but there are no explicit validation checkpoints or feedback loops in the body; verification is only implied via the deferred reference.

2 / 3

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md' for full implementation details, code examples, and framework-specific guidance), and that file exists with the detailed content appropriately split out.

3 / 3

Total

9

/

12

Passed

Description

67%

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 'Use when' trigger and clearly states both what and when, but its capability list reads as domain/target enumeration rather than concrete actions, and the trigger terms are generic SEO keywords that risk overlapping sibling skills.

Suggestions

Replace the domain-listing trigger with concrete verbs, e.g. 'Audit, validate, and fix BreadcrumbList JSON-LD markup' to lift specificity.

Add natural user-facing terms like 'breadcrumb navigation', 'breadcrumb trail', and 'breadcrumbs' alongside the technical 'BreadcrumbList schema'.

Lead the trigger with the breadcrumb-specific phrase ('Use when checking breadcrumb schema...') rather than generic SEO terms to reduce conflict with sibling SEO skills.

DimensionReasoningScore

Specificity

It names the SEO domain and two actions ('auditing metadata, crawlability, structured data, or indexability' and 'Verify the rendered HTML and HTTP response'), but mostly lists audit targets rather than enumerating multiple distinct concrete actions.

2 / 3

Completeness

It explicitly answers both what ('auditing ... structured data ... Verify the rendered HTML and HTTP response') and when via an explicit 'Use when auditing ...' trigger clause, satisfying the 'Use when' requirement.

3 / 3

Trigger Term Quality

Relevant SEO keywords are present ('metadata, crawlability, structured data, or indexability', 'BreadcrumbList schema'), but it omits natural variations a user would say such as plain 'breadcrumbs' or 'breadcrumb navigation'.

2 / 3

Distinctiveness Conflict Risk

The breadcrumb-specific phrasing ('related to Implement valid BreadcrumbList schema') gives a niche, but the leading trigger terms (metadata, crawlability, structured data, indexability) are generic SEO terms likely shared with sibling checklist skills.

2 / 3

Total

9

/

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.