obsidian-direct

The skill's stated purpose to automate Obsidian vault interactions is coherent, but the implementation outline introduces a significant data flow concern by routing vault operations through an external API. This external dependency shifts trust away from the user’s local environment to a remote service, elevating data exposure risk for vault content and metadata. Credential handling relies on an environment variable and is not described with per-operation scoping or safeguards. Overall, the footprint is suspicious rather than benign: it enables powerful vault manipulation and routes data externally without explicit security controls or data-handling guarantees. If used, it should be restricted to trusted environments, with clear data handling, encryption, access controls, and preferably local-first operation or audited, verifiable external service integrators.