--- name: YouTube link triage and branch description: >- Use when the user pastes a YouTube (or similar video) URL and wants more than a raw download: factual triage, then a operator choice between a short reference note or a gated risk/approval brief. --- # YouTube link triage and branch Extends `video-dl`. Do **not** re-implement yt-dlp here. Do not connect payments, publish, or send external messages from this skill. ## Steps 1. Confirm the URL and intent (reference / evaluate / monetise-adjacent). If intent is unclear, ask once with a short choice widget. 2. Run `video-dl` (`get` for the URL). Record local path, size, and media line. On failure, report the error and stop. 3. Produce a **facts-only** summary (5–8 bullets): what the video is, who/what it promotes, claims made on-screen or in description. Do not invent revenue, subscriber, or product claims. 4. End the summary with one **Therefore** sentence (recommended next move). 5. Ask the user to choose: **Reference note** | **Risk & approval brief** | **Stop**. ### Branch A — Reference note 6a. Write a short Working Draft (title, date, source URL, path/size, 5–8 facts, Therefore). Upload unconverted to the user’s Working Drafts Drive folder when standing rules require uploads. Deliver the path and Drive link. ### Branch B — Risk & approval brief 6b. Write a one-page Working Draft with: Executive summary; risks table (claim / evidence grade / risk / mitigation); operator approval checklist; recommended **gated** next step; status line `Working Draft — not authorised alone`. Upload unconverted when required. Do not execute gated steps (accounts, payments, publish) without explicit approval of the exact action. ### Branch C — Stop 6c. Keep the download only if already saved; report path. No further pack. ## Guardrails - Facts vs assumptions vs gaps must be labelled. - Never collapse “downloaded” into “reviewed and approved”. - Prefer Architect / Project Manager register for the packs.