Wiki Mode is one of the skills in the claude-obsidian plugin. It tells the agent which filing method a vault uses and suggests a destination for a planned note under Generic, LYT, PARA or Zettelkasten.
Changing the mode is a reviewed two-step operation: a preview of the exact file that changes, then an apply that needs the approval hash. Existing notes are never moved or rewritten.
What You Get
- The current vault mode and its configuration
- A suggested destination for a new concept or source note under the chosen method
- Templates for LYT atomic notes and maps of content, PARA projects, areas and resources, and Zettelkasten atomic notes
- A mode change shown as a preview first and applied only with the approval hash
- A guarantee that switching mode affects future notes only
Common Use Cases
- Finding out which method a vault currently uses
- Switching a vault from Generic to PARA or LYT
- Asking where a new concept page should live before saving it
- Starting a Zettelkasten vault with time-sortable note identifiers
What Makes It Unique
Most Obsidian setups bake one folder scheme into a template. This skill makes the method a setting and routes new notes by it, while old notes stay where they are. The mode change goes through a dry run and an approval hash, and the skill refuses to guess when its config file is invalid.
Under The Hood
The skill loads its SKILL.md and, when needed, one of the bundled templates. It runs Python helper scripts from the installed plugin: a mode helper for reading the mode and suggesting routes, and the plugin core to preview and apply a mode change. The only file a change touches is the vault’s mode configuration. It does not fetch web pages or call APIs, and the route suggestions are text only. The scripts live in the wider plugin, outside this skill’s own folder.