Content
51%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 content is a concise, actionable command reference with copy-paste bash examples, but it lacks any sequenced workflow or validation for its destructive/batch operations and its reference tables point to non-existent or mis-pathed files. Fixing the broken paths and adding a short validated workflow would substantially raise quality.
Suggestions
Correct the reference paths: point the Scripts table at 'scripts/memory-backup.sh' and 'scripts/memory-consolidate.sh' (the real locations) and either create 'docs/hnsw.md' and 'docs/memory-schema.md' or remove those reference rows.
Add a short sequenced workflow with a validation checkpoint around destructive/batch operations, e.g. 'list --namespace' to confirm the target key before 'memory delete', and verify an export file exists after 'memory export'.
Remove the duplicated frontmatter restated in the Purpose and When to Trigger/Skip sections to recover tokens, keeping a single concise statement of intent.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient with no concept over-explanation, but it restates the frontmatter three times — the Purpose section verbatim repeats the description and the 'When to Trigger'/'When to Skip' sections re-list the same Use/Skip clauses — so several tokens do not earn their place and could be tightened. | 3 / 5 |
Actionability | Each command is a complete, copy-paste-ready bash invocation (e.g. 'npx @claude-flow/cli memory store --key ... --namespace patterns') with worked examples for the common cases (store, search, get, list), but delete/init/stats/export lack example blocks and no prerequisites (e.g. init or install) are stated, leaving minor gaps. | 4 / 5 |
Workflow Clarity | The body is a command catalog rather than a sequenced workflow; the only implicit sequence is the vague Best Practices list ('Check memory for existing patterns before starting', 'Store successful patterns after completion'), with no validation checkpoints for the destructive 'delete' or batch 'export' operations, fitting the anchor for a rough sequence with many gaps and absent validation. | 2 / 5 |
Progressive Disclosure | Structure is well organized with clearly signaled Scripts and References tables, but the referenced paths are broken: 'docs/hnsw.md' and 'docs/memory-schema.md' do not exist, and the scripts are cited at '.agents/scripts/...' while the actual bundle lives at 'scripts/...', so navigation does not actually resolve. | 3 / 5 |
Total | 12 / 20 Passed |