wiki is the entry point of the claude-obsidian plugin. It creates a new vault or adopts an existing Obsidian vault without moving your notes, shows a preview of every path it would change, and applies only after you approve the plan hash.
After setup it routes requests to ingest, query, save, autoresearch, lint, fold or canvas, and keeps every vault change inside one inspected, recoverable transaction.
What You Get
- A new vault or an adopted existing one, created after a dry-run preview
- A routing table that sends each request to the matching wiki skill
- Optional scaffold profiles for six kinds of knowledge work
- Reference notes on frontmatter, provenance, Git checkpoints and optional plugins
- An operation ID and exact changed paths after every applied change
Common Use Cases
- Starting a second brain in a new folder
- Adopting an existing Obsidian vault for use with Claude Code
- Adding a software, research or project scaffold to a vault
What Makes It Unique
Setup is non-destructive and dry-run by default, uses no network access, creates no Git remote, and refuses to overwrite without reviewed approval. Every mutation uses a hash-bound transaction with recovery, and parallel helper agents can only return drafts. A bundled reference set explains how optional Obsidian plugins, a CLI and REST or MCP transports fit in, always as read-only extras.
Under The Hood
The skill is instructions plus a set of reference files. It runs the plugin’s Python core script through the shell for help, init, adopt and an optional Git checkpoint, and those commands create or change files in the vault folder you select, only after you approve the plan hash. It does not fetch templates or remote content unless you separately approve the destinations. Some references describe optional steps such as initializing Git, installing community plugins or enabling a local REST adapter, all gated on your approval.