domains / families / agent-tooling / obsidian-cli

obsidian-cli

combined

Skill for the official Obsidian CLI (v1.12+). Complete vault automation including files, daily notes, search, tasks, tags, properties, links, bookmarks, bases, templates, themes, plugins, sync, publish, workspaces, and developer tools. Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.

When to use

• Use when managing vault content through the Obsidian CLI.
• Use when developing or debugging Obsidian plugins and themes from the command line.
• Use when the user wants shell-driven interaction with a running Obsidian app.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The copies overlap heavily on the core Obsidian CLI syntax, file/vault targeting, common patterns, and the plugin develop/test cycle. However, they disagree on vault targeting defaults and each copy adds material steps the others lack: the kepano/brycewang copies state the most recently focused vault is the default; the sickn33 copy says the working-directory vault is used when applicable and adds a Limitations section with safety constraints; the LeoYeAI copy adds prerequisites, platform notes, and a much broader command reference (daily notes, files, search, tasks, tags, properties). Crowning one copy would hide these real alternatives and constraints.