What problem does it solve? Obsidian vaults accumulate notes with inconsistent frontmatter over time, and enforcing a schema across hundreds of notes by hand is error-prone and irreversible without backups. This Skill validates every note's frontmatter against a declared YAML schema and runs approval-gated migrations with a rollback manifest written before any change. ## Core Features & Use Cases - Schema Validation: Dispatches a validator agent to check every note against declared note_types, producing severity-labeled findings (Critical for missing required fields or enum violations, Nit for unknown keys). - Approval-Gated Migration: Converts Critical findings into a per-note migration plan with user-filled placeholders, writes a rollback manifest with content hashes before any write, and patches frontmatter only after explicit approval. - Schema Bootstrapping: When no schema exists at .mz/vault-schema.yml, presents a starter template with permanent, fleeting, and research note types for the user to accept, edit, or reject. - Use Case: After adding a required status field to your permanent notes schema, run migrate mode to backfill the field across all existing notes, reviewing each proposed patch and keeping a rollback manifest for recovery. ## Quick Start Ask the AI to validate your Obsidian vault's frontmatter against the schema at .mz/vault-schema.yml, or to run a schema migration with rollback protection.
