organize

Organizing an Obsidian vault works by scanning for untagged markdown notes and root-level files, proposing YAML tags and destination folders based on your rules, and applying the moves only after you explicitly confirm the plan.

Adding missing YAML frontmatter is handled by applying rule-driven categorization to each note, generating a specific tagging proposal, and writing the YAML tags into the file metadata before moving it into the correct folder.

Yes, you can review file moving proposals because the Skill generates a per-note plan detailing the move, tags, and rationale, and executes filesystem changes strictly after receiving explicit user confirmation.

Vault cleanup specifically targets untagged notes and markdown files sitting in the vault root, and explicitly avoids the special case of migrating external local files into the Obsidian vault.

Triage of root-level markdown files is achieved by applying organization rules from your Obsidian rules reference to determine the best destination folder and YAML tags for each file before proposing a move.