From obsidian-skills
This skill should be used when the user asks to "read an Obsidian note", "search my vault", "create a note in Obsidian", "append to my daily note", "list tags in Obsidian", "check my tasks", "open a file in Obsidian", "manage Obsidian plugins", "query a base", or any interaction with an Obsidian vault via the command line. Also triggered when the user mentions "obsidian", "vault", "daily note", or "Obsidian CLI".
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-skills:obsidian-cliThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Obsidian CLI (`obsidian`) is a command line interface for controlling Obsidian from the terminal. It enables scripting, automation, and integration with external tools. The Obsidian desktop app must be running for CLI commands to work.
Obsidian CLI (obsidian) is a command line interface for controlling Obsidian from the terminal. It enables scripting, automation, and integration with external tools. The Obsidian desktop app must be running for CLI commands to work.
# Single command mode
obsidian <command> [parameters] [flags]
# Interactive TUI mode (autocomplete, history, Ctrl+R search)
obsidian
param=value. Quote values with spaces: content="Hello world"open, overwrite, verbose\n for newline, \t for tab--copy to any command to copy output to clipboardIf the terminal's cwd is inside a vault, that vault is used. Otherwise the active vault is used.
obsidian vault=Notes daily
obsidian vault="My Vault" search query="test"
Many commands accept file=<name> (wikilink-style resolution) or path=<path> (exact path from vault root). If neither is provided, the active file is used.
obsidian read file=Recipe
obsidian read path="Templates/Recipe.md"
obsidian read # read active file
obsidian read file=Recipe # read by name
obsidian create name="Trip to Paris" template=Travel open # create from template
obsidian append file=TODO content="- [ ] Buy milk" # append to file
obsidian prepend path="journal.md" content="---" # prepend after frontmatter
obsidian daily # open today's daily note
obsidian daily:read # read daily note contents
obsidian daily:append content="- [ ] Buy groceries" # add to daily note
obsidian daily:path # get daily note path
obsidian search query="meeting notes" # search vault
obsidian search query="TODO" path=Projects limit=10 # scoped search
obsidian search:context query="meeting" format=json # search with line context
obsidian tasks # list all tasks
obsidian tasks todo # incomplete tasks only
obsidian tasks daily # tasks from daily note
obsidian task ref="Recipe.md:8" toggle # toggle task status
obsidian task daily line=3 done # mark daily task done
obsidian tags counts # list tags with counts
obsidian properties file=Note format=yaml # show file properties
obsidian property:set name=status value=draft file=Note # set property
obsidian property:read name=tags file=Note # read property
obsidian files # list all files
obsidian files folder=Projects ext=md # filter by folder/extension
obsidian backlinks file=Note # find what links to a file
obsidian links file=Note # outgoing links
obsidian orphans # files with no incoming links
obsidian unresolved # broken links
obsidian outline file=Note # show heading structure
obsidian plugins # list installed plugins
obsidian plugins:enabled filter=community # list enabled community plugins
obsidian plugin:install id=my-plugin enable # install and enable
obsidian plugin:reload id=my-plugin # reload (for development)
obsidian devtools # toggle dev tools
obsidian dev:screenshot path=screenshot.png # take screenshot
obsidian eval code="app.vault.getFiles().length" # run JavaScript
obsidian dev:console level=error # show error logs
obsidian dev:css selector=".workspace" prop=background # inspect CSS
obsidian dev:dom selector=".nav-file-title" text all # query DOM
Many commands support format=json|tsv|csv|md for structured output. Default varies by command. Use total flag to get counts only.
For the complete command reference with all parameters and flags, consult references/commands.md. Commands are organized into these categories:
help, version, reload, restartbases, base:views, base:create, base:querybookmarks, bookmarkcommands, command, hotkeys, hotkeydaily, daily:path, daily:read, daily:append, daily:prependdiff, history, history:list, history:read, history:restore, history:openfile, files, folder, folders, open, create, read, append, prepend, move, rename, deletebacklinks, links, unresolved, orphans, deadendsoutlineplugins, plugins:enabled, plugins:restrict, plugin, plugin:enable, plugin:disable, plugin:install, plugin:uninstall, plugin:reloadaliases, properties, property:set, property:remove, property:readpublish:site, publish:list, publish:status, publish:add, publish:remove, publish:openrandom, random:readsearch, search:context, search:opensync, sync:status, sync:history, sync:read, sync:restore, sync:open, sync:deletedtags, tagtasks, tasktemplates, template:read, template:insertthemes, theme, theme:set, theme:install, theme:uninstall, snippets, snippets:enabled, snippet:enable, snippet:disableuniquevault, vaults, vault:openwebwordcountworkspace, workspaces, workspace:save, workspace:load, workspace:delete, tabs, tab:open, recentsdevtools, dev:debug, dev:cdp, dev:errors, dev:screenshot, dev:console, dev:css, dev:dom, dev:mobile, evalConfirm the CLI is available and connected before relying on command output: run obsidian version. A successful version string means the desktop app is running with the CLI enabled; an error means the app is not running or the CLI is disabled (see Prerequisites).
references/commands.md - Complete command reference with all parameters, flags, and descriptions for every Obsidian CLI commandGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub jrjsmrtn/jrjsmrtn-skills --plugin obsidian-skills