Skip to content

OpenClaw only

Obsidian

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.

  • Pass
  • Automation
  • Version 1.0.0

The facts

Publisher
Peter Steinberger
Runs on
OpenClaw only
Updated
May 18, 2026
Downloads on ClawHub
110.4k
Installs on ClawHub
4.1k
Stars
459
Category
Automation View on ClawHub

Security review

PassChecked on September 22, 2026

This skill is a straightforward Obsidian helper, with a visible third-party CLI install that users should trust-check before use.

The review is ClawHub’s, shown here as published. Diali does not edit it. Read the full audit on ClawHub

What it needs before the first run

Nothing to configure. It runs as soon as it is installed.

Install it on your Diali agent

  1. Open Skills in the dashboard

    Every plan includes the catalog. Search for the skill by name.

  2. Read the review, then install

    The verdict and summary above are shown again on the install screen. Pick the agent it goes on.

  3. Give it what it needs, then use it

    If the skill asks for credentials or settings, the dashboard collects them. The skill then runs inside the agent’s own sandbox.

From the skill’s README

Written by the publisher and shown as published on ClawHub.

Obsidian

Obsidian vault = a normal folder on disk.

Vault structure (typical)

  • Notes: *.md (plain text Markdown; edit with any editor)
  • Config: .obsidian/ (workspace + plugin settings; usually don’t touch from scripts)
  • Canvases: *.canvas (JSON)
  • Attachments: whatever folder you chose in Obsidian settings (images/PDFs/etc.)

Find the active vault(s)

Obsidian desktop tracks vaults here (source of truth):

  • ~/Library/Application Support/obsidian/obsidian.json

obsidian-cli resolves vaults from that file; vault name is typically the folder name (path suffix).

Fast “what vault is active / where are the notes?”

  • If you’ve already set a default: obsidian-cli print-default --path-only
  • Otherwise, read ~/Library/Application Support/obsidian/obsidian.json and use the vault entry with "open": true.

Notes

  • Multiple vaults common (iCloud vs ~/Documents, work/personal, etc.). Don’t guess; read config.
  • Avoid writing hardcoded vault paths into scripts; prefer reading the config or using print-default.

obsidian-cli quick start

Pick a default vault (once):

  • obsidian-cli set-default "<vault-folder-name>"
  • obsidian-cli print-default / obsidian-cli print-default --path-only

Search

  • obsidian-cli search "query" (note names)
  • obsidian-cli search-content "query" (inside notes; shows snippets + lines)

Create

  • obsidian-cli create "Folder/New note" --content "..." --open
  • Requires Obsidian URI handler (obsidian://…) working (Obsidian installed).
  • Avoid creating notes under “hidden” dot-folders (e.g. .something/...) via URI; Obsidian may refuse.

Move/rename (safe refactor)

  • obsidian-cli move "old/path/note" "new/path/note"
  • Updates [[wikilinks]] and common Markdown links across the vault (this is the main win vs mv).

Delete

  • obsidian-cli delete "path/note"

Prefer direct edits when appropriate: open the .md file and change it; Obsidian will pick it up.

Get started

Give a skill an agent to run on

Every plan includes the skills catalog, every channel and every connector. Build an agent and install your first skill from the dashboard.