/ingest

description: Turn material into notes at the right altitude — a quick capture, a small collection, or a full build
argument-hint: [what to ingest, or leave blank to handle Inbox/]

Handle whatever I point you at — or everything in `Inbox/` if I don't say.

**If this folder isn't a vault yet** (no `.agents/` and no notes), don't force a build — say so and offer `/obsidian-knowledge:setup` first, then come back to this.

1. **Recall.** If this vault has `.agents/learned/`, read `conventions.md` and `examples.md` and scan `.agents/learned/skills/` for a matching playbook. Look at how this vault is already organized and plan to fit in, not impose. 2. **Pick the altitude.** Match the effort to the material — a single note (**Capture**), a few notes plus a light index (**Small collection**), or the full scaffold with a concept-graph canvas (**Full build**). Default to the lightest that fits; when unsure, go lighter and offer to go deeper. See "Choose the altitude" in `.agents/ingestion-workflow.md`. (For an obvious one-note save, just use `/obsidian-knowledge:capture`.) 3. **Do the work** at that altitude, following the `obsidian-knowledge` skill and the vault's `.agents/*.md` if present (otherwise the skill's bundled `references/`). 4. **Reflect.** Append a journal entry and propose any durable convention / example / playbook updates for review. Commit per the approval policy; surface rule-change diffs before committing them.

$ARGUMENTS