obsidian

Verified

by elizaOS · Updated Apr 16, 2026

claude-opus-4-6

14in5.7Kout

$0.383m 41s

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli. Use when the user asks about notes, vault management, PKM, knowledge base organization, wikilinks, or personal knowledge management in Obsidian.

obsidianmarkdownnotespkmknowledge-basevaults

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. hey retro's this afternoon — can you clean up the Sprint 24 obsidian note, move the right one into Projects/Engineering, keep links working, and tell me what changed

Let me read all the relevant files:

Good — I've got the full picture. Here's the plan:

The work-vault Sprint 24.md is the official team note (matches Sprint 23.md in Projects/Engineering/). That's the one to move.
The personal-vault Sprint 24.md is your private scratch notes — leaving that alone.
I'll clean up the work-vault note to match Sprint 23's structure, move it into Projects/Engineering/, and update links in the files that reference it.

Let me do it:

Now move the file and update all references:

Now update the wikilinks in all files that reference Sprint 24:

Let me verify everything looks right:

Everything's clean. Here's what changed:

What I did

1. Moved work-vault/Sprint 24.md → work-vault/Projects/Engineering/Sprint 24.md Now lives alongside Sprint 23.md where it belongs. (Left your personal-vault/Sprint 24.md scratch notes untouched.)

2. Restructured the note to match Sprint 23's format (retro-ready)

"Committed Items" → split into "Completed Items", "Deferred", and "Carry-over" — each ticket now has outcome context (merged when, why deferred, how long blocked)
"Notes" section removed — that info was folded into the items themselves
"Retro Topics (draft)" → "Retro Summary" with proper What went well / What to improve / Actions structure matching Sprint 23's format — actions section left blank for you to fill during retro
"Carry-over from Sprint 23" renamed to just "Carry-over" with a "(3rd sprint)" flag to support the escalation conversation

3. Updated all wikilinks across 3 files

Standup Notes.md — 3 links: [[Sprint 24]] → [[Projects/Engineering/Sprint 24]]
Retro Action Items.md — 1 link: same update
Inside Sprint 24 itself: [[Projects/Engineering/Sprint 23]] → [[Sprint 23]] (since they're now siblings in the same folder, shortest-path linking applies per your Obsidian config)

Good luck at retro — the ENG-389 escalation is long overdue 🙂

Claude Sonnet 4.6

Preview

No preview available

Sprint 24.md1 KB work-vault_Retro Action Items.md.diff0 KB work-vault_Standup Notes.md.diff1 KB

External Tools

Tool	Type
obsidian-cli	binary

Permissions

Scope	Description
filesystem:read
filesystem:write
filesystem:delete
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

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?

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?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does obsidian support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does obsidian need?

It uses obsidian-cli; channels commonly include text, diff; permissions include filesystem:read, filesystem:write, filesystem:delete, 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. You want to refactor note paths while preserving wikilinks and Markdown links. You need to locate the active or default Obsidian vault on disk.

When obsidian is not the right choice

You need to work with a cloud note system or external knowledge base service rather than local Obsidian vaults. You only need generic Markdown file editing without Obsidian-specific vault or link-management behavior.

What it produces

Produces text report and code diff.