Content
70%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.
A highly actionable, well-sequenced workflow with strong error-handling guidance and copy-paste-ready gbrain commands. Its main costs are redundancy — grounding/citation rules repeated across four or five sections — and a monolithic structure that inlines protocol detail a reference file should carry.
Suggestions
Consolidate the citation, no-hallucination, and source-precedence rules (currently repeated in Contract, Anti-Patterns, Quality Rules, Output Format, and Citation in Answers) into a single section.
Move the Token-Budget Awareness implementation detail (cost formulas, fractional-budget compatibility, packing counters) into a reference file, keeping only the decision rule and one example inline.
Give get_timeline and list_pages the same concrete command examples the other tools have, so every listed tool is executable as written.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is operational rather than tutorial-style, but the citation/no-hallucination rules are restated across Contract, Anti-Patterns, Quality Rules, Output Format, and Citation in Answers, and the Token-Budget section inlines protocol minutiae (ceil(fact.length/4) cost math, fractional-budget compatibility) that could be tightened or moved out. | 3 / 5 |
Actionability | Concrete, executable commands with flags and question-to-command mappings cover the common cases (recall with budget-policy, query with return-unit, four graph-query examples, doctor, filter flags); minor gaps remain since get_timeline and list_pages are never shown as actual commands. | 4 / 5 |
Workflow Clarity | A clear 5-phase sequence with explicit validation ("Check each retrieval result for notices before answering") and genuine error-recovery feedback loops in 'When it fails' (try display names/synonyms, narrow or page before claiming absence), matching the anchor-5 pattern of sequence plus checkpoints plus recovery loops. | 5 / 5 |
Progressive Disclosure | No bundle files exist, so everything lives in a ~230-line SKILL.md; section headers give structure, but protocol-level detail (Token-Budget Awareness, memory-verbs block) is inlined where a reference file would be appropriate, and external doc pointers (docs/protocol/MEMORY_VERBS_v1.md, ../conventions/agent-operator-protocol.md) are buried mid-paragraph rather than clearly signaled. | 3 / 5 |
Total | 15 / 20 Passed |