Obsidian Cli
- 1 installs
- 3.2k repo stars
- Updated August 4, 2026
- brycewang-stanford/awesome-agent-skills-for-empirical-research
This is a copy of obsidian-cli by kepano - installs and ranking accrue to the original listing.
obsidian-cli is a skill that interacts with a running Obsidian vault through the obsidian command-line tool to manage notes and develop plugins.
About
This skill uses the obsidian CLI to interact with a running Obsidian instance from the command line. A developer uses it to read, create, append, and search notes, set properties, list tasks and tags, and also to reload, debug, and screenshot Obsidian plugins and themes. It matters for scripting vault operations and plugin development workflows.
- Drives a running Obsidian vault via the obsidian CLI
- Reads, creates, searches, and manages notes, tasks, and properties
- Supports Obsidian plugin and theme development and debugging
Obsidian Cli by the numbers
- 1 all-time installs (skills.sh)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
obsidian-cli capabilities & compatibility
- Capabilities
- vault automation · plugin dev
- Works with
- obsidian
- Use cases
- documentation · debugging
- Pricing
- Free
What obsidian-cli says it does
Use the `obsidian` CLI to interact with a running Obsidian instance. Requires Obsidian to be open.
After making code changes to a plugin or theme, follow this workflow:
npx skills add https://github.com/brycewang-stanford/awesome-agent-skills-for-empirical-research --skill obsidian-cliAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 3.2k |
| Last updated | August 4, 2026 |
| Repository | brycewang-stanford/awesome-agent-skills-for-empirical-research ↗ |
What it does
Read, create, search, and manage Obsidian notes and develop or debug plugins from the command line.
Who is it for?
Scripting Obsidian vault operations and developing or debugging Obsidian plugins and themes.
Skip if: Editing an Obsidian vault when the app is not running.
When should I use this skill?
When the user asks to interact with their Obsidian vault or develop and debug Obsidian plugins from the command line.
What you get
Notes read, created, and searched, or a plugin reloaded and inspected via CLI.
- Vault notes created, searched, or updated via CLI
- Plugin reload and debug output
By the numbers
- 4-step plugin develop/test cycle
Files
Obsidian CLI
Use the obsidian CLI to interact with a running Obsidian instance. Requires Obsidian to be open.
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:
obsidian create name="My Note" content="Hello world"Flags are boolean switches with no value:
obsidian create name="My Note" silent overwriteFor 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
Commands target the most recently focused vault by default. Use vault=<name> as the first parameter to target a specific vault:
obsidian vault="My Vault" search query="test"Common patterns
obsidian read file="My Note"
obsidian create name="New Note" content="# Hello" template="Template" silent
obsidian append file="My Note" content="New line"
obsidian search query="search term" limit=10
obsidian daily:read
obsidian daily:append content="- [ ] New task"
obsidian property:set name="status" value="done" file="My Note"
obsidian tasks daily todo
obsidian tags sort=count counts
obsidian backlinks file="My Note"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:
obsidian plugin:reload id=my-plugin2. Check for errors — if errors appear, fix and repeat from step 1:
obsidian dev:errors3. Verify visually with a screenshot or DOM inspection:
obsidian dev:screenshot path=screenshot.png
obsidian dev:dom selector=".workspace-leaf" text4. Check console output for warnings or unexpected logs:
obsidian dev:console level=errorAdditional 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-colorToggle mobile emulation:
obsidian dev:mobile onRun obsidian help to see additional developer commands including CDP and debugger controls.
Related skills
Lark SharedWire Feishu/Lark Open Platform auth, tokens, and shared API helpers into agent-built bots and internal tools.514k
Runcomfy CliLet their coding agent call any RunComfy model from the terminal or scripts without managing separate SDKs.298k30
Skills CliDiscover, install, update, and manage reusable agent capabilities from the open Skillselion ecosystem directly inside their coding agent.270k71TzstCreate, extract, list, and script `.tzst` / `.tar.zst` archives from the terminal with the right compression, streaming, and conflict flags.267k71XdropPull files from an Xdrop share URL, decrypt them locally, and land outputs in a chosen directory with optional JSON for automation.266k71
WizardAuthor interactive bash setup wizards that open URLs, capture secrets, write .env upserts, and set GitHub Actions secrets step by step.104k202kFAQ
Does obsidian-cli need Obsidian open?
Yes, it requires a running Obsidian instance to execute commands.
Can it help develop plugins?
Yes, it supports reload, dev:errors, dev:screenshot, dev:dom, eval, and other developer commands.