obsidian-cli

Read, write, and search Obsidian vaults via the obsidian CLI.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Nero-kk/claude-agent-skills --skill obsidian-cli-nero-kk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-cli
Source: https://github.com/Nero-kk/claude-agent-skills/tree/main/claude-skills/obsidian-cli
Command: npx skills add https://github.com/Nero-kk/claude-agent-skills --skill obsidian-cli-nero-kk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Obsidian vaults are powerful for knowledge management, but interacting with them from external tools or automating tasks via a CLI is often cumbersome. The Obsidian CLI Skill simplifies this by enabling read, write, search, and vault-management operations directly from the terminal.

Core Features & Use Cases

  • Read, create, and search notes from the Obsidian vault using the obsidian CLI.
  • Reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM for plugin/theme development and debugging.
  • Use cases include automation of note creation, bulk updates, and testing plugins without opening the Obsidian UI.

Quick Start

Create or read a note in the active Obsidian vault using the obsidian CLI.

Frequently Asked Questions about obsidian-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate note creation and search operations in an Obsidian vault from the command line?

You can automate note creation, bulk updates, and search operations in an Obsidian vault by using the obsidian CLI to read and write notes directly from the terminal.

Can I reload Obsidian plugins and debug them without opening the UI?

Yes, you can reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM for plugin and theme development directly via the obsidian CLI.

What is the best way to inspect the DOM of an Obsidian vault during plugin development?

The best way to inspect the Obsidian vault DOM during plugin development is using the obsidian CLI, which supports running JavaScript and capturing errors directly from the terminal.

Does the obsidian CLI support running custom JavaScript code for vault debugging workflows?

Yes, the obsidian CLI supports running custom JavaScript code to capture errors and inspect the DOM, enabling automated debugging workflows for vault operations.

What limitations exist when managing Obsidian vaults externally using a CLI?

Limitations of managing Obsidian vaults externally include potential conflicts with the UI if not properly synchronized, and the CLI's dependence on the active vault's state for read and write operations.