Skill

obsidian-vault-crud

Safe Create/Read/Update/Delete operations for Obsidian Vault notes. Implements atomic writes, advisory locking, concurrent edit detection, and lossless YAML frontmatter handling. Use when reading, writing, updating, or appending to any vault note.

From obsidian-integration

Install

Run in your terminal

npx claudepluginhub richfrem/agent-plugins-skills --plugin obsidian-integration

Tool Access

This skill is limited to using the following tools:

BashReadWrite

Supporting Assets

View in Repository

acceptance-criteria.md

assets/resources/architecture-background.md

assets/resources/kepano-analysis-summary.md

assets/resources/safety-learnings.md

evals/evals.json

evals/results.tsv

fallback-tree.md

obsidian-parser/parser.py

references/acceptance-criteria.md

references/fallback-tree.md

requirements.txt

scripts/vault_ops.py

Skill Content

Similar Skills

executing-plans

Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.

superpowers

134.2k

brainstorming

7 files

Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.

superpowers

134.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

134.2k

Stats

Parent Repo Stars1

Parent Repo Forks1

Last CommitMar 21, 2026

Actions

View Source View Plugin View on GitHub View README

Dependencies

This skill requires Python 3.8+ and standard library only. No external packages needed.

To install this skill's dependencies:

pip-compile ./requirements.in
pip install -r ./requirements.txt

See ./requirements.txt for the dependency lockfile (currently empty — standard library only).

Obsidian Vault CRUD

Status: Active Author: Richard Fremmerlid Domain: Obsidian Integration Depends On: obsidian-markdown-mastery (WP05)

Core Mandate

This skill provides the disk I/O layer for all agent interactions with the Obsidian Vault. It does NOT handle syntax parsing (that belongs to obsidian-markdown-mastery). Instead, it ensures that every file write is:

Atomic — via POSIX os.rename() from a .tmp staging file
Locked — via an advisory .agent-lock file at the vault root
Conflict-aware — via mtime comparison before/after read
Lossless — via ruamel.yaml for frontmatter (never PyYAML)

Available Commands

Read a Note

python ./vault_ops.py read --file <path>

Create a Note

python ./vault_ops.py create --file <path> --content <text> [--frontmatter key=value ...]

Update a Note

python ./vault_ops.py update --file <path> --content <text>

Append to a Note

python ./vault_ops.py append --file <path> --content <text>

Safety Guarantees

Atomic Write Protocol

Write content to <target>.agent-tmp
Verify the .agent-tmp file was written completely
os.rename('<target>.agent-tmp', '<target>') — atomic on POSIX
If any step fails, the .agent-tmp is cleaned up

Advisory Lock Protocol

Before any write batch: create <vault_root>/.agent-lock
After write batch completes: remove .agent-lock
Other agents check for .agent-lock before writing
This is advisory (does not block Obsidian UI)

Concurrent Edit Detection

Capture os.stat(file).st_mtime before reading
Before writing, check st_mtime again
If mtime changed → another process edited the file → ABORT

Frontmatter Handling

Uses ruamel.yaml (NOT PyYAML) to preserve comments, indentation, and array styles
Ensures Dataview and Obsidian Properties remain intact