Obsidian Official CLI
ReviewAudited by ClawScan on May 10, 2026.
Overview
This looks like a legitimate Obsidian CLI reference, but it gives an agent broad note-vault control and developer-level commands like JavaScript eval without clear approval guardrails.
Install only if you want your assistant to operate your Obsidian vault. Before use, set clear rules requiring confirmation for delete, bulk edit, publish, plugin/theme/workspace changes, and especially `obsidian eval`; keep vault backups and verify any optional third-party install source.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent could change or delete notes, alter vault organization, or publish changed content if instructed or if it misinterprets a task.
The skill explicitly enables automatic agent control of the vault and documents destructive and publishing-capable commands. This is purpose-aligned, but the artifacts do not define approval, rollback, or scope limits for high-impact actions.
Your AI assistant can now read, write, and organize your Obsidian vault automatically. ... obsidian delete file="Old Note" ... obsidian publish:add changed
Use this skill with explicit rules that require confirmation before delete, bulk edit, publish, plugin/theme/workspace, or other irreversible actions.
If used carelessly, the agent could run arbitrary Obsidian JavaScript that reads or modifies many notes or changes app state.
The documented eval command can run JavaScript inside Obsidian, which is an escape-hatch capability beyond safer scoped note operations. The artifacts do not restrict it to read-only code or require explicit user approval.
obsidian eval code="app.vault.getFiles().length" # Run JavaScript
Do not allow `obsidian eval` unless you specifically request it and understand the code to be run; maintain a backup before allowing developer commands.
Private notes may be exposed to the assistant during tasks, and malicious or misleading text stored in notes could influence the assistant's behavior.
The skill can read and search vault content, which is expected for Obsidian automation, but vault notes may contain private information or prompt-like text that enters the agent's context.
obsidian read file="Recipe" obsidian search query="meeting"
Limit searches/reads to relevant vaults or folders, avoid using it on highly sensitive notes unless needed, and treat note contents as untrusted context.
Installing from an unverified third-party tap could run code or install files outside the reviewed skill artifacts.
The skill itself has no install spec that runs this, but the documentation suggests an optional third-party Homebrew tap while the registry source is listed as unknown.
brew tap alexanderkinging/tap brew install obsidian-cli-official
Prefer the official Obsidian app/CLI and verify any Homebrew tap or GitHub source before installing external wrappers.
A user or agent could over-trust the skill because of self-authored approval language.
The package includes self-approval and no-risk claims. These are not independent security assurances and should not override the actual artifact review.
✅ **通过验证，批准发布** ... ✅ 无风险因素 ... **置信度：** 100%
Treat bundled approval reports as author notes only, not as platform or independent security validation.