clip-threadlisted

# /clip-thread — Capture Chat/Email Thread to Intake > **RETIRED 2026-06-21 (v2.33.0).** Folded into `/intake`: clip-thread → `/intake thread <id>` (or auto-detected from a chat/email URL). Kept for reference only — not a live skill (archived under `skills/.archived/`, excluded from discovery). Save a chat thread or email conversation to `intake/clippings/{YYYY-MM-DD}-{slug}.md` for review and promotion. Unlike `/clip` (URL/snippet) or `/intake` (bulk/doc-anchored), `/clip-thread` is shaped specifically for *threaded* conversations — Slack threads, Teams channel discussions, Gmail conversation chains, MS365 email threads. ## Step 0: Resolve Config Read `~/.gemini/antigravity/aria-knowledge.local.md` and extract `knowledge_folder`. If the file doesn't exist, stop: "aria-knowledge is not configured. Run /setup to get started." Verify `{knowledge_folder}/intake/clippings/` exists. If not, stop: "Clippings directory not found. Run /setup to repair the knowledge folder structure." ## Step 1: Probe Connected MCPs Check Claude's available tool list for `~~chat` and `~~email` MCPs. The skill needs at least ONE of these connected to proceed. - **`~~chat`** (slack, ms365): if connected, available for Slack threads or Teams channel messages. - **`~~email`** (gmail, ms365): if connected, available for Gmail or MS365 email threads. If NEITHER category has a connected MCP, output the standard fallback notice and stop: > No required MCPs connected for `/clip-thread`. Connect one o