meta-sync-templatelisted

Interactive flow to propagate the reference (`.template`) vault's plugins, snippets, and root docs to one or more configured vaults. Reads the active router config, lists every vault with online status, flags vaults missing `obsidian-local-rest-api` upfront, lets the user pick all or a subset, and optionally re-clones with `--force`. Use whenever the user says "propagate the template", "sync vaults with template", "propage la config du template aux autres vaults", "mets à jour les vaults avec la config du template", "diffuse les plugins du vault de référence", "/obsidian-router:meta-sync-template", or any phrasing implying the reference vault should be the source of truth for plugins/config across the fleet.
tboome33/obsidian-mcp-router · ★ 1 · AI & Automation · score 74

Install: claude install-skill tboome33/obsidian-mcp-router

# meta-sync-template Interactive bulk propagation of the reference vault (typically `.template`) to one or more configured vaults. Conversational picker over `scripts/setup-vault.mjs`'s `--sync-all` and `--sync-plugins` modes with up-front diagnostics (online/offline status, REST-API-plugin presence per target). **Which command runs** (moved out of the frontmatter, which the Agent Skills spec caps at 1024 characters): the router config comes from the `OBSIDIAN_ROUTER_CONFIG` env var, defaulting to `~/.claude/obsidian-mcp-router/config.json`. The all-vaults case runs `npm run setup-vault -- --sync-all` (the script auto-skips the reference vault and refuses to leak credentials); subsets loop `scripts/setup-vault.mjs <path> --sync-plugins`. Flagging a missing `obsidian-local-rest-api` before anything runs lets the user bootstrap that vault first rather than meet a runtime warning mid-sync. **Safety**: as of obsidian-mcp-router v0.11.2+, the underlying script itself enforces every safety invariant this skill cares about — it refuses to sync the reference vault onto itself (case-insensitive on Windows / macOS), and it refuses to first-time-copy `obsidian-local-rest-api` into a target lacking it (the copy would clone the reference's `data.json` and leak the API key). The skill's role is purely UX: a friendly picker, clear pre-flight info, per-vault aggregation. The hard safety guarantees live in `setup-vault.mjs` (`samePath()` check at `syncPluginsMode` entry; `CREDENTIAL_LEAK_P