wiki-switch skill | PlugMCP

wiki-switch

by Ar9av3.6k

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add Ar9av/obsidian-wiki --skill wiki-switch -a cursor -y

Download skill .skills/wiki-switch/SKILL.md on GitHub

Related skills

View all

Questions

How do I install wiki-switch?: Download .skills/wiki-switch/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does wiki-switch live?: The publisher keeps it at https://github.com/Ar9av/obsidian-wiki.
Which agents can use wiki-switch?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: wiki-switch description: > List, create, or switch named Obsidian wiki vault profiles under the global config directory. Use when changing the active vault, checking which vault is active, or managing multi-vault profiles.

Wiki Switch — Manage Multiple Vault Profiles

Global config dir. Every path below is relative to the global config dir, resolved per the Config Resolution Protocol in llm-wiki/SKILL.md: $XDG_CONFIG_HOME/obsidian-wiki (default ~/.config/obsidian-wiki), or the legacy ~/.obsidian-wiki if that already exists on disk. Resolve it once per invocation with:

CONFIG_DIR="$( [[ -d "$HOME/.obsidian-wiki" && ! -e "${XDG_CONFIG_HOME:-$HOME/.config}/obsidian-wiki" ]] && echo "$HOME/.obsidian-wiki" || echo "${XDG_CONFIG_HOME:-$HOME/.config}/obsidian-wiki" )"

Each vault is a complete config file at . The active vault is whichever file symlinks to. Switching vaults means re-pointing that symlink.

$CONFIG_DIR/config.<name>

$CONFIG_DIR/config

Invocation	Action
`/wiki-switch <name>`	→ Switch
`/wiki-switch list`	→ List
`/wiki-switch show [name]`	→ Show
`/wiki-switch new <name>`	→ New
`/wiki-switch` (no args)	→ List (treat as list)
`@<name> …` (inline, in any request)	→ Not this skill — the Config Resolution Protocol resolves that vault for one invocation without re-pointing the symlink

Verify $CONFIG_DIR/config.<name> exists. If not, tell the user the vault doesn't exist and list what's available (run List).

Run:

ln -sf "$CONFIG_DIR/config.<name>" "$CONFIG_DIR/config"

Read OBSIDIAN_VAULT_PATH from the newly active config.

Confirm to the user:

Switched to vault: <name>
Vault path: <value of OBSIDIAN_VAULT_PATH from the config>

Find all files matching $CONFIG_DIR/config.* (exclude config itself — that's the symlink).
Resolve the current symlink target: readlink "$CONFIG_DIR/config"
For each config file, read the first non-empty comment line (lines starting with #) as a human description of the vault. Fall back to the file's suffix as the label if no comment exists.
Display:
```
Vaults:
  personal   My personal research wiki    ← active
  work       Work projects wiki
```
Mark the active one with ← active. If the symlink is broken or config doesn't exist, show (none active).

Check $CONFIG_DIR/config.<name> doesn't already exist. Abort if it does.

Copy the active config:

cp "$CONFIG_DIR/config" "$CONFIG_DIR/config.<name>"

Read the copied config. Config files use # --- Section name --- comment headers to group fields into sections (e.g., # --- Vault-specific ---, # --- Vault-independent ---, # --- Secrets ---). Use these sections to determine what to ask about:
- Fields in sections labeled "vault-specific", "paths", or similar → ask the user for new values
- Fields in sections labeled "vault-independent", "global", "shared" → keep as-is (copy over unchanged)
- Fields in sections labeled "secrets" → ask if the new vault uses the same credentials or different ones
- If there are no section headers, present all fields and let the user decide which to change
Ask the user for updated values for the vault-specific fields. Use the current values as visible defaults — the user only needs to supply what differs.
Write the updated values into $CONFIG_DIR/config.<name>.
Update the top comment line to describe the new vault (e.g., # Obsidian Wiki — <name> vault).

Confirm:

Created: $CONFIG_DIR/config.<name>
Run `/wiki-switch <name>` to activate it, then run `wiki-setup` to initialise the new vault.

Do not switch automatically — let the user decide when to activate.

wiki-switch

Install

Related skills

Questions

name: wiki-switch description: > List, create, or switch named Obsidian wiki vault profiles under the global config directory. Use when changing the active vault, checking which vault is active, or managing multi-vault profiles.

Wiki Switch — Manage Multiple Vault Profiles

Dispatch

Switch (default action)

List

Show

New