Content
78%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 well-structured router that practices what it preaches: near-zero token waste, concrete inline rules for cross-cutting concerns (document IDs, video), and flawless one-level-deep reference navigation with every referenced file verified real. Its limitations are the duplicated topic list, the absence of any inline code snippet for the most common tasks, and no disambiguation rule for multi-guide requests.
Suggestions
Merge "When to Apply" into the "Quick Reference" (or replace its bullets with the matching file stems) — the topic list currently appears twice, costing tokens without adding routing signal.
Add one small inline snippet for the highest-frequency action (e.g., a minimal defineType/defineField example or a one-line GROQ query) so the most common guidance is actionable before loading a reference file.
Extend "How to Use" with a disambiguation rule for requests matching multiple guides (e.g., prefer the framework guide for integration setup and the topic guide for content modeling).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~85-line body is lean with no padding and no explanations of concepts Claude already knows (the Video section's cost rationale is justified, not fluff), but the topic set is listed twice — "When to Apply" (14 bullets) substantially duplicates the "Quick Reference" (25 entries) — so some tokens do not earn their place. | 4 / 5 |
Actionability | Global Rules and the Video section give concrete directives with real identifiers ("defineVideoField() from sanity/media-library", "@mux/mux-player-react", "sanity-plugin-mux-input", singleton pattern "homePage-en"), and every Quick Reference entry carries a routing description, but the body contains no executable code or commands of its own. | 4 / 5 |
Workflow Clarity | "How to Use" gives a clear sequence with an explicit extension condition ("Start with the single framework or topic guide that best matches the request, then read additional references only when the task crosses concerns"), and the single routing action is largely unambiguous; the minor gap is no guidance for requests that match several guides equally or none. | 4 / 5 |
Progressive Disclosure | Textbook progressive disclosure: the body is a pure index while all detail lives in one-level-deep references/ files — all 25 Quick Reference stems verified to exist with substantive content (frontmatter, incorrect/correct code examples), and paths are clearly signaled via the stem list plus the explicit "references/groq.md" examples. | 5 / 5 |
Total | 17 / 20 Passed |