AgentStack
SKILL verified MIT Self-run

Obsidian Cli

skill-doctormozg-claude-pipelines-obsidian-cli · by DoctorMozg

ALWAYS invoke when using the obsidian CLI tool to interact with a vault from the terminal. Triggers: obsidian CLI, vault command line, obsidian read/create/search from shell.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-doctormozg-claude-pipelines-obsidian-cli

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Obsidian Cli? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Overview

The obsidian CLI is an official command-line interface that requires Obsidian to be running. It allows reading, writing, searching, and inspecting vault notes from a shell.

When to Use

Invoke when running shell commands against an Obsidian vault, scripting vault operations, or checking note content from the terminal. Trigger phrases: "obsidian CLI", "vault command line", "obsidian read/create/search from shell".

When NOT to use

  • Obsidian is not running — the CLI requires the live Obsidian app to be open.
  • Programmatic vault reading without Obsidian running — use direct file reads instead.
  • OFM syntax questions with no shell interaction — use obsidian-markdown.

Core Process

  1. Verify Obsidian is running before issuing CLI commands.
  2. Use file= for wikilink-style resolution, or path= for exact path resolution.
  3. For multi-vault setups, add vault= to target a specific vault.

Techniques

Parameter conventions

  • Parameters use = syntax: file=NoteName, not --file NoteName.
  • Flags are boolean with no value: --copy, --silent, --total.
  • Multiline content uses \n and \t escape sequences.

File resolution

| Form | Meaning | | -------------- | ---------------------------------------------- | | file= | Resolves like a wikilink (search across vault) | | path= | Exact vault-root-relative path | | vault= | Target a specific vault (multi-vault setups) |

Read operations

  • obsidian read file= — print note content.
  • obsidian daily:read — read today's daily note.
  • obsidian search — full-text search.
  • obsidian tags — list all tags.
  • obsidian backlinks file= — list notes linking to this note.

Write operations

  • obsidian create file= content= — create a note.
  • obsidian append file= content= — append to a note.
  • obsidian daily:append content= — append to today's daily note.
  • obsidian property:set file= key= value= — set a frontmatter property.

Developer / inspection

  • obsidian plugin:reload name= — reload a plugin.
  • obsidian dev:errors — show console errors.
  • obsidian dev:screenshot — take a screenshot.
  • obsidian dev:dom — inspect the DOM.
  • obsidian dev:console — open the console.
  • obsidian eval code= — evaluate JavaScript in the Obsidian context.
  • obsidian dev:css — show applied CSS.

Common Rationalizations

N/A — reference skill.

Red Flags

  • Using --file syntax instead of file= — parameters use =, not --.
  • Running CLI commands when Obsidian is not open — the command will hang or error.
  • Using path= when file= would work — path= requires an exact vault-root-relative path and is brittle across vault reorganizations.

Verification

Run obsidian tags and confirm output. Obsidian must be running.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.