watch-videolisted

# Watch a video — comprehension, not ingestion Someone shares a video and asks you about it. Two hooks make that possible, and **neither is discoverable on its own** — hooks have no semantic match, so a session asked to "watch this" finds nothing and improvises. That gap is the whole reason this skill exists. ## The boundary — read this first > **This skill WATCHES. It does not FILE.** Its output is *understanding held in the session*, not a vault artifact. No note, no frontmatter, no cross-links, no `_index` update, no action-item routing. Working files go to a scratch path (`/tmp`), never to `vault/`. > > **`/aios:ingest` is the filing pipeline** — it exists precisely so that turning a source into a permanent, wired-up vault note is a deliberate act with conventions. If the operator wants that, **hand off** (*"want me to `/aios:ingest` this so it lands in `reflections/ingests/` with the cross-links?"*) — do not half-implement it here. Two paths, one boundary, no overlap. So the shape of a run is: **get it into context → do what was asked → offer, don't assume.** If the ask was open-ended (*"watch this"* with no question), watch it, then say what it is in two or three lines and ask what they want from it. Don't manufacture a deliverable nobody requested. ## Which tool — the actual decision | The source | Reach for | Why | |---|---|---| | Document (PDF, docx, deck, sheet) | MarkItDown or the `document-skills` | Not this skill's job; those already match semantically | |