Obsidian Vault Management

The Specific Problem

Obsidian is a popular Markdown-based knowledge management app, but its native interface lacks robust command-line support for automation. Tasks like managing multiple vaults, performing bulk operations, or integrating with scripts become cumbersome. For instance, when notes are scattered across folders or need to be part of CI/CD pipelines, manual GUI interactions create bottlenecks. Challenges include updating wikilinks safely during renames or searching content across vaults efficiently.

Core Capabilities and Key Steps

The obsidian-cli tool addresses these issues by providing a command-line interface with core capabilities:
- Vault Discovery: It reads Obsidian's configuration file (e.g., ~/Library/Application Support/obsidian/obsidian.json) to locate active or default vault paths via obsidian-cli print-default, eliminating hard-coded paths.
- Search and Retrieval: Commands like obsidian-cli search "query" search note titles, while obsidian-cli search-content "query" performs full-text search inside notes, returning snippets and line numbers for script-friendly output.
- Note Creation and Movement: obsidian-cli create generates new notes with specified content. Crucially, obsidian-cli move renames or relocates notes while automatically updating all [[wikilinks]] and common Markdown links across the vault—this prevents broken references, a key advantage over simple file moves.
- Deletion and Cleanup: obsidian-cli delete removes notes, aiding in maintenance.

Operations act directly on .md files on disk, and Obsidian detects changes in real-time without manual refresh. For developers, this enables integrating Obsidian vaults into version control, backup, or automated publishing workflows.

Applicable Boundaries and Caveats

This skill depends on a correctly installed and running Obsidian desktop app with functional obsidian:// URI handlers. Key considerations include:
- Vault Path Management: Avoid assuming fixed paths; always use obsidian-cli print-default to read config, as users often have multiple vaults (e.g., work/personal, iCloud sync).
- Note Creation Limits: Do not create notes under hidden dot-folders (e.g., .obsidian/...), as Obsidian may refuse to process them.
- Direct Edit Alternative: For simple modifications, directly editing .md files is viable—Obsidian syncs automatically—but complex tasks like bulk link updates require CLI.
- Platform Specificity: Config file paths (e.g., macOS ~/Library/...) must be adjusted based on the operating system.

In summary, the obsidian-cli skill empowers engineers to treat Obsidian vaults as programmable assets, but adherence to its design constraints ensures stability and reliability.