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 lean, concrete, and workflow-driven with a useful anti-patterns section and checklist. Its main defects are a broken reference to a missing TROUBLESHOOTING.md and the absence of a fully worked REST fallback example.
Suggestions
Fix or remove the broken reference to TROUBLESHOOTING.md — either ship the file in the bundle or inline a one-line fallback for when memory_commits is unavailable.
Add a complete, copy-paste REST fallback example (e.g., a fetch to GET /agentmemory/commits with URLSearchParams) so the URL-encoding guidance is executable rather than advisory.
Include a brief example of how to render the empty-result message so the step-4 guidance is as concrete as the happy-path rendering spec.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~55-line body is lean with no padding or explanation of concepts Claude already knows; even the 'Why' section earns its tokens by defining non-obvious rendering semantics ('An empty result means the filter matched nothing, not that work is missing'). Fits the 'every token earns its place' anchor. | 5 / 5 |
Actionability | Concrete tool invocation ('memory_commits { "branch": "main", "limit": 20 }'), an expected-output sample, precise parsing rules with defaults and a 500 cap, and a URL-encoding anti-pattern with named functions. Minor gaps: no full REST fallback example and the quick-start call is a sketch rather than copy-paste syntax, so it sits at anchor 4 rather than 5. | 4 / 5 |
Workflow Clarity | A clear 4-step sequence (parse arguments, call the tool, render reverse-chronologically, handle empty results) is reinforced by a checklist, and the empty-result branch is an explicit checkpoint. The tool-unavailable failure path delegates to a file that does not exist, a minor validation gap keeping it below 5. | 4 / 5 |
Progressive Disclosure | Sections are well organized for a short skill, but the only external reference ('See [TROUBLESHOOTING.md](TROUBLESHOOTING.md)') points to a nonexistent file — a dangling pointer that breaks navigation at runtime. This is more than a minor organization gap (not 4), though nothing is buried or mis-inlined (not 2). | 3 / 5 |
Total | 16 / 20 Passed |