This skill manages several Obsidian wiki vaults from one machine. Each vault is a config file named config.<name> in the obsidian-wiki config folder, and the active vault is whichever file the config symlink points to. The agent can list the profiles, show one, create one from the active config, or switch to another.
A switch changes your persistent default. For a single request against another vault, the inline @name override handled by the shared llm-wiki skill leaves the symlink alone.
What You Get
- A list of vault profiles with a one-line description each and the active one marked
- A switch that re-points the config symlink and confirms the vault path
- A new profile scaffolded from the active config, asking only for the vault-specific values that differ
- A show command that prints a profile with API key and secret lines replaced by asterisks
- Guidance on when to use the inline @name override for a one-off request
Common Use Cases
- Moving between a personal and a work wiki
- Creating a profile for a new vault from the current one
- Checking which vault is active before an ingest
- Reviewing a profile’s settings without exposing secrets
What Makes It Unique
The skill treats each vault as a complete config file and a switch as a single symlink change, so there is no profile database to keep in sync. It reads the section headers of the config to decide which values to ask for, copies shared settings unchanged, and leaves activation to the user after a new profile is created.
Under The Hood
The agent loads the SKILL.md and the shared llm-wiki skill for the config resolution rules. It runs small shell commands on your machine: ln to re-point the symlink, cp to copy a config, and readlink to find the active profile. It reads and writes files in the obsidian-wiki config folder under your home directory, including config files that may hold keys, and redacts key and secret lines when showing one. It makes no network calls.