Obsidian Cli

A solid CLI wrapper that lets Claude interact directly with your Obsidian vault without fumbling around with file paths. It handles the usual suspects: reading notes, creating content, searching across your vault, managing properties and tasks. The real win is the plugin development workflow. Instead of manually reloading plugins and hunting through console logs, you get clean commands to reload code, capture errors, take screenshots for visual verification, and inspect DOM elements. It's basically what you'd build yourself after getting tired of the reload-and-pray cycle when developing Obsidian plugins.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 11
skills.sh installs: 84.1K
GitHub stars: 51.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add kepano/obsidian-skills --skill obsidian-cli --agent claude-code

Installs into .claude/skills of the current project.

Files

Obsidian CLI

Use the obsidian CLI to interact with a running Obsidian instance. Requires Obsidian to be open.

Before using the CLI

Run obsidian help to check availability. If the command is missing, explain how to turn on the CLI using https://help.obsidian.md/cli. The obsidian command ships with the Obsidian installer; don't install the unrelated npm package obsidian-cli. If it can't find Obsidian, ask the user to open the desktop app, then retry. In a sandboxed shell the same message can mean the sandbox blocked the CLI's local socket.

On WSL, run Obsidian.com from the Windows install folder, not Obsidian.exe. Obsidian.com is the console wrapper that prints the output; Obsidian.exe exits without printing anything.

The CLI exits with status 0 even when a command fails, so read its output before reporting that a command succeeded.

Quote parameters for the current shell, and pass note text as literal argument data, never as executable shell syntax.