Obsidian CLI (kepano)

Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme d...

Security Scan

The skill's instructions match an Obsidian CLI helper, but the manifest omits that the obsidian CLI/binary is required and the runtime instructions allow arbitrary JS and full-vault access (possible exfiltration) — review before installing.

Purpose & Capability

The SKILL.md describes an Obsidian CLI helper and developer tooling (create/read/search notes, plugin dev, eval, screenshots). That purpose is coherent with the instructions. However the registry metadata lists no required binaries while the runtime instructions explicitly require the `obsidian` CLI and a running Obsidian instance — a small but notable mismatch.

Instruction Scope

The instructions direct the agent to run the obsidian CLI against the user's vault and include developer commands that can run arbitrary JavaScript in the app context (obsidian eval), read all files (app.vault.getFiles() and file/path targeting), take screenshots, inspect DOM, and copy output to clipboard. Those capabilities are consistent with plugin development but also allow reading or exporting arbitrary vault content; nothing in SKILL.md constrains or sanitizes what the agent may capture or transmit.

Install Mechanism

This is an instruction-only skill with no install spec and no code written to disk, which is low-risk from an installation perspective.

Credentials

The skill requests no environment variables or credentials (appropriate). However, it implicitly requires access to the user's Obsidian vault files and a running Obsidian app; the manifest does not declare the required `obsidian` binary, which is an omission that reduces clarity about runtime requirements.

Persistence & Privilege

The skill is not marked always:true and doesn't request special platform-wide persistence or configuration changes. Autonomous invocation is allowed by default but not combined with additional privileges in this skill.

What to consider before installing

This skill is mostly what it says — a helper for the Obsidian CLI and plugin development — but be cautious: the instructions allow running arbitrary JavaScript inside your Obsidian app and reading any file in your vault (and copying or screenshotting output). The registry metadata failing to list the required `obsidian` CLI is a minor inconsistency. Only install if you trust the skill author; avoid invoking developer commands that run eval or access sensitive notes unless you test in a disposable vault first. Consider restricting the agent's autonomy (do not allow it to run commands without confirmation) and review any outputs the agent plans to send externally.

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 overwrite

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

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-plugin
   

2. Check for errors — if errors appear, fix and repeat from step 1:

   obsidian dev:errors
   

3. Verify visually with a screenshot or DOM inspection:

   obsidian dev:screenshot path=screenshot.png
   obsidian dev:dom selector=".workspace-leaf" text
   

4. 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

Run obsidian help to see additional developer commands including CDP and debugger controls.