obsidian-cli
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
Obsidian CLI
Run obsidian <command> to control a running Obsidian instance from the terminal. The app must be running for most commands; the first command will launch Obsidian if not open.
Run obsidian help or obsidian help <command> for the canonical, always-up-to-date command reference. This skill documents common patterns and non-obvious behaviors.
Status and commands
!which obsidian
Targeting vaults and files
- Vault:
vault=<name>as first parameter. Default: cwd if it's a vault folder, else the active vault. - File:
file=<name>resolves like a wikilink (name only, no path or extension needed).path=<path>for exact path from vault root. - TUI: Run
obsidianwith no args for interactive mode; omit theobsidianprefix inside.
Parameters and flags
- Parameters:
param=value. Quote values with spaces:content="Hello world". - Flags: Boolean, no value:
silent,overwrite,newtab. - Multiline content: Use
\nfor newlines,\tfor tabs incontent=.
Search, links, and structure
obsidian search query="text" [path=folder] [limit=n] [format=text|json] [total] [case]
obsidian search:context query="text" [path=folder] [limit=n] # includes surrounding context
obsidian links [file=Note] [total]
obsidian backlinks [file=Note] [counts] [total]
obsidian outline [file=Note] [format=tree|md]
obsidian orphans [total] [active] # notes with no links to or from them
obsidian deadends [total] [active] # notes with no outgoing links
obsidian unresolved [total] [counts] [verbose] # broken wikilinks
obsidian tags [active] [file=Note] [total] [counts] [sort=count]
obsidian tag name=project [total] [verbose]
Common patterns
Notes and content
To peek at a note without reading its full content, use property:read or properties file=Note.
obsidian read file="Note" # Use this to read the content of a wikilink
obsidian create name="Note" content="# Title\n\nBody" [template=Name] [overwrite] [silent]
obsidian append file="Note" content="- [ ] Task"
obsidian prepend file="Note" content="# Header\n"
obsidian move file="Note" to=folder/newpath.md
obsidian rename file="Note" name="New file name"
obsidian delete file="Note"
Daily notes (Daily notes plugin)
obsidian daily:read
obsidian daily [paneType=tab|split|window] [open]
obsidian daily:append content="- [ ] Buy groceries" [inline] [open]
obsidian daily:prepend content="- [ ] Morning routine" [inline] # goes after frontmatter
obsidian daily:path # returns expected path even if file doesn't exist yet
Tasks
obsidian tasks [daily] [file=Note] [todo] [done] [status="x"] [total] [verbose]
obsidian task ref=path:line [toggle] [done] [todo] [daily]
Properties and frontmatter
obsidian properties [active] [file=Note] [total] [counts] [format=yaml|json|tsv]
obsidian property:read name=status [file=Note]
obsidian property:set name=status value=done [file=Note]
obsidian property:remove name=status [file=Note]
Bases (Bases plugin)
obsidian bases
obsidian base:views [file=base.base]
obsidian base:query [file=base.base] [view=name] [format=json|csv|tsv|md|paths]
obsidian base:create name="Item" content="..." [open] [newtab]
Plugin development
Develop/test cycle
After making code changes to a plugin or theme, follow this workflow:
-
Reload the plugin to pick up changes:
obsidian plugin:reload id=my-plugin -
Check for errors — if errors appear, fix and repeat from step 1:
obsidian dev:errors -
Verify visually with a screenshot or DOM inspection:
obsidian dev:screenshot path=screenshot.png obsidian dev:dom selector=".workspace-leaf" text -
Check console output for warnings or unexpected logs:
obsidian dev:console level=error
Additional developer commands
Run JavaScript in the app context:
obsidian eval code="app.vault.getFiles().length"
Inspect CSS values:
obsidian dev:css selector=".workspace-leaf" prop=background-color
Toggle mobile emulation:
obsidian dev:mobile on
Quick reference
| Task | Command |
|---|---|
| List commands | obsidian help |
| Open daily note | obsidian daily |
| Append to daily | obsidian daily:append content="- [ ] Task" |
| Search vault | obsidian search query="text" |
| Read active/specified file | obsidian read or obsidian read file=Note |
| Create from template | obsidian create name="Title" template=Name |
| List tags with counts | obsidian tags counts |
| List tasks from daily | obsidian tasks daily |
| Find broken wikilinks | obsidian unresolved counts |
| Find orphan notes | obsidian orphans |
References
obsidian help— full command list (always up to date)obsidian help <command>— help for a specific command- Obsidian CLI docs (Obsidian)
More from nweii/agent-stuff
suggest-lucide-icons
Suggest relevant Lucide icons for concepts or UI placements. Searches lucide.dev to find actual icons that symbolize ideas or fit design contexts. Use when needing icons for UI work, documentation, or symbolic representation.
250archive-conversation
Create analytical archival summaries of AI conversations, capturing intellectual journeys, key insights, and technical logs. Use when archiving, saving, or documenting a chat session.
77culinary-assistant
Culinary guidance for cooking, recipes, and meal planning. Use for kitchen techniques, substitutions, and format conversion (Mela, Schema.org). Handles recipe parsing and improvements.
60aid-finances
Expert financial guidance for budgeting, investments, and retirement planning. Use for analyzing market strategies, debt management, or general personal finance questions.
57validating-startup-ideas
Find and validate startup ideas by mining user complaints, crafting premises, and navigating the idea maze. Use when discovering product opportunities, validating ideas, shaping solutions, researching user pain points, or exploring what to build.
44obsidian-templater
Help with templates/snippets for the Obsidian Templater plugin. Use to help generate Obsidian templates from natural language, understand and debug existing tp.* snippets, and adapt vault notes and workflows to Templater when users mention Templater, tp.*, or <% %>.
39