Agent skill · software engineering · sickn33
obsidian-cli
Use the Obsidian CLI to read, create, search, and manage vault content, or to develop and debug Obsidian plugins and themes from the command line.
Why this skill is useful
Adds specific commands and workflows for managing Obsidian vaults and developing plugins that the AI wouldn't reliably generate on its own.
What it needs
Requires obsidian installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Obsidian CLI Use the obsidian CLI to interact with a running Obsidian instance. Requires Obsidian to be open. 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. Command reference Run obsidian help to see all available commands. This is always up to date. Full docs: https://help.obsidian.md/cli Syntax Parameters take a value with =. Quote values with spaces: Flags are boolean switches with no value: For multiline content use \n for newline and \t for tab. File targeting Many commands accept file or path to target a file. Without either, the active file is used. file=<name> — resolves like a wikilink (name only, no path or extension needed) path=<path> — exact path from vault root, e.g. folder/note.md Vault targeting Current CLI defaults use the vault in the working directory when applicable, otherwise the active vault; verify the target explicitly. Use vault=<name> as the first parameter to target a specific vault: Common patterns Use --copy on any command to copy output to clipboard. Use silent to prevent files from opening. Use total on list commands to get a count. Plugin development Develop/test cycle After making code changes to a plugin or theme, follow this workflow: 1. Reload the plugin to pick up changes: 2. Check for errors — if errors appear, fix and repeat from step 1: 3. Verify visually with a screenshot or DOM inspection: 4. Check console output for warnings or unexpected logs: Additional developer commands Run JavaScript in the app context: Inspect CSS values: Toggle mobile emulation: Run obsidian help to see additional developer commands including CDP and debugger controls. Limitations 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/obsidian-cli