A Claude Code plugin for managing your Obsidian vault via CLI. Provides a set of skills for processing, organizing, and maintaining your knowledge base without leaving the terminal.
- Obsidian >= 1.12.4 with CLI enabled
- Obsidian installer must be up to date — if you see a warning like
Your Obsidian installer is out of date, download the latest installer from obsidian.md/download and reinstall (vault and settings are preserved). An outdated installer can cause CLI write commands to fail silently. - Obsidian must be running when using skills
- Claude Code
- Open Obsidian → Settings → General → Command line interface
- Toggle Register CLI on
- Verify:
obsidian versionin your terminal
On Windows, obsidian may resolve to Obsidian.exe (GUI version) instead of Obsidian.com (console version). The GUI exe breaks on subcommands with colon + parameters (property:set, daily:append, etc.) with exit code 127.
Fix: create a wrapper script at ~/bin/obsidian (ensure ~/bin is in your PATH):
mkdir -p ~/bin
cat > ~/bin/obsidian << 'EOF'
#!/usr/bin/env bash
exec '/c/Users/<username>/AppData/Local/Programs/Obsidian/Obsidian.com' "$@"
EOF
chmod +x ~/bin/obsidianA wrapper script works in both interactive and non-interactive shells (unlike aliases).
# Add the marketplace from GitHub
claude plugin marketplace add straintensor15/obsidian-brain
# Install the plugin
claude plugin install obsidian-brain@obsidian-brainclaude plugin marketplace add /path/to/obsidian-brain
claude plugin install obsidian-brain@obsidian-brainProcesses raw notes from _inbox/: determines topic, sets frontmatter and tags, finds related notes, adds wikilinks, moves to target folder with automatic link updates.
Typical flow:
- Drop notes into
_inbox/(after a meeting, lecture, or reading) - Run
/process-inbox - For each note: review the suggested name, tags, folder, and found connections
- Confirm or adjust the plan
- Notes are organized, linked with wikilinks, and indexed by Obsidian
Splits large notes (>10KB) into atomic notes and creates a Map of Content (MOC).
Typical flow:
- A 5000-word book summary sits in
literature/ - Run
/decompose(or the plugin will suggest candidates) - Review the plan: which sections become separate notes, which stay in the MOC
- Confirm
- Result: 8 atomic notes in
notes/+ MOC in_moc/with links
Three-stage duplicate search (by names → tags → content) with interactive merging.
Typical flow:
- Run
/dedup - Plugin finds pairs with varying confidence (high / medium / low)
- For each pair: view both files, choose the primary one
- Duplicate is archived to
_archive/merged/, all links updated automatically
Two modes:
analyze — graph diagnostics:
- Run
/cluster→ chooseanalyze - Get a report: hubs (most-linked notes), orphans, dead ends, broken links, weak clusters
- For each problem — a recommendation (create links, add to MOC, archive)
group — group into MOC/summary:
- Run
/cluster→ choosegroup - Plugin finds clusters of related notes (by tags, links, content)
- For each cluster: suggests MOC (different aspects) or a summary note (common thesis)
- Confirm composition and type → MOC in
_moc/or summary innotes/
Two modes:
quick — healthcheck in 30 seconds:
- Run
/audit→ choosequick - Three quick checks: orphans, broken links, singleton tags
- Brief report with numbers
full — full audit with fixes:
- Run
/audit→ choosefull - Checks across 5 categories: frontmatter, tags, links, placement, content
- Summary report with issue counts per category
- Choose: fix all / only category X / skip
- Interactive mode: for each issue — suggested fix → confirmation
Interactive refactoring of vault tag taxonomy.
Typical flow:
- Run
/rename-tags - See the full tag tree with note counts
- Plugin identifies: singleton tags, duplicates with different casing, flat tags that could become hierarchical
- Approve the rename plan (you can edit it)
- Tags renamed across the entire vault in one command
Interactive content improvement: structure, formatting, tables, rewrite, summary, wikilinks.
Typical flow:
- Run
/improveand specify a note - See the operations menu with relevance scores (high / medium / low)
- Select the desired operations
- For each operation: preview "before → after" → confirm or skip
- Final report of applied changes
Available operations:
| # | Operation | What it does |
|---|---|---|
| 1 | Structure | Headings, section reorganization, empty sections |
| 2 | Format | Bold terms, lists, callouts |
| 3 | Tabulate | Enumerations → markdown tables |
| 4 | Rewrite | Better phrasing, remove filler |
| 5 | Summarize | TL;DR with key theses |
| 6 | Wikify | Add [[wikilinks]] to existing notes |
Before first use, configure the reference files in references/ to match your vault:
# Copy the vault config template and edit it
cp references/vault-config.example.md references/vault-config.md
# Then open references/vault-config.md and set your vault path and folder structureReference files:
references/vault-config.md— your vault path and folder structure (gitignored, copy from.example.md)references/frontmatter-spec.md— frontmatter templates and field rulesreferences/cli-operations.md— Obsidian CLI commands referencereferences/interaction-patterns.md— interaction patterns (language, confirmations, reports)
_inbox/ ← Incoming notes (processed by /process-inbox)
notes/ ← Atomic notes
literature/ ← Book/course/article summaries
projects/ ← Project notes
_moc/ ← Maps of Content (navigation files)
daily/ ← Daily notes
_archive/ ← Archive (inactive + merged duplicates)
_templates/ ← Obsidian templates
_assets/ ← Attachments (images, PDFs)
- Files are never deleted — only archived
- Moving and renaming only happen after user confirmation
- Wikilinks are updated automatically via CLI when moving files
- All content is preserved — nothing is lost
- Git commits after each operation with specific file names
MIT