Use when the user asks to ingest a source into their Obsidian vault at <vault>, add an article/PDF/page to the wiki, process something dropped into raw/, or mentions "/obsidian-wiki:ingest". Trigger on "ingest this", "add this to my notes", "process this article", "put this in the wiki", or when a new file appears under <vault>/raw/.
Vault path:
<vault>refers to the path returned by$CLAUDE_PLUGIN_ROOT/scripts/resolve-vault.sh. Run it first to resolve the vault location.
Incorporate a new source into the Obsidian vault at <vault> by writing or
updating a wiki page, adding cross-references to related pages, and logging the activity.
The vault already has its own structure — do not restructure it. Work within the existing
six category directories and use Home.md as the navigation index.
Before ingesting anything, confirm these exist:
<vault>/ — the vault root<vault>/CLAUDE.md — schema with category rules and frontmatter template<vault>/log.md — append-only activity log<vault>/raw/ — source inboxIf any are missing, the vault has not been bootstrapped for this plugin. Point the user at the plugin README (bootstrap section) instead of creating these files yourself.
Read CLAUDE.md once per session before the first ingest. It defines the decision rules
for category placement, the frontmatter schema, and the cross-reference conventions that
this vault uses. Trust it over your own defaults.
Sources belong in raw/. If the user hands over a path outside raw/ (a download in
~/Downloads, a URL, a paste), offer to copy or save it into raw/ first and use that
as the canonical source path for citations. This matters because the summary page's
sources: frontmatter and the log entry both cite raw/<filename>, and those references
need to keep resolving later.
For URLs or clipped web content, save the rendered markdown into raw/ with a
descriptive filename (date prefix optional). For PDFs or images, keep the binary in
raw/ and reference it by filename.
The existing wiki uses six top-level directories. Pick exactly one:
| Directory | What goes here |
|---|---|
Architecture/ | System-level designs spanning multiple components |
Gotchas/ | Surprises, footguns, non-obvious failure modes you want to remember |
Patterns/ | Reusable approaches and conventions |
Platforms/ | Platform-specific notes (macOS, Linux, Android, etc.) |
Projects/ | Per-project notes (one file per project) |
Technologies/ | Per-tool / per-protocol notes (one file per technology) |
Read CLAUDE.md for the tie-breaker rules when a source could fit in more than one
category. When in doubt, ask the user — do not guess silently.
Prefer updating over creating. Before writing a new page, grep the target category for an existing page on the same topic. If one exists and the source extends it, update the existing page instead. Creating a parallel page fragments the wiki.
Write the page using the frontmatter schema from CLAUDE.md. At minimum:
---