Security audit
Security checks for vulnerabilities and agentic risk
This skill transparently helps an agent read and update Obsidian notes with typed links, with approval required by default before writing.
Install this only for vaults you are comfortable letting an agent read. Keep the default review-before-write workflow for important notes, and use autonomous mode only on a scoped folder or after backing up/versioning the vault.
The skill explicitly instructs the agent to run local shell commands (which obsidian, obsidian version, and other obsidian ... commands) during normal operation. That expands the skill from simple file reading/writing into command execution against the host environment, which increases attack surface and can violate least-privilege expectations for a vault-linking skill.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
2. Link spoke notes into hubs before looking for lateral spoke-to-spoke connections
3. Hub-to-hub relationships (e.g., one concept is `prerequisite_for` another) are often the highest-value links in the vault
If the vault doesn't have hub notes but should, suggest creating them — but don't create them without approval.
### Step 2: Read and Summarize