Content
65%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |