Obsidian Vault Context
v1.0.1Teach Claude to use an Obsidian vault as a shared workspace with persistent state across sessions. Covers vault navigation, orchestration file management, ou...
⭐ 0· 66·0 current·0 all-time
byTristin E@tesfandiari1
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the content: the SKILL.md and reference docs explain how the agent should navigate, read, and write an Obsidian vault and how to set up optional headless sync. There are no unexpected environment variables, binaries, or installs declared that would be unrelated to the stated purpose.
Instruction Scope
The instructions explicitly direct the agent to read and write orchestration files inside the vault (e.g., _context/status.md, tasks.md, decisions.md) and to append rather than overwrite some files. Boundaries are stated (read/write only inside the vault, treat company/legal as read-only, do not modify skill/agent files). This is coherent, but it does grant the agent authority to create and update files in the user's vault automatically — users should be aware that the agent will persist session state to disk and may update status/tasks during sessions.
Install Mechanism
There is no install spec and no code in the package (instruction-only). The references describe installing Obsidian Headless (npm install -g obsidian-headless) as an optional, user-run step; nothing in the skill installs software automatically.
Credentials
The skill declares no required environment variables, credentials, or config paths. The optional Obsidian Headless reference correctly notes that the user will need Obsidian account credentials and Node.js if they choose headless sync; that requirement is documented in the references and is proportional to enabling bidirectional sync.
Persistence & Privilege
always is false and the skill does not request permanent elevated privileges. The skill instructs the agent to persist state into vault files (its explicit purpose). The only notable privilege is the agent's ability to autonomously write to the vault (the platform default) — this is expected for a vault-syncing skill but worth user attention.
Assessment
This skill is a coherent, instruction-only guide for using an Obsidian vault as the agent's persistent workspace. Before enabling it: (1) ensure the vault does not contain secrets or credentials you don't want the agent to touch; (2) if you enable Obsidian Headless, install it yourself and run it as an unprivileged user, use selective sync and E2EE, and be aware ob login stores credentials locally; (3) back up your vault before allowing automatic writes; (4) if you prefer the agent not to modify files, configure sync as pull-only or disable autonomous writes; and (5) review the orchestration files (status.md, tasks.md, decisions.md) to confirm the agent's update rules match your expectations.Like a lobster shell, security has layers — review code before you run it.
latestvk971h94jf9mf1dee21rqf7hwvx83nhna
License
MIT-0
Free to use, modify, and redistribute. No attribution required.