Skip to main content
/ingest takes raw knowledge inputs — book notes, highlights, exported files — from your vault’s knowledge/raw/ folder and converts them into clean, structured notes using a consistent template. It handles books, articles, podcasts, and courses.

Usage

When run without an argument, /ingest scans {vault}/knowledge/raw/ for any file that doesn’t have processed: true in its frontmatter, processes each one, then marks it as processed and reports a summary.

What It Produces

Every book is converted into a structured note using the Book Note Template:

Output Location

The structured note is saved to:
After creating the note, /ingest also updates {vault}/knowledge/books/_index.md with the new book entry and creates wiki-links to related files already in your vault.

Supported Source Types

Saved to {vault}/knowledge/books/[book-slug].md. Ingestion extracts metadata, key concepts, frameworks, actionable insights, and up to 3–5 memorable quotes (max 15 words each).
Saved to {vault}/knowledge/articles/. Same extraction process, adapted for article-length content.
Saved to {vault}/knowledge/podcasts/. Key ideas, guest frameworks, and timestamps are extracted where available.
Saved to {vault}/knowledge/courses/. Module-level concepts and exercises are captured in structured format.

Auto-Chain After Ingestion

After successfully processing a file, /ingest automatically triggers the next steps in the pipeline:
  1. /audit runs on the ingested book to independently verify the knowledge
  2. If audit passes, /absorb runs to connect insights to your vault
  3. All 3 notification channels are updated (Obsidian task, daily note, audit flag)
Use /chain to run the full pipeline from epub to vault sync in one command — no need to trigger each step manually.