obsidian-file-manager
Pass
Audited by Gen Agent Trust Hub on Mar 11, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill manages an Obsidian vault by reading and writing markdown files. While processing external content presents a surface for indirect prompt injection, the skill uses structured YAML frontmatter and clear document boundaries to manage content. Ingestion points like
scripts/lib/obsidian_client.rbread data that is bounded by---delimiters, and capabilities are restricted to local file operations. - [SAFE]: User-provided parameters for document types and project names are validated against whitelists in
FileNamerbefore being used in file path generation or metadata creation. - [SAFE]: Sensitive information, specifically the Obsidian API key, is handled via an external configuration file. The documentation explicitly instructs users to set restricted file permissions (chmod 600) to protect this data.
- [SAFE]: Communication with the Local REST API occurs over HTTPS to localhost. The client is configured to accept self-signed certificates, which is the standard configuration for the Obsidian Local REST API plugin.
- [SAFE]: The skill uses
YAML.safe_loadfor parsing file metadata, preventing unsafe deserialization attacks. - [SAFE]: The documentation suggests optional integration with cron for automated archival tasks. This is a standard system administration pattern for maintenance scripts and does not involve hidden persistence or privilege escalation.
Audit Metadata