obsidian-cli

Automate Obsidian vault management via the obsidian CLI.

5|2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/Tx1207/hello-scholar --skill obsidian-cli-tx1207
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-cli
Source: https://github.com/Tx1207/hello-scholar/tree/main/skills/memory/obsidian-cli
Command: npx skills add https://github.com/Tx1207/hello-scholar --skill obsidian-cli-tx1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables command-line interaction with a running Obsidian instance to read, create, search, and manage notes, tasks, properties, plugins, and themes, simplifying development, debugging, and workflow automation in Obsidian projects.

Core Features & Use Cases

  • Read and create notes via the obsidian CLI in the active vault.
  • Search vault content, manage properties, inspect DOM or errors for debugging plugins/themes.
  • Reload plugins, execute JavaScript, capture errors, take screenshots, and develop or debug Obsidian plugins and themes.

Quick Start

Use the obsidian CLI to read a note named My Note from the active 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 reading and creating notes in an Obsidian vault from the command line?

You can automate reading and creating notes in an Obsidian vault by running obsidian CLI commands, which interact directly with your active vault to manage content deterministically for script-driven workflows.

Can I debug Obsidian plugins and themes using a CLI tool?

Yes, you can debug Obsidian plugins and themes using CLI commands to inspect the DOM, capture errors, execute JavaScript, and reload plugins directly within your running vault environment.

What is the best way to search vault content and manage note properties via automation?

Searching vault content and managing properties via automation is done through the obsidian CLI, allowing deterministic, script-driven execution to query and update notes in the focused Obsidian instance.

Does the Obsidian CLI require the Obsidian app to be running to manage vaults?

Yes, the Obsidian CLI requires the Obsidian application to be running with a focused vault, as it automates interactive management by communicating with the active instance rather than parsing offline files.

Why would I use command line automation for Obsidian instead of editing files directly?

Command line automation for Obsidian enforces deterministic execution for script-driven operations, enabling you to reload plugins, take screenshots, and manage notes interactively without manual GUI interaction.

What are the limitations of using a CLI to manage an active Obsidian vault?

The CLI relies on the obsidian CLI commands and assumes a running Obsidian instance with a focused vault, meaning it cannot execute vault management tasks offline and depends on the active app state.