obsidian-vault-config

Symlink a shared Obsidian config directory into multiple vaults using a bash script.

2|Updated Sep 14, 2026
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill obsidian-vault-config-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: obsidian-vault-config
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/obsidian-vault-config
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill obsidian-vault-config-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Managing plugins, themes, and settings across multiple Obsidian vaults normally means duplicating configuration by hand, which drifts out of sync and silently forks when Obsidian rewrites its config files. This Skill keeps one shared config at ~/.obsidian-shared and symlinks it into every vault so a change made anywhere applies everywhere. ## Core Features & Use Cases - Shared config linking: Symlinks plugins/, themes/, snippets/, and the settings JSON files (app, appearance, hotkeys, core-plugins, community-plugins) into each vault's .obsidian directory while leaving per-vault files like workspace.json alone. - Health checks and repair: The --check flag reports DETACHED entries where Obsidian replaced a symlink with a real file, and --relink-all restores the links with automatic timestamped backups. - Safe operation: The script refuses to link while Obsidian is running, is idempotent on re-runs, and never deletes displaced files. - Use Case: You create a new vault and want it to have every plugin, theme, and hotkey your other vaults use. Run obsidian-link on the new vault path and it opens fully configured with no manual setup. ## Quick Start Ask the agent to link your new Obsidian vault into the shared config so it inherits all shared plugins, themes, and settings.

Frequently Asked Questions about obsidian-vault-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share Obsidian plugins and settings across multiple vaults?▼

Keep one shared config directory at ~/.obsidian-shared and symlink its plugins, themes, snippets, and settings JSON files into each vault's .obsidian folder. The obsidian-link script automates this and registers each vault for later re-linking.

How do I onboard a new Obsidian vault with my existing setup?▼

Run obsidian-link followed by the new vault's path. The script creates .obsidian if absent and symlinks every shared entry, so the vault opens with all shared plugins, themes, hotkeys, and settings already active.

Why did my Obsidian vault settings stop syncing with other vaults?▼

Obsidian sometimes replaces a symlink with a real file when it rewrites its config, detaching that vault from the shared setting. Run obsidian-link --check to find DETACHED entries, quit Obsidian, then run --relink-all to restore the links.

Can I run obsidian-link while Obsidian is open?▼

No. The script refuses to link while Obsidian is running because Obsidian rewrites its config on exit and would overwrite the fresh symlinks. Quit Obsidian first; --check and --list are read-only and safe anytime.

Which Obsidian config files should stay per-vault instead of shared?▼

Keep workspace.json, graph.json, and templates.json per-vault. workspace.json tracks open panes and thrashes when two vaults are open, and templates.json holds a vault-relative folder path. Never symlink the entire .obsidian folder.