Obsidian Knowledge Vault Organizer

Reorganize an Obsidian vault without fear of breaking it. This skill works from a text listing you paste — folder tree, note names, tag counts — and returns three things: a diagnosis with numbers, a target structure chosen for how you actually use the vault, and a phased, reversible migration plan you execute by hand inside Obsidian.

Nothing in this skill reads, moves, renames, or deletes your files. There is no script. That is a deliberate safety choice: a vault is years of thinking, and the person who understands each note is you. The agent designs the system and the sequence; your hands do the moves, inside the app, where links stay intact.

Ask these five questions before auditing or designing anything. Record the answers and put the profile at the top of every output. If the user already answered one, do not ask again. If they want to proceed with gaps, state the defaults you are using.

1. Vault size — Roughly how many notes? (Under 200 / 200–1,000 / 1,000–3,000 / over 3,000 — an estimate is fine.) How this changes the design: Size sets phase sizing. Under 200 notes migrate in 2–3 sittings. Over 1,000 notes need small batches per area and a longer Phase 2. Over 3,000 notes also get a stricter tag budget and archive-first sequencing, because finding things by browsing stops working at that scale.