DoAny
Sign Up
O

obsidian

Verified

by openclaw · Updated Apr 16, 2026

opus
329in4.3Kout
$0.481m 38s

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

obsidianmarkdownnotesknowledge-managementvaultscli

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. need the Obsidian note cleanup done now before eng review — rename Agent Runtime to Execution Engine, put it under Architecture, remove the duplicate draft, and send me a quick summary

I'll start by exploring the codebase and understanding the Obsidian vault structure.

Let me find the vault and locate the relevant notes.

The vault is right in the working directory. Let me explore the structure and read the relevant files.

Good — I can see the top-level Agent Runtime.md and the duplicate Drafts/Agent Runtime.md. Let me read all the relevant files.

Now I have the full picture. I need to:

  1. Rename Agent Runtime.md to Execution Engine.md and move it under Architecture/
  2. Update all [[Agent Runtime]] wikilinks across the vault to [[Execution Engine]]
  3. Delete Drafts/Agent Runtime.md
  4. Update Index.md

Let me first set a default vault for obsidian-cli, then use obsidian-cli move to handle the rename + wikilink updates.

The working directory vault isn't registered in Obsidian, so I'll handle the rename, move, and link updates directly on the files.

Now update the title in the moved note and replace all [[Agent Runtime]] wikilinks across every file.

Need to read the moved file first, then edit it.

Now delete the duplicate draft.

Now let me verify everything looks correct.

All done. Here's the summary:

Vault cleanup complete:

  • Renamed Agent Runtime.md → Architecture/Execution Engine.md — title and body updated to "Execution Engine"
  • Moved the note into Architecture/ alongside System Overview.md
  • Updated wikilinks in all 3 referencing notes (System Overview, Q2 Roadmap, Index) — [[Agent Runtime]] → [[Execution Engine]] (7 link occurrences total)
  • Deleted Drafts/Agent Runtime.md (the old scratch/TODO draft that was superseded)
  • Verified zero remaining references to "Agent Runtime" across the vault

The vault is clean for eng review.

Claude Sonnet 4.6

External Tools

ToolType
obsidian-clibinary

Permissions

ScopeDescription
filesystem:read
filesystem:write
process:spawn

SKILL.md

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.

FAQ

What does obsidian do?

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

When should I use obsidian?

Use it when you need a repeatable workflow that produces text report, code diff.

What does obsidian output?

In the evaluated run it produced text report, code diff.

How do I install or invoke obsidian?

openclaw skills install obsidian

Which agents does obsidian support?

OpenClaw

What tools, channels, or permissions does obsidian need?

It uses obsidian-cli; channels commonly include text, diff; permissions include filesystem:read, filesystem:write, process:spawn.

Is obsidian safe to install?

Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.

How is obsidian different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does obsidian outperform not using a skill?

About obsidian

When to use obsidian

You need to search, create, move, or delete notes in an Obsidian vault from an agent workflow. You want note renames or moves to preserve wikilinks and Markdown links across the vault. You need to locate the active or default Obsidian vault on disk before editing notes.

When obsidian is not the right choice

You only need generic Markdown file editing without any Obsidian-specific vault discovery or link-aware refactoring. Obsidian CLI is not installed or the task depends on cloud APIs rather than local vault files.

What it produces

Produces text report and code diff.

Install

openclaw skills install obsidian

Invoke: Use obsidian when you want the agent to follow this workflow.