Content
63%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 delivers highly actionable, domain-specific operational detail with a clear phased workflow and genuine error-recovery loops. It is held back by inline bloat — dense blockquoted protocol digressions and version-gated caveats in the mainline — and by inlining material that the referenced convention/protocol docs should carry.
Suggestions
Move the long blockquoted digressions (MEMORY_VERBS contract, redaction handling, visibility/readback rules, keyless-brain extraction) into the docs they already cite (e.g. docs/protocol/MEMORY_VERBS_v1.md) and keep one-line summaries with the reference link in SKILL.md.
Add a concrete write-path example — an actual put_page or remember invocation with arguments and a readback check — to match the read path's copy-paste quality.
Collect version-gated details (gbrain >= 0.43, MEMORY_VERBS v1, v0.18.0+ citation format, schema-pack overrides) into a single version-compatibility section, and trim the shallow-ls anecdote to the rule plus the two verification commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly all content is system-specific (gbrain CLI flags, MCP paths) with no generic-concept padding, but the ~255-line body could be tightened: the 'Real example: a shallow ls counted 132 files' war story, dense nested parentheticals in the MEMORY_VERBS blockquote, and version-gated details ('v0.43+', 'MEMORY_VERBS v1', 'v0.18.0+') woven inline rather than in a deprecated/old-patterns section. | 3 / 5 |
Actionability | Abundant copy-paste-ready commands with exact flags and a fully worked example ('gbrain recall --query zebra telescope --budget-tokens 75 --budget-policy query_first --json', 'find <dir> -name "*.md" | wc -l'). Not 5 because the write path — put_page / remember invocations, the skill's core cycle — never receives a concrete example. | 4 / 5 |
Workflow Clarity | Phases 1–4 are clearly sequenced with numbered steps, explicit error-recovery loops (revision_conflict re-read/merge/retry, write_pending polling) and a readback confirmation checkpoint. Not 5 because some checkpoints remain implicit — Phase 2 never states how to verify a write landed; that lives separately in 'Output Format'. | 4 / 5 |
Progressive Disclosure | References are clearly signaled and one level deep ('See skills/conventions/brain-first.md', 'Contract: docs/protocol/MEMORY_VERBS_v1.md'), but reference-grade protocol detail (verb contract, redaction semantics, visibility matrix, keyless-brain extraction) is inlined rather than deferred to the cited docs, and none of the referenced files exist in this skill's bundle. | 3 / 5 |
Total | 14 / 20 Passed |