CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

71%

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

65%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 lean, well-organized overview that appropriately defers implementation detail to a real one-level-deep reference file. It falls short on actionability and workflow clarity: no executable code or concrete verification tooling appears in the body itself, and the check-fix flow lacks an explicit re-validation loop.

Suggestions

Include a minimal executable JSON-LD BreadcrumbList snippet (or at least the exact ListItem shape: position, name, item) in the Fix section rather than deferring all code to the reference.

Add an explicit validation loop after Fix — re-fetch the rendered page and confirm the schema parses and matches the visible trail — instead of a single one-sentence Check with no feedback loop.

Name concrete verification tooling in the Check section (e.g., Google Rich Results Test or Search Console) so the checkpoint is executable without opening the reference.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout; the only trimmable text is the opening sentence "Breadcrumbs help search engines understand your site's structure and often appear in search results...", which explains a concept Claude already knows — a minor instance of over-explanation rather than the 'some unnecessary explanation' of the level below.

4 / 5

Actionability

The body names specifics ("Use JSON-LD to mark up each item in the breadcrumb trail correctly", "Flag exact routes or templates where search-facing output violates the rule") but contains no executable code, commands, or verification tooling — the JSON-LD example and check methods are entirely deferred to references/rule.md, leaving key details missing from the body.

3 / 5

Workflow Clarity

A sensible Check → Fix → Explain → Code Review sequence is present and the "Check" section ("Verify that the page contains valid BreadcrumbList structured data matching the visible breadcrumbs") acts as a checkpoint, but there is no post-fix re-validation loop and concrete validation methods are left implicit in the body.

3 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview that clearly signals a single one-level-deep reference ("see `references/rule.md`"), which exists in the bundle and carries the code example, exceptions, and verification detail — content appropriately split with easy navigation.

5 / 5

Total

15

/

20

Passed

Description

66%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 has a clear, explicit 'Use when' trigger clause and names a distinct SEO niche, with good natural keyword coverage. Its weaknesses are an implicit 'what' buried inside the rule title and broad leading trigger terms (metadata, crawlability, indexability) that overlap with sibling SEO audit skills.

Suggestions

Lead with an explicit capability statement in third person (e.g., 'Audits and implements valid BreadcrumbList JSON-LD structured data in rendered HTML') instead of burying the what inside the 'Use when' clause.

Narrow the trigger terms to breadcrumb-specific phrases (breadcrumbs, breadcrumb trail, JSON-LD, rich results) so the description does not compete with sibling SEO skills covering metadata, crawlability, or indexability.

Add common synonyms users would actually say — 'schema markup', 'JSON-LD', 'rich results', 'breadcrumbs' — to broaden trigger coverage.

DimensionReasoningScore

Specificity

"auditing metadata, crawlability, structured data, or indexability" plus "Verify the rendered HTML and HTTP response" names the domain with two concrete actions, but coverage stops there — matching the '1-2 concrete actions' anchor rather than the several specific actions of the level above.

3 / 5

Completeness

The explicit "Use when auditing..." clause clearly answers when, and "Verify the rendered HTML and HTTP response rather than relying only on source files" gives a concrete what; however, the core capability is only implied through the embedded rule title, so the what is not as explicit as the level-5 anchor.

4 / 5

Trigger Term Quality

Natural terms like "metadata", "crawlability", "structured data", "indexability", "rendered HTML", and "BreadcrumbList schema" give good keyword coverage, but common variations users would say — "schema markup", "JSON-LD", "rich results", "breadcrumbs" alone — are missing.

4 / 5

Distinctiveness Conflict Risk

The breadcrumb-schema niche itself is distinct, but the leading triggers "auditing metadata, crawlability, structured data, or indexability" are exactly the domain of sibling SEO audit skills (metadata, indexability, canonical-url), creating more than the 'minor overlap risk' of the level above.

3 / 5

Total

14

/

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