Obsidian
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent for managing local Obsidian Markdown vaults, but users should remember it can read, edit, move, and delete private notes through an external CLI.
This appears safe to install if you want an agent to help manage Obsidian vaults. Before use, make sure you trust the obsidian-cli package, limit use to vaults you are comfortable exposing to the agent, and ask for confirmation before creating, moving, or deleting notes.
Findings (3)
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.
Installing the skill may install and rely on a third-party command-line tool that can access and modify Obsidian vault files.
The skill depends on installing an external Homebrew CLI package. This is expected for an obsidian-cli skill, but the CLI's provenance and updates are outside the instruction-only artifacts.
Install specifications: [0] brew | formula: yakitrak/yakitrak/obsidian-cli | creates binaries: obsidian-cli
Install obsidian-cli only from a source you trust and keep normal package-manager update hygiene.
Private note snippets could be exposed to the agent during use, and note text should not automatically be treated as trusted instructions.
The skill can bring local note contents into the agent's working context. That is purpose-aligned for Obsidian search, but notes may contain private information or untrusted text.
`obsidian-cli search-content "query"` (inside notes; shows snippets + lines)
Use the skill only on vaults you intend the agent to read, and review sensitive search results before sharing or acting on them.
A mistaken move or delete command could alter notes or links across the vault.
The documented CLI operations can mutate or delete vault content. This is expected for an Obsidian automation skill and is not shown as automatic or hidden.
`obsidian-cli move "old/path/note" "new/path/note"` ... `obsidian-cli delete "path/note"`
Confirm the target vault and note paths before move/delete operations, and keep backups or Obsidian sync/version history enabled.