Obsidian Vault Ops

The problem

Managing a growing Obsidian vault through the GUI is slow for bulk operations. You cannot easily audit broken links, find orphaned images, or generate templated notes from the command line without manual friction.

What it does

• Locates and inventories the vault root to provide folder-level note counts.
• Executes recursive content searches across the entire vault to find specific terms or tags.
• Generates new Markdown notes with valid YAML frontmatter using pre-defined templates.
• Performs bulk link repairs to fix broken [[wikilinks]] after file renames or migrations.
• Identifies orphaned attachments and images that are no longer referenced in any note.

Frameworks & tools

Obsidian, Markdown, YAML, and standard shell utilities (grep, sed, find, awk).

Why this beats prompting it yourself

Standard LLMs often struggle with the specific syntax of Obsidian wikilinks and YAML frontmatter requirements. This skill uses verified shell patterns to ensure link replacements are precise and file operations do not corrupt your knowledge base.

Use cases

• Audit your vault to delete unused images and free up storage.
• Batch update links after reorganizing your folder hierarchy.
• Generate daily standup or meeting notes with consistent metadata automatically.
• Search your entire second brain for specific concepts without opening the app.

Known limitations

Does not support rendering notes to HTML/PDF or interacting with the Obsidian Sync service. Operates strictly on the local filesystem.