---
name: vault-ingestion
description: File raw content the owner pastes or uploads in chat into the Obsidian vault, following AGENTS.md conventions. Use when the owner pastes text, drops a document/PDF/spreadsheet/transcript/email export, or shares a batch of material and wants it organized and filed into the vault — single item or bulk. Produces a routing manifest for approval, then applies it and commits in one commit. Not for answering questions about existing vault content, and not for the spoken daily debrief (that has its own workflow in AGENTS.md).
served: true
---

# Vault Ingestion

This skill is a thin trigger. The **canonical procedure lives in the vault's `AGENTS.md`** — the **"Vault ingestion workflow"** section, with routing in **"Ingesting and filing content."** Those sections are the single source of truth; this file deliberately does not restate them, so nothing drifts.

When this skill fires:

1. **Read the current `AGENTS.md`** — the "Vault ingestion workflow" and "Ingesting and filing content" sections — plus `Agent/Working Style.md` for the owner's output preferences. They win over anything remembered here.
2. **Pick the transport** per AGENTS "Transports: reaching the vault" — **check first whether you already hold the `vault-mcp` brain tools** (the default when connected to a running vault); if so, that's your transport, and its `ingest_content` + `apply_ingest` tools *are* this workflow — they run the manifest pass and commit server-side, so don't shell out to git. Otherwise probe for the desktop-local servers (**Obsidian Semantic** `obsidian-vault` for markdown notes, **filesystem MCP** `vault-filesystem` for binaries), with the **GitHub connector** as fallback. Say so if you fall back.
3. **Follow the workflow:** triage the input into a manifest (decompose into pieces; route each by what it is across the PEAK pillars — **People / Events / Areas / Knowledge** — plus the area TODOs and Open Items) → shape each piece into native form (frontmatter per schema, short-form wikilinks, binaries to the area's `Files/`) → reconcile against the live vault on approval (merge rather than duplicate, refresh folder notes/indexes, link every new note) → review and commit once (`ingest: <YYYY-MM-DD> <label> (N notes, M updates)` when you author the commit; on the brain MCP `apply_ingest` makes the single commit for you).

Key rules (all detailed in AGENTS.md): **don't stage what you can file** — route straight from the chat into structured homes (the inbox is for imports and deliberate captures, and it must be drained); **manifest before apply** — the owner approves the plan as a draft, nothing touches the vault until then; **one run, one reversible commit**. Run the **fan-out check** ("what else does this input touch?") before finalizing the manifest.
