Obsidian 1

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.

Security Scan

The skill's requirements and instructions match its stated purpose (automating Obsidian via obsidian-cli); nothing requested is disproportionate, but it will read your Obsidian config and notes so you should only install it from a trusted brew tap.

Purpose & Capability

The skill is focused on automating Obsidian and only requires the obsidian-cli binary; that aligns with the name/description. Minor metadata inconsistency: registry Owner ID (kn78z...) differs from _meta.json ownerId (kn70py...), which is likely an editorial/packaging error and should be checked.

Instruction Scope

SKILL.md explicitly instructs reading the user's Obsidian configuration file at ~/Library/Application Support/obsidian/obsidian.json to discover vaults — this is coherent for the stated task but means the skill will read user files (vault paths and config). The guidance is macOS-centric (the path is macOS specific) while the skill has no OS restriction; that may cause failures on non-mac systems.

Install Mechanism

Install uses a brew formula (yakitrak/yakitrak/obsidian-cli). Brew formulas are lower-risk than arbitrary downloads, but this is a third-party tap (yakitrak) rather than the official homebrew/core or upstream Obsidian release; you should review the formula/tap before installing.

Credentials

The skill requests no environment variables or credentials — proportional to its purpose. Its runtime behavior (reading files under your home directory) is expected for a vault-management tool.

Persistence & Privilege

The skill is not marked always:true, does not request elevated or cross-skill configuration, and is runnable only when invoked. No excessive persistence or privilege is requested.

Assessment

This skill appears to do what it says: automate Obsidian via obsidian-cli and read your Obsidian config/notes. Before installing: 1) Verify you trust the brew tap (yakitrak) and inspect the formula or tap repo for malicious build/install steps. 2) Be aware the skill will read ~/Library/Application Support/obsidian/obsidian.json and your vault files — treat this as access to potentially sensitive notes. 3) Confirm OS compatibility if you are not on macOS (the SKILL.md uses a macOS path). 4) If you want extra caution, inspect obsidian-cli source code or run installation in a sandbox/container.

Obsidian

Obsidian vault = a normal folder on disk.

Vault structure (typical)

• Notes: *.md (plain text Markdown; edit with any editor)
• Config: .obsidian/ (workspace + plugin settings; usually don’t touch from scripts)
• Canvases: *.canvas (JSON)
• Attachments: whatever folder you chose in Obsidian settings (images/PDFs/etc.)

Find the active vault(s)

Obsidian desktop tracks vaults here (source of truth):

• ~/Library/Application Support/obsidian/obsidian.json

obsidian-cli resolves vaults from that file; vault name is typically the folder name (path suffix).

Fast “what vault is active / where are the notes?”

• If you’ve already set a default: obsidian-cli print-default --path-only
• Otherwise, read ~/Library/Application Support/obsidian/obsidian.json and use the vault entry with "open": true.

Notes

• Multiple vaults common (iCloud vs ~/Documents, work/personal, etc.). Don’t guess; read config.
• Avoid writing hardcoded vault paths into scripts; prefer reading the config or using print-default.

obsidian-cli quick start

Pick a default vault (once):

• obsidian-cli set-default "<vault-folder-name>"
• obsidian-cli print-default / obsidian-cli print-default --path-only

Search

• obsidian-cli search "query" (note names)
• obsidian-cli search-content "query" (inside notes; shows snippets + lines)

Create

• obsidian-cli create "Folder/New note" --content "..." --open
• Requires Obsidian URI handler (obsidian://…) working (Obsidian installed).
• Avoid creating notes under “hidden” dot-folders (e.g. .something/...) via URI; Obsidian may refuse.

Move/rename (safe refactor)

• obsidian-cli move "old/path/note" "new/path/note"
• Updates [[wikilinks]] and common Markdown links across the vault (this is the main win vs mv).

Delete

• obsidian-cli delete "path/note"

Prefer direct edits when appropriate: open the .md file and change it; Obsidian will pick it up.