Content
63%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 dense, largely actionable architecture reference with excellent concrete contracts (templates, CLI calls, validation rules) and well-sequenced embedded protocols. Its weaknesses are length with padded asides, slow-changing reference material kept inline instead of in bundle files, and two orphaned/dangling bundle references.
Suggestions
Move slow-changing reference material (source-quality buckets, confidence formula details, per-skill defaults table, markdown link-path tables) into a references/ file, keeping SKILL.md to the contracts and decision rules.
Link references/karpathy-pattern.md and references/WRITING.md from the body (or remove/rename them) — karpathy-pattern.md is currently unreachable, and the bundled WRITING.md is confusable with the runtime <global config dir>/WRITING.md.
Fix the dangling "scripts/manifest.py" reference (the script is absent from the bundle), and split the long inline paragraphs (the snapshots bullet in the Sources section, the manifest migration aside) into short rules plus a compact example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most content is skill-specific contracts, tables, and templates that earn their tokens, but there is real padding: the ~140-word single-paragraph snapshots bullet in the Sources section, the long manifest-migration aside, repeated "why this matters/syntax" justifications, and operational detail (per-skill confidence defaults) that belongs to companion skills. Mostly efficient but several sections could be tightened — matching anchor 3 rather than 4. | 3 / 5 |
Actionability | Guidance is largely executable: copy-paste bash functions (find_config, obsidian_wiki_config_dir), exact CLI invocations ("obsidian-wiki memory sync INGEST source=...", "scripts/manifest.py migrate <vault> --dry-run"), complete page/paper templates, and value tables. Not anchor 5 because "scripts/manifest.py" and ".env.example" are referenced but absent from the bundle, leaving minor executability gaps. | 4 / 5 |
Workflow Clarity | The Config Resolution Protocol is an ordered 0–3 sequence with explicit failure handling ("tell the user it doesn't exist and list the available vaults... do not silently fall back"), migration prescribes --dry-run and honest failure reporting, and lint enforces illegal transitions, drift, and undated claims. Not 5 because the main operational workflows (ingest, rebuild) are delegated to companion skills, so no end-to-end validated sequence lives in this file. | 4 / 5 |
Progressive Disclosure | references/MEMORY.md is clearly signaled and one level deep, but scored against the actual bundle: references/karpathy-pattern.md is never linked from the body, references/WRITING.md is orphaned and confusable with the runtime <global config dir>/WRITING.md, scripts/manifest.py is referenced but missing, and ~700 lines of reference-grade detail (source-quality buckets, confidence formulas, link-path tables) sit inline in SKILL.md — beyond the "minor organization gaps" of anchor 4. | 3 / 5 |
Total | 14 / 20 Passed |