obsidian-vault-manager
Skill10 starsChanged 9 months agoMITView on GitHub
Manage local Obsidian vaults and markdown notes. Use when Codex needs to connect to local Obsidian vaults, register vault paths, or create/edit/refactor/search notes, frontmatter, links, tags, and attachments within a vault.
- Reads credentials
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lensetek/SkillForgetheir own version, first seen Sep 16, 2026
- raja-patnaik/obsidian-agenttheir own version, first seen Apr 3, 2026
- eugenepyvovarov/mcpbundler-agent-skills-marketplaceword for word, first seen Feb 15, 2026
Other versions3 projects use a version of this.
Word for word · 1
- eugenepyvovarov/mcpbundler-agent-skills-marketplace★ 12100% same
Edited · 0
None found.
Wrote their own version · 2
- raja-patnaik/obsidian-agent★ 76same name
- lensetek/SkillForge★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 8 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Add a vault manually when needed:
- Very specific: line 18
Run full Obsidian CLI command surface via obsidian subcommand (machine-first by default):
- Very specific: line 26
If <skill-root>/.. is skills, project_root is two levels above the skills folder (<skill-root>/../../..).
- Very specific: line 28
Keep the vault registry at .skills-data/obsidian-vault-manager/vaults.json.
- Very specific: line 29
Use .skills-data/obsidian-vault-manager/.env for SKILL_ROOT, SKILL_DATA_DIR, and per-skill env keys.
- Very specific: line 32
Write logs/cache/tmp under .skills-data/obsidian-vault-manager/logs, .skills-data/obsidian-vault-manager/cache, …
- Distinctive: line 33
Keep automation in <skill-root>/scripts and do not write outside <skill-root> and <project_root>/.skills-data/obsidian-vault-manager/ …
- Very specific: line 39
Ask the user for default working folder (relative path), defaulting to vault root (.).
- Distinctive: line 44
Use the configured working folder as the default root for searches and edits (do not roam the entire vault unless requested).
- Very specific: line 47
Keep internal links valid after rename/move.
- Very specific: line 53
Use rg --glob '*.md' <pattern> <vault_path> to find notes and references.
- Distinctive: line 58
Add YAML frontmatter when needed (tags, aliases, status).
- Distinctive: line 62
Keep headings and block IDs stable unless requested.
- Distinctive: line 63
When moving sections across notes, update inbound links and mentions.
- Distinctive: line 70
Keep attachment paths relative when possible.
- Distinctive: line 71
Update embeds and markdown links if a file is moved.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Obsidian Vault Manager
Quick start
- Register or discover vaults with Obsidian CLI first:
python3 scripts/vault_registry.py discover --mergepython3 scripts/vault_registry.py list
- Add a vault manually when needed:
python3 scripts/vault_registry.py add --path "/path/to/Vault" --name "Vault"
- Manage active workspace:
python3 scripts/vault_registry.py set-active --name "Vault"python3 scripts/vault_registry.py set-workdir --name "Vault" --workdir "path/inside/vault"python3 scripts/vault_registry.py active
- Run full Obsidian CLI command surface via
obsidiansubcommand (machine-first by default):python3 scripts/vault_registry.py obsidian --vault "Vault" search query="meeting notes"python3 scripts/vault_registry.py obsidian --raw --vault "Vault" read file="Project.md"
- Enable destructive commands with
--force-delete:python3 scripts/vault_registry.py obsidian --force-delete --vault "Vault" delete file="Old.md" permanent
- Pick a vault and confirm its path contains
.obsidian/for manual adds.
Local data and env
- If
<skill-root>/.. isskills, project_root is two levels above theskillsfolder (<skill-root>/../../..). Confirm with the user if unsure. - Store all mutable state under <project_root>/.skills-data/obsidian-vault-manager/.
- Keep the vault registry at .skills-data/obsidian-vault-manager/vaults.json.
- Use .skills-data/obsidian-vault-manager/.env for SKILL_ROOT, SKILL_DATA_DIR, and per-skill env keys.
- Install local tools into .skills-data/obsidian-vault-manager/bin and prepend it to PATH when needed.
- Install dependencies under .skills-data/obsidian-vault-manager/venv (python/node/go/php).
- Write logs/cache/tmp under .skills-data/obsidian-vault-manager/logs, .skills-data/obsidian-vault-manager/cache, .skills-data/obsidian-vault-manager/tmp.
- Keep automation in
<skill-root>/scripts and do not write outside<skill-root>and <project_root>/.skills-data/obsidian-vault-manager/ unless the user requests it.
Vault connection workflow
- Attempt CLI-first discovery with
scripts/vault_registry.py discover; keep.skills-data/obsidian-vault-manager/vaults.jsonas the skill-owned state. - Register or confirm vault entries in
vaults.json. - Set active vault with
scripts/vault_registry.py set-active --name <name>. - Ask the user for default working folder (relative path), defaulting to vault root (
.). - Save it with
scripts/vault_registry.py set-workdir --name <name> --workdir <relative/path>. - Confirm the chosen vault name, vault path, and working folder before edits.
Working rules
- Use the configured working folder as the default root for searches and edits (do not roam the entire vault unless requested).
- Edit only note content and attachments unless the user asks to change
.obsidiansettings. - Preserve existing frontmatter keys; add new keys without reordering unless requested.
- Keep internal links valid after rename/move; update
[[Wiki Links]]and markdown links. - For
obsidianpassthrough commands, destructive actions require explicit--force-deletewhen supported by the command. - Confirm before delete, rename, or bulk changes.
Common tasks
Search and review
- Use
rg --glob '*.md' <pattern> <vault_path>to find notes and references. - Summarize matching files before edits.
Create a note
- Choose a filename that matches the main title.
- Add YAML frontmatter when needed (tags, aliases, status).
- Save as UTF-8 with a trailing newline.
Edit or refactor
- Keep headings and block IDs stable unless requested.
- When moving sections across notes, update inbound links and mentions.
Rename or move
- Rename the file and update links across the vault.
- For wiki links, update
[[Old Name]]and[[path/Old Name|alias]].
Attachments
- Keep attachment paths relative when possible.
- Update embeds and markdown links if a file is moved.
Scripts
scripts/vault_registry.py: list, add, remove, set active, set default working folder, show active, discover vaults, and full CLI passthrough viaobsidiansubcommand; writes registry to.skills-data/obsidian-vault-manager/vaults.json(override with--project-rootor--data-root).scripts/obsidian_cli.py: machine-first wrapper used for structured command execution and CLI discovery.
References
references/obsidian-vaults.md: config locations and vault discovery details.references/obsidian-markdown-skill.md: upstream Obsidian markdown skill content (format rules, links, tasks).references/obsidian-json-canvas-skill.md: upstream JSON canvas skill content.references/obsidian-bases-skill.md: upstream Bases skill content.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

