obsidian-cli

Automate Obsidian CLI commands for vaults, files, and URIs.

40|9|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/akillness/oh-my-skills --skill obsidian-cli-akillness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-cli
Source: https://github.com/akillness/oh-my-skills/tree/main/.agent-skills/obsidian-cli
Command: npx skills add https://github.com/akillness/oh-my-skills --skill obsidian-cli-akillness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Obsidian CLI enables you to control a running Obsidian desktop app from the terminal, making it easy to automate vault/file operations, run commands, and interact with URIs without manual clicks.

Core Features & Use Cases

  • Official desktop CLI for single commands and an interactive TUI to manage vaults, notes, searches, and developer tasks.
  • Vault and file targeting with vault= ordering and file=/path= resolution for precise automation across multiple vaults.
  • URI integration with obsidian:// for opening, creating, and wiring callback-based workflows, including encoding rules and x-success/x-error hooks.
  • Developer tooling support with commands like plugin:reload, devtools, dev:screenshot, and eval for plugin and theme workflows.
  • Desktop-bound automation vs Headless workflows, clarifying when the CLI applies to the running app versus separate headless usage.

Quick Start

Install and enable the Obsidian CLI from the desktop app, then use the terminal to run commands against a vault.

Frequently Asked Questions about obsidian-cli

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

FAQPage Schema
How do I automate Obsidian vault and file operations from the terminal?

Automate Obsidian vault and file operations from the terminal by enabling the Obsidian CLI in the desktop app's settings, then executing commands that target specific vaults and files using vault= and path= resolution rules.

Can I use obsidian:// URIs to trigger workflows and callbacks from the command line?

Yes, you can use obsidian:// URIs from the command line to open, create, and wire callback-based workflows, utilizing encoding rules and x-success or x-error hooks for automated interactions with the desktop app.

Does the Obsidian CLI work with headless installations or only the desktop app?

The Obsidian CLI is bound to the running desktop app for automation, meaning it applies to the active desktop installation rather than separate headless usage, clarifying the boundary between desktop-bound and headless workflows.

What developer tools are available for Obsidian plugin and theme workflows via the CLI?

Obsidian plugin and theme developer tools available via the CLI include commands for plugin reloading, accessing devtools, capturing development screenshots, and evaluating code to streamline your workflow.

How do I target specific notes across multiple Obsidian vaults using the command line?

Target specific notes across multiple Obsidian vaults using the command line by applying vault= ordering and file= or path= resolution rules, ensuring precise automation for the correct vault and file.

Why is my Obsidian CLI not working after installation?

If the Obsidian CLI is not working after installation, ensure the CLI is explicitly enabled in the Obsidian desktop app Settings, as the terminal commands require an active connection to a running desktop installation.