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.
An unusually tight, opinionated instruction skill: every section states a rule, its failure mode, and a concrete application, with no filler and no over-explanation. The main defect is that its one executable artifact, the referenced memory-lint script, is missing from the bundle, leaving both the lint workflow and the sole external reference dangling.
Suggestions
Ship the referenced 'scripts/memory-lint.bb' in the bundle (or remove/replace the reference with an inline checklist), so the 'Verify links' step is actually executable.
Consider consolidating the write/update path into one short sequenced checklist (decide against the bar → match the genre shape → attach evidence anchors → update the index → lint), pulling together steps currently spread across four sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and dense throughout: 'Memory is not a diary', 'Every claim carries its anchor, or it's vibes', 'a stale "pending" is a lie with a timestamp'. The few anecdotes (the 30-file corpus, the 28KB file) are evidence anchors for the rules they justify, not padding, and the text never explains concepts Claude already knows. | 5 / 5 |
Actionability | Highly concrete guidance for an instruction-only skill: genre shapes ('the rule → Why: → How to apply: → the incident'), a concrete correction marker ('**CORRECTION (was wrong here):**'), and a size threshold ('past ~10KB ... split'). Not 5 because the one executable command, 'scripts/memory-lint.bb <memory-dir>', references a script that does not exist in this bundle, so it is not copy-paste runnable. | 4 / 5 |
Workflow Clarity | The core decision bar is unambiguous ('its absence already burned a red→green cycle, or would burn one next session') and verification steps are embedded (verify every [[link]] resolves, run the lint script, split files past ~10KB). Not 5 because the writing/updating process is distributed across sections rather than presented as one sequenced workflow with explicit checkpoints. | 4 / 5 |
Progressive Disclosure | Well-organized single file with clear section headers, each appropriately scoped; ~90 lines of cohesive rule content that does not warrant splitting. Minor gap: the sole external reference, 'scripts/memory-lint.bb', does not resolve to a real file in the bundle (no scripts/ directory exists). | 4 / 5 |
Total | 17 / 20 Passed |