What problem does it solve?
Obsidian-based workflows require careful routing between vault operations, app actions, and git-backed backups. This skill automates and safely routes user intents to the appropriate backend (MCP vault operations, Obsidian CLI/app actions, or git sync), reducing friction and the chance of misrouted requests.
Core Features & Use Cases
- Routing policy: default to MCP for vault data operations; invoke Obsidian CLI/app actions when editor behavior is required; use CLI/git for backups and synchronization.
- Safe defaults and guidance: when intent is ambiguous, prefer MCP routing and provide clear guidance for app or sync actions.
- Practical scenarios: open, edit, or tag notes; apply frontmatter changes; back up vault to remote via Git.
Quick Start
Open a note in Obsidian from a URI and trigger a vault backup or sync when requested.