obsidian-vault-manager

Managing two Obsidian vaults with consistent frontmatter requires a unified YAML schema applied across both vaults. This skill enforces that schema and standardizes folder structures, ensuring metadata remains uniform whether notes are in work or personal vaults.

The best way to capture meeting notes into separate work and personal vaults is using an inbox processing workflow that routes notes to the correct vault. This skill ensures each captured note lands in the appropriate vault with proper metadata and cross-vault wikilinks.

Obsidian does not natively link separate vaults, but cross-vault linking via wikilinks can be established through consistent naming conventions and governance. This skill supports creating and maintaining those cross-vault wikilinks between dual vaults.

Setting up a daily review workflow across multiple Obsidian vaults involves standardizing lifecycle workflows and inbox processing for each vault. This skill provides the necessary governance to maintain review routines and organize notes consistently across both environments.

Automating Obsidian vault management with this skill requires Python and the pyyaml dependency to parse and enforce YAML frontmatter schemas. The Python scripts handle metadata validation and cross-vault operations to maintain consistent note structures.