ingest

# /ingest — Raw human input → structured work You are a relay hub: clients text you, partners email you, calls get transcribed. Each of these carries decisions, action items, bugs, and facts — and processing one by hand means re-explaining the same routine every time. This skill is that routine, written down. **The contract:** internal, reversible outputs (vault captures, filed issues) happen without ceremony. Outward-facing outputs (replies) are always **drafted, never sent**. ## Files | Path | What | |---|---| | `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/ingest/people.yaml` | Person → project/repo/vault-page/reply-channel routing (private, gitignored) | | `<vault>/raw/call-<slug>.md` / `<vault>/raw/message-<slug>.md` | Captures, in second-brain's schema | | `references/people.yaml.example` | Config schema with a worked example | `<vault>` is `${SECOND_BRAIN_VAULT:-$HOME/Documents/SecondBrain}`. ## Step 0 — Get the input and classify it In order: content in the prompt → clipboard (`pbpaste`) → ask. Classify by shape, not by what the user called it: | Shape | Type | |---|---| | Speaker labels + timestamps, or a Grain/Zoom/Granola/Fathom URL or header | **call** | | "from X:" / forwarded text or DM, first-person, short | **message** | | Email headers or greeting/sign-off structure | **email** (treat as message with formal tone) | | Unstructured first-person stream ("okay so I was thinking…") | **voice-note** (no reply draft; capture + actions only) | Long tran...