Menu
Read, search, and create notes in the Obsidian vault/wiki memory store.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Selectively file durable, novel conversation outcomes as canonical vault notes. Use when a result will materially change future action or prevent repeated work and is not already recoverable elsewhere, or when the user explicitly asks to preserve it. Triggered by the Stop-hook decision gate or requests such as "file this", "save this conversation", and "remember this".
This skill should be used when the user asks to "organize the vault", "update indexes", "fix broken links", "rename ambiguous files", "fix filenames", "garden the vault", "sync indexes", "clean up the vault", "maintain the vault", or after making substantial structural edits (creating, moving, renaming, or deleting files) in an Obsidian vault. Also triggered by scheduled cron invocations for routine vault maintenance.
| name | obsidian-knowledge |
| description | Read, search, and create notes in the Obsidian vault/wiki memory store. |
Use the configured Obsidian vault as the durable memory/source of truth for
non-trivial context, project knowledge, and conversation outcomes. Vault roots
come from ~/.config/obsidian-knowledge/vaults.yaml; paths passed to the CLI are
relative to that root and normally begin with wiki/.
When the harness, a tool, or a repeated workaround gets in the way, record it without starting an implementation side quest:
obsidian-knowledge papercut "search hung after an automatic rebuild"
The command appends an entry to wiki/repos/<owner>/<repo>/PAPERCUTS.md when the
current directory has an identifiable Git origin; otherwise it falls back to
wiki/systems/knowledge-base/PAPERCUTS.md. The log records the working directory
and is lock-protected for concurrent agents. It records the papercut only; continue
the task unless the user asks to investigate or fix it.
Do not manually edit updated: timestamps in Obsidian notes. The vault linter manages updated metadata automatically; content edits should leave existing timestamp fields alone unless the user explicitly asks for timestamp repair.
obsidian-knowledge read "wiki/path/to/note.md"
obsidian-knowledge search "concept or phrase"
write reads literal Markdown from stdin, rejects blank content and existing
files, writes atomically, fsyncs, then reads the final path back and compares the
bytes. Treat only Wrote and verified: as success.
obsidian-knowledge write "wiki/path/to/new-note.md" <<'ENDNOTE'
# Title
Literal Markdown with `identifiers`, `$()`, and [[wikilinks]].
ENDNOTE
Read the current note, integrate the change into the complete Markdown, then replace it explicitly:
obsidian-knowledge read "wiki/path/to/existing-note.md"
obsidian-knowledge write "wiki/path/to/existing-note.md" --replace <<'ENDNOTE'
# Complete updated note
Preserved content plus the integrated durable change.
ENDNOTE
Obsidian links notes with [[Note Name]] syntax. When creating notes, use these to link related content.
If a known note cannot be read and the CLI reports Operation not permitted,
the parent process lacks Documents or Full Disk Access. Grant that process in
System Settings → Privacy & Security, restart it, and retry. Do not reinterpret
an access error as a missing note.