Content
57%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 well-organized, appropriately split overview that correctly defers detail to a single real reference file, but it spends tokens explaining concepts Claude already knows and offers descriptive rather than directly executable guidance with no in-body verification checkpoint.
Suggestions
Cut the opening rationale sentence and the 'Explain how descriptive anchor text improves ...' instruction; Claude already knows the SEO/accessibility rationale, so keep only the actionable rule.
Add a concrete in-body verification step (e.g. inspect rendered anchor elements via DevTools or a curl of the rendered HTML) rather than only deferring verification to the reference.
Make the Fix section actionable with a before/after anchor-text example or a selector, instead of the generic 'replace ... with descriptive phrases that include relevant keywords'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean but the opening 'Descriptive anchor text helps search engines understand the context ... and significantly improves accessibility ...' explains a concept Claude already knows and the 'Explain how ...' line restates it; not a 1 because it is not padded or verbose, not a 3 because of the unnecessary rationale and generic instructional filler. | 2 / 3 |
Actionability | Names concrete bad examples ('click here', 'read more') and points to a real reference with HTML examples, but the body itself is descriptive ('Verify that...', 'Replace generic link text...') with no executable verification method or selectors in-line; not a 1 because some concrete guidance and a real code reference exist, not a 3 because key execution detail is deferred. | 2 / 3 |
Workflow Clarity | The Check/Fix/Explain/Code Review sections give a recognizable sequence for a simple task, but there is no in-body verification checkpoint confirming the fix in rendered output — verification is only implied/deferred to the reference; not a 1 because steps are listed, not a 3 because the verification checkpoint is missing rather than explicit. | 2 / 3 |
Progressive Disclosure | The body is a concise overview with a clearly signaled one-level-deep pointer ('see references/rule.md'), and that file exists and is self-contained with no nested references; matches the clear-overview-with-well-signaled-reference anchor; not a 2 because the split is appropriate and navigation is easy. | 3 / 3 |
Total | 9 / 12 Passed |