- Home
- Skills
- Productivity
- Obsidian Vault Assistant
Obsidian Vault Assistant
Search and update local Obsidian notes with source citations, backups, and conflict checks.
$3
Works with the AI Agents you already use
Obsidian Vault Assistant
Example session with this skill installed
Illustrative example using synthetic notes: connect to my SampleVault in read-only mode. Read Launch.md and Meeting.md, summarize the launch actions and dependencies, cite each source path, and do not modify any notes. Launch.md says Alex owns the launch, due 2026-11-05, and must confirm onboarding copy. Meeting.md says Sam will run the accessibility review by 2026-11-03; release depends on both items.
- Read your context and instructions
- Compiled the obsidian vault assistant
Launch action summary
Illustrative output based on the two synthetic notes supplied in the example prompt. This is a walkthrough, not a recorded production session.
The launch has two stated prerequisites: confirmation of the onboarding copy and completion of an accessibility review. The notes identify Alex as the launch owner and Sam as the accessibility-review owner.
| Action | Owner stated in notes | Due date stated in notes | Source |
|---|---|---|---|
| Own the launch | Alex | 2026-11-05 | Launch.md |
| Confirm onboarding copy | Not assigned separately | Not specified | Launch.md |
| Run accessibility review | Sam | 2026-11-03 | Meeting.md |
Dependencies and open questions
Meeting.md makes both onboarding copy and accessibility review prerequisites to release. The review date is two days before the launch date. The notes do not assign a separate owner or deadline for copy approval, so those details should be confirmed rather than inferred from Alex's launch ownership.
Next steps
- Ask who signs off on onboarding copy and when it must be ready.
- Confirm that the review result will be available before the launch decision.
- If a note update is later requested, switch to an authorized read-write connection, reread the target note, and use its current SHA-256 hash.
The requested workflow uses read-only access; no note edits are part of this example.
Connects securely to your tools. The creator never sees your data.
About this skill
Turn your local notes into usable knowledge
Search, read, create, edit, append, move, and delete Markdown notes in a vault you choose. Ask your agent to find project context, summarize meeting notes with source paths, or update a specific note while preserving its frontmatter and wikilinks.
What is included
- A standard SKILL.md workflow with English setup instructions.
- The complete local MCP server and the original Codex plugin.
- Nine tools, pinned Python dependencies, an installer, and disposable-vault verification checks.
- Read-only and read-write connections, pre-change backups, and SHA-256 conflict checks.
Local setup
Use Codex with the bundled plugin, or configure the bundled stdio MCP server in another compatible local agent. Requires uv and Python 3.11+; first setup may download dependencies. Installing SKILL.md alone does not connect your disk. No Obsidian REST API, API key, or running Obsidian app is required.
Clear boundaries
Works with .md/.markdown files up to 2 MiB. Hidden folders and symlinks are excluded. Moves do not automatically repair wikilinks. Windows has prior integration verification; macOS/Linux have not been verified on real hardware. Requested note content goes to the calling AI host; this server creates no separate cloud index.
License and price
USD 3, one-time purchase for the packaged skill. The underlying project is also available on GitHub under MIT; included open-source components retain their licenses. Agent/model charges, if any, are separate. This is an independent community project, not an official Obsidian or OpenAI product.
Markdown only (.md/.markdown), up to 2 MiB per note. Hidden paths, symlinks, and junctions are excluded. No PDF/OCR, image/Canvas editing, semantic vector search, or automatic wikilink repair. Hash checks are not cross-process transaction locks. Local MCP setup is required; ordinary hosted chat cannot directly reach the disk. macOS/Linux have no real-hardware verification claim.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 28 days ago
Requires
Permissions
File Scopes
Reads the user-selected local vault; writes require read-write permission. Existing-note changes are backed up and checked against a prior SHA-256 hash. Local config/backups: ~/.obsidian-codex/. Network is needed for initial dependency installation, not for a separate cloud vault index. Requested note content is returned to the calling AI host.