Content
82%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 an exemplar of token-efficient instruction writing: terse, dense, and assuming intelligence, with concrete tool-level guidance (named mem_* tools, ordering, dedup-by-ID rules) and explicit guard conditions for risky write operations. Remaining gaps are minor: no invocation argument examples, recovery steps phrased as prohibitions, and a dangling DOCS.md pointer outside the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and lean with zero padding — no concept explanations Claude already knows — and trusts the reader with compressed maxims like "A failed read is not evidence of absence" and "snippets are not identity evidence". Every token earns its place, matching 'Lean and efficient; assumes Claude's competence'. | 5 / 5 |
Actionability | Concrete guidance throughout: exact tools and order ("mem_context, then mem_search with distinctive keywords, then mem_get_observation"), "mem_update by ID: keep topic_key", and mem_session_summary's field list (Goal, Instructions, Discoveries, Accomplished, Next Steps, Relevant Files). Not 5 because no invocation arguments or signatures are shown, so it is not fully copy-paste ready. | 4 / 5 |
Workflow Clarity | Recall, write (search → read candidates in full → update vs. save), and session-close flows are clearly sequenced with guard checkpoints ("If already covered, write nothing", "On ambiguous identity or failed lookup, do not overwrite"). Not 5 because error-recovery loops (e.g., what to do after a failed write beyond 'do not blindly repeat') are stated as prohibitions rather than explicit validate-fix-retry steps. | 4 / 5 |
Progressive Disclosure | At ~40 lines with well-organized sections (When to Use, Selective Memory, Session Close Rules, Delivery Guarantee) and no need for external references, structure is good. Not 5 because "Canonical prose lives in DOCS.md" points to a file absent from the skill's bundle (no references/ directory), and a stray '---' rule awkwardly severs the final Delivery Guarantee section. | 4 / 5 |
Total | 17 / 20 Passed |