Content
78%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, mostly lean instruction-only skill with concrete rules, a worked example, and a closing checklist; the guidance is actionable despite the absence of code. The main gaps are minor editorializing and the lack of an explicit validation/feedback checkpoint in the recall-save workflow.
Suggestions
Trim rhetorical flourishes (e.g. 'the single most destructive habit in agent memory, and it is invisible until someone asks a question about old code') to tighten conciseness without losing the rule.
Add a concrete recall/save template — e.g. a search-query construction rule and a one-line memory-entry format like 'FACT (when: date range, source: file/commit)' — to lift actionability beyond abstract lists.
Turn the recall→save→close flow into an explicit numbered sequence with a validation checkpoint, such as 'after recalling, confirm the entry's validity window still applies before acting on it', to add a feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean rule-based prose with no explaining of concepts Claude already knows, but occasional editorializing flourishes ('the single most destructive habit in agent memory', 'Paraphrase drifts') could be trimmed; sits above the verbose midpoint but short of every-token-earns-its-place. | 4 / 5 |
Actionability | Provides concrete lists (when to recall, when to save, what fields each entry carries) and a worked example with a sample memory entry, but stays backend-agnostic so there is no exact tool-call syntax or template to copy; mostly actionable with minor gaps. | 4 / 5 |
Workflow Clarity | Clear recall-before / save-after structure plus a closing checklist and a 4-step worked example, but there is no explicit validation checkpoint (e.g. confirm an entry's validity window before acting on it); minor validation gap keeps it below 5. | 4 / 5 |
Progressive Disclosure | Self-contained SKILL.md with no bundle files and well-organized section headers (Recall, Save, Write it so it survives, Close don't overwrite, etc.), a worked example, and a checklist; navigation is easy and there are no nested references. | 5 / 5 |
Total | 17 / 20 Passed |