From obsidian-wiki
Use when the user asks to ingest a source into their Obsidian vault at ~/dev/knowledge, add an article/PDF/page to the wiki, process something dropped into raw/, or mentions "/vault-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 ~/dev/knowledge/raw/.
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-wiki:vault-ingestThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Incorporate a new source into the Obsidian vault at `~/dev/knowledge` by writing or
Incorporate a new source into the Obsidian vault at ~/dev/knowledge 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:
~/dev/knowledge/ — the vault root~/dev/knowledge/CLAUDE.md — schema with category rules and frontmatter template~/dev/knowledge/log.md — append-only activity log~/dev/knowledge/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:
---
title: <Page Title>
aliases: []
tags: [<topic>, <subtopic>]
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
sources: [raw/<filename>]
related: [[Other Page]]
---
Body structure (short, readable, grep-friendly):
raw/.Do not paraphrase the entire source. The wiki is summary + cross-ref, not a mirror.
After writing the summary page, scan the rest of the vault for entities the source mentions. Use grep over the category directories for exact entity names (tool names, protocol names, project names, platform names).
For each hit:
[[Page Name]] link format (Obsidian wikilinks).If the source contradicts an existing page, do not silently overwrite. Surface the contradiction: add a "Conflicts with" note to the new page, and ask the user how to reconcile. See the "Contradictions" section below.
Home.md is the vault's Map-of-Content index. It contains tables organized by
category. If you created a brand-new page in a category that has a table in Home.md,
add one row for the new page.
Rules:
Home.md, do not invent one — just skip the
index update and note it in the report.Append a new entry to ~/dev/knowledge/log.md. Newest at the bottom, never edit past
entries. Format:
## [YYYY-MM-DD] ingest | <source title>
- Created: [[New Page]]
- Updated: [[Page A]], [[Page B]]
- Cross-refs: [[Page C]]
- Source: raw/<filename>
Use today's date. Omit the lines that don't apply (e.g. no "Created" line if you only updated existing pages).
After all edits, print a compact summary:
Home.md was touchedKeep this short — the user will review the diffs in Obsidian.
If the source disagrees with something already in the vault:
## Conflicts section that quotes both claims and cites both
pages.Silent overwrites destroy wiki history. The user relies on the vault being append-mostly, and needs to see conflicts explicitly.
Home.md beyond adding a row. The index is hand-curated and fragile.CLAUDE.md first. The schema has decisions baked in
that are not obvious from the folder names alone.npx claudepluginhub sureserverman/obsidian-wiki-plugin --plugin obsidian-wikiGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.