wiki-cli checks whether the official obsidian executable is usable against your vault, then uses it to read notes and search. A present binary is not enough: the skill trusts the detector’s usable flag, because the app may be closed or command line access may be off.
Every create, write, append, move, rename and delete command is off limits. Changes go through the claude-obsidian transaction core.
What You Get
- A transport report saying whether the Obsidian CLI is present and usable
- Read and search results from the vault through the CLI
- A file-read and rg fallback when the CLI is not ready
- An optional persisted transport snapshot when you or setup ask for it
- A firm boundary that keeps writes in the transaction core
Common Use Cases
- Searching a large vault through Obsidian’s own index
- Listing backlinks or tags for a note
- Finding out why the Obsidian CLI does not respond
What Makes It Unique
It separates detection from trust: binary presence only means present, and only the usable flag allows CLI reads. The CLI is an optional read surface and never a lock manager or a write path, so choosing a transport never changes how mutations are protected.
Under The Hood
The skill is instructions that run the plugin’s detect-transport shell script and the obsidian command line from inside your vault folder, for reading and searching only. The detector can write a small derived file under .vault-meta/ only when you ask for a snapshot. The skill does not fetch web pages or call outside services, and it does not write notes.