description: "Workflow for scanning and standardizing Obsidian note YAML frontmatter metadata schemas."

Obsidian Vault Metadata Standardizer Workflow (/maintenance-vault)

This workflow synchronizes and standardizes the YAML frontmatter of Markdown notes within the Obsidian Vault directory: /Users/keira/Documents/GitHub/Obsidian Vault Mac/.

🛠️ Execution Steps

1. Vault Directory Resolution

• Set active vault root to: /Users/keira/Documents/GitHub/Obsidian Vault Mac/
• Verify the existence of the core directories (10_Projects/, 20_Areas/, 30_Resources/).

2. Identify Note Categories & Schemas

Map each folder path to its designated YAML frontmatter schema: - 10_Projects/Consultancy/Wedding/T&J: yaml category: consultancy field: "wedding" project: "tj" tags: - consultancy type: note - 10_Projects/Consultancy/Others/ANMA: yaml category: consultancy field: "wellness" project: "anma" tags: - consultancy type: note - 10_Projects/Personal_Projects/VWG: yaml category: personal-project field: "wedding" project: "vwg" tags: - personal_project type: note - 20_Areas/Spiritual: yaml category: spiritual tags: - astrology - profile type: note - 20_Areas/Tech_Learning: yaml category: learning tags: - tech - ba type: note

3. Scan & Detect Anomalies

• Scan notes in the folders listed above.
• Detect files that:
• Are missing YAML frontmatter entirely.
• Have incomplete frontmatter fields.
• Contain mismatched tags/categories.

4. Safe Frontmatter Update

• Execute the local Python helper script: bash python3 "/Users/keira/Documents/GitHub/Obsidian Vault Mac/update_yaml.py"
• If the script is run directly by the agent, preserve existing frontmatter properties like Created: and merge the missing keys carefully to prevent data loss.
• NEVER overwrite the actual text body of a note.

5. Report & Log

• Print a clear checklist of all notes that were updated.
• Verify file formatting matches standard Obsidian properties display.