Content
80%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 tight, command-dense reference that respects the token budget and gives copy-pasteable obsidian-cli usage with useful non-obvious caveats (URI handler, dot-folders, hardcoded paths). The one real gap is the absence of validation around the destructive `delete` and vault-wide `move` operations, which caps workflow clarity.
Suggestions
Add a verification step after `move`, e.g. re-run `obsidian-cli search-content "old-name"` to confirm no stale links remain, or note that move reports the count of updated links.
Add a caution before `delete` (e.g. confirm the path via `search` first, or note there is no undo/trash semantics via the CLI).
Show how to extract the active vault from `obsidian.json` with a one-line jq command instead of just describing it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean bullets and one-liners ("Obsidian vault = a normal folder on disk.") with zero padding — it never explains what Obsidian or Markdown is, and assumes Claude's competence. Every line adds non-obvious operational knowledge (config path, URI-handler caveat, dot-folder caveat), matching 'Lean and efficient; every token earns its place'. | 5 / 5 |
Actionability | Nearly every operation has a concrete, copy-pasteable command (`obsidian-cli search-content "query"`, `move "old/path/note" "new/path/note"`, `create "Folder/New note" --content "..." --open`) plus the exact config file path. It is not 5 because reading `obsidian.json` is described but not shown (no jq/example), and `--content "..."` is a placeholder rather than a worked example — 'concrete code or commands with minor gaps'. | 4 / 5 |
Workflow Clarity | The find-vault → set-default → operate flow is clearly sequenced, but the skill documents destructive and batch operations (`delete`, and `move` which rewrites wikilinks vault-wide) with no validation or verification steps. Per the rubric guideline this caps workflow clarity at 3, taking precedence over the simple-skill exception; it stays at 3 rather than lower because the sequence itself is coherent and unambiguous. | 3 / 5 |
Progressive Disclosure | The skill is a short (~58-line), single-file overview with well-organized sections (vault structure, find vaults, CLI quick start) and no bundle files — nothing here needs offloading to references. Per the rubric's simple-skill guideline, a lean skill under ~50 lines with no need for external references scores 5 on well-organized sections alone. | 5 / 5 |
Total | 17 / 20 Passed |