Agent skill · software engineering · jeremylongshore
obsidian-multi-env-setup
Configure multiple Obsidian environments for development, testing, and
Why this skill is useful
Adds specific commands and configurations for managing multiple Obsidian environments that the AI wouldn't reliably generate on its own.
What it needs
Requires git, node, obsidian installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Obsidian Multi-Environment Setup Overview Configure separate development, testing, and production vaults for Obsidian plugin work. Covers vault templates for team onboarding, environment-specific plugin settings, sync strategies, and .obsidian/ directory management across environments. Prerequisites Obsidian desktop app installed Node.js 18+ and npm/pnpm for plugin builds Git for version control (recommended) Basic understanding of symlinks and file system operations Instructions Step 1: Create the Environment Structure Set up three isolated vaults -- dev, test, and prod: Step 2: Symlink Plugin Source for Development In the dev vault, symlink your plugin's build output so changes appear immediately: For hot reload during development, use the Hot Reload plugin: Then enable both your plugin and hot-reload in .obsidian/community-plugins.json: Step 3: Environment-Specific Plugin Settings Each vault gets its own data.json for your plugin. Create a config factory: Use it in your plugin's onload(): Step 4: Vault Templates for Team Onboarding Create a template vault that new team members clone: Script to provision a new team member's vault: Step 5: Sync Strategies Choose based on your team's needs: Git sync (best for plugin developers): Pair with the Obsidian Git plugin for auto-commit/push on a schedule. Obsidian Sync (best for non-technical teams): Configure in Settings > Sync. Selective sync lets you exclude .obsidian/plugins/ on certain devices to prevent config conflicts. iCloud/Dropbox (simplest, most fragile): Place the vault inside the sync folder. Avoid editing on multiple devices simultaneously. .obsidian/ conflicts are common -- keep a backup. Step 6: Managing .obsidian/ Across Environments The .obsidian/ directory holds all configuration. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/obsidian-multi-env-setup--7a63e0