Obsidian
Work with Obsidian vaults using the official obsidian CLI: read/search/create/edit notes, tasks, links, properties, plugins.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Obsidian when an AI agent needs a reusable SKILL.md workflow for this job: Work with Obsidian vaults using the official obsidian CLI: read/search/create/edit notes, tasks, links, properties, plugins.
When not to use it
Skip Obsidian when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/obsidian # Save SKILL.md to ~/.claude/skills/obsidian/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/obsidian/SKILL.md. For a shared project, commit the folder at .claude/skills/obsidian/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Obsidian skill for this task: Use Obsidian when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 73/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Obsidian
Use the official `obsidian` CLI for Obsidian vault work. Vault files are plain Markdown, so direct file edits are still fine when safer/faster.
## Requirements
- Obsidian 1.12.7+ installed. - Settings -> General -> Command line interface enabled. - `obsidian` registered on PATH. - Obsidian app running; the CLI connects to the running app.
Check:
```bash obsidian version obsidian help ```
macOS registration creates `/usr/local/bin/obsidian` pointing at the app-bundled CLI. Linux registration copies the binary to `~/.local/bin/obsidian`.
## Vault model
- Notes: `*.md`. - Config: `.obsidian/`; avoid editing unless asked. - Canvases: `*.canvas` JSON. - Attachments: vault-configured folder. - Multiple vaults are common; pass `vault="<name>"` when ambiguous.
Obsidian desktop tracks vaults here:
- `~/Library/Application Support/obsidian/obsidian.json`
## Command pattern
```bash obsidian <command> [name=value] [flag] obsidian vault="Notes" search query="meeting notes" format=json ```
Parameter values with spaces need quotes. Add `--copy` to copy output where useful.
## Common commands
Open/read:
```bash obsidian open file=Recipe obsidian open path="Inbox/Idea.md" newtab obsidian read obsidian read file=Recipe ```
Search:
```bash obsidian search query="TODO" matches obsidian search query="status::active" format=json obsidian search:open query="project notes" ```
Create/modify:
```bash obsidian create name="New Note" obsidian create path="Inbox/Idea.md" content="# Idea" obsidian append file=Note content="New line" obsidian prepend file=Note content="After frontmatter" ```
Move/delete:
```bash obsidian move file=Note to=Archive/ obsidian move path="Inbox/Old.md" to="Projects/New.md" obsidian delete file=Note ```
Daily/tasks:
```bash obsidian daily obsidian daily:read obsidian daily:append content="- [ ] Review inbox" obsidian tasks all todo obsidian task file=Note line=8 done ```
Properties/links:
```bash obsidian tags all counts obsidian property:read file=Note name=status obsidian property:set file=Note name=status value=done obsidian backlinks file=Note obsidian unresolved verbose counts ```
Developer/debug:
```bash obsidian plugin:reload my-plugin obsidian dev:errors obsidian dev:screenshot file=shot.png obsidian eval "app.vault.getFiles().length" ```
## Notes
- `file=<name>` uses Obsidian-style file resolution; `path=<vault-relative.md>` is exact. - Prefer CLI move/delete/property commands for Obsidian-aware updates. - Prefer direct Markdown edits for bulk text changes after locating the vault path. - Do not rely on third-party `obsidian-cli` unless user explicitly asks for it.
Intended uses
- Use Obsidian when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.