obsidian▌
steipete/clawdis · updated Apr 8, 2026
Automate Obsidian vault operations and search plain Markdown notes via obsidian-cli.
- ›Requires obsidian-cli binary; install via Homebrew or manually
- ›Core commands: search note names or content with snippets, create notes with optional auto-open, move/rename notes with automatic wikilink and Markdown link updates across the vault, and delete notes
- ›Vaults are standard folders on disk containing .md files, .canvas JSON files, and a .obsidian/ config directory; read the active vault from
Obsidian
Obsidian vault = a normal folder on disk.
Vault structure (typical)
- Notes:
*.md(plain text Markdown; edit with any editor) - Config:
.obsidian/(workspace + plugin settings; usually don’t touch from scripts) - Canvases:
*.canvas(JSON) - Attachments: whatever folder you chose in Obsidian settings (images/PDFs/etc.)
Find the active vault(s)
Obsidian desktop tracks vaults here (source of truth):
~/Library/Application Support/obsidian/obsidian.json
obsidian-cli resolves vaults from that file; vault name is typically the folder name (path suffix).
Fast “what vault is active / where are the notes?”
- If you’ve already set a default:
obsidian-cli print-default --path-only - Otherwise, read
~/Library/Application Support/obsidian/obsidian.jsonand use the vault entry with"open": true.
Notes
- Multiple vaults common (iCloud vs
~/Documents, work/personal, etc.). Don’t guess; read config. - Avoid writing hardcoded vault paths into scripts; prefer reading the config or using
print-default.
obsidian-cli quick start
Pick a default vault (once):
obsidian-cli set-default "<vault-folder-name>"obsidian-cli print-default/obsidian-cli print-default --path-only
Search
obsidian-cli search "query"(note names)obsidian-cli search-content "query"(inside notes; shows snippets + lines)
Create
obsidian-cli create "Folder/New note" --content "..." --open- Requires Obsidian URI handler (
obsidian://…) working (Obsidian installed). - Avoid creating notes under “hidden” dot-folders (e.g.
.something/...) via URI; Obsidian may refuse.
Move/rename (safe refactor)
obsidian-cli move "old/path/note" "new/path/note"- Updates
[[wikilinks]]and common Markdown links across the vault (this is the main win vsmv).
Delete
obsidian-cli delete "path/note"
Prefer direct edits when appropriate: open the .md file and change it; Obsidian will pick it up.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
obsidian is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Sep 9, 2024
Keeps context tight: obsidian is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Registry listing for obsidian matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakshi Patil· Jul 7, 2024
obsidian reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend obsidian for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· May 5, 2024
Useful defaults in obsidian — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Dhruvi Jain· Apr 4, 2024
obsidian has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Rahul Santra· Mar 3, 2024
Solid pick for teams standardizing on skills: obsidian is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Feb 2, 2024
We added obsidian from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Jan 1, 2024
obsidian fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.