Content
75%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 well-structured, information-dense reference skill with genuinely actionable rules (self_state verification, honest uncertainty, explicit tool routing) and no filler. Its gaps are minor: some redundancy around the self_state rule, descriptive sections without corresponding guidance, and a buried pointer to deeper docs.
Suggestions
State the "call self_state before claiming a part is running" rule once (in "Talking about yourself") and reference it elsewhere instead of repeating it in the intro and owner-controls sections.
Move the pointer to the detailed docs under `memory/` out of the inline sentence and into a clearly labeled final section (e.g., "## Deeper detail") so navigation to it is explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes competence — it documents bespoke system behavior Claude could not know (lifecycles, hormone half-lives, RRF fusion) with no padding about generic concepts. It falls short of anchor 5 because of minor redundancy: the "call self_state before saying a part is running" rule appears in the intro, again under "Talking about yourself", and indirectly under "The owner's controls", and several sentences carry multiple parentheticals that could be tightened. | 4 / 5 |
Actionability | Concrete directives dominate: "Call `self_state` before saying a part is running", "say what you searched", "read this file before answering", "do not promise a deletion you did not do", and a complete tool-routing table in "When to use what" (e.g., "Prior work, decisions, people, dates: `memory_search`, then `memory_get`"). Not a 5 because sections like Feelings and Dreams are largely descriptive background with little guidance on what to do with the information beyond tone effects. | 4 / 5 |
Workflow Clarity | The core workflows are clearly sequenced with checkpoints: answer questions about how parts work from this file, verify live state via `self_state` before claiming a part runs, and fall back to "say you are not sure instead of filling the gap" — an explicit error-recovery guardrail. It is not a 5 because some sequences (e.g., handling a correction via reconsolidation vs. memory_pin) are described but not stepped through, and no explicit validate-then-retry loop exists for the owner-requested forget/edit path. | 4 / 5 |
Progressive Disclosure | No bundle files exist, and the single ~70-line body is well-organized into clearly headed, navigable sections that appropriately cover one cohesive topic. It fits anchor 4's good structure with minor gaps rather than 5: it exceeds the under-50-lines simple-skill case, and the pointer to further detail ("the docs under `memory/` have the detail") is buried inline in "Talking about yourself" rather than clearly signaled as a navigable reference section. | 4 / 5 |
Total | 16 / 20 Passed |