obsidian-vault-gateway

You can automate Obsidian vault access securely by using a gateway skill that requires explicit permission for read operations and per-operation confirmation for any write actions like creating or editing notes.

Yes, managing Obsidian markdown notes and JSON canvas files programmatically is possible because the gateway delegates tasks to specialized sub-skills like obsidian-markdown and json-canvas based on the request type.

The best way to structure AI-driven vault operations is through a gated delegation workflow where read operations require initial permission and write operations require per-operation confirmation to ensure vault safety.

Yes, the gateway supports the PARA structure and existing templates by automatically loading vault structure knowledge via the dedkat-vault skill at initialization to understand your conventions.

When no specialized skill matches your vault edit request, the gateway falls back to direct vault access to execute the create, edit, move, delete, or append operation directly.

You need to confirm every write operation to ensure safe delegation and maintain a structured workflow, preventing unauthorized or accidental modifications to your Obsidian vault files.