Obsidian 1.0.0

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

Security Scan

The skill's requirements and runtime instructions match its stated purpose (managing Obsidian vaults via obsidian-cli); the only notable risk is installing a third‑party brew formula—otherwise it behaves as expected.

Purpose & Capability

Name/description (manage Obsidian vaults) aligns with the declared requirement (obsidian-cli) and the SKILL.md, which documents how to find the active vault and use obsidian-cli commands. Requiring obsidian-cli is proportionate and expected.

Instruction Scope

SKILL.md instructs the agent to read the Obsidian config at ~/Library/Application Support/obsidian/obsidian.json and to operate on vault files (*.md, .canvas, attachments). Reading that config and notes is necessary to locate and manage vaults, but it does mean the skill will access potentially sensitive personal notes and config data if invoked — this is expected for its purpose but worth noting for privacy.

Install Mechanism

Install uses a Homebrew formula from a third‑party tap (yakitrak/yakitrak/obsidian-cli). Using a non-official tap carries some risk because it will install binaries from that tap; verify the tap/formula source and trustworthiness before installing. No direct downloads or extract-from-URL steps are present in the skill bundle.

Credentials

No environment variables, credentials, or config paths beyond the user's Obsidian config and vault files are requested. The access asked for is proportional to the skill's stated function.

Persistence & Privilege

The skill is not forced always-on and does not request elevated or system-wide configuration changes. It is user-invocable and may be invoked autonomously (platform default), which is normal for skills.

Assessment

This skill is internally consistent: it needs obsidian-cli and reads your Obsidian config and vault files to do its job. Before installing: (1) confirm you trust the Homebrew tap 'yakitrak' and review the formula/source code for the obsidian-cli package, (2) be aware that running the skill will access and can modify your local notes and Obsidian config (back up sensitive vaults first), and (3) if you’re not on macOS or do not keep Obsidian in the documented path, verify how obsidian-cli determines vault locations. If you have any doubt about the brew tap, inspect the repo or run obsidian-cli in a controlled environment first.

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.