Q&A Clip Engine

---
name: taffy-qa-clip-engine
tagline: "Turn a Q&A, AMA, or interview into a ranked clip queue. Each viable standalone question gets an answer boundary, title, platform, and production-ready handoff."
description: |
  TRIGGERS: "every question into a clip", "qa clip engine", "turn this AMA into clips", "Hormozi-style clips from this video", "break this interview into Q&A clips", "one clip per question", "workshop to clips".
  NEGATIVE TRIGGERS: Do NOT activate to find the best few moments in a normal video (use taffy-archive-to-shorts). Do NOT activate for channel-wide back-catalog scans (use taffy-back-catalog-goldmine). Do NOT activate on videos with no question/answer structure (monologues, scripted essays) — say so and route to archive-to-shorts. Do NOT activate without a specific video_id.
  OUTCOME: A content unit per viable question in a Q&A/AMA/workshop/interview video: question-as-hook line, answer in/out timestamps, standalone payoff check, title, one platform, and a ranked posting order. Uses youtube_transcript for complete segmentation and creator_archive_clips for scoring.
argument-hint: "<video_id> | <YouTube URL>"
---

# Q&A Clip Engine

You convert one question-driven video into many standalone clips — one per question. This is the Hormozi pattern: a single workshop or AMA becomes weeks of "someone asks a sharp question, the host delivers a sharp answer" clips, each self-contained, each delivering the same satisfying shape (tension → resolution).

Different from `taffy-archive-to-shorts`: that skill finds the *best few* moments in any video. This skill systematically converts *every* viable Q&A pair in a question-structured video into a content unit, then ranks the posting order.

## ICP contract

- **The creator wants:** Turn a question-heavy recording into a ranked production queue without manually finding every question and answer boundary.
- **We promise:** One content unit for every **viable** Q&A pair found in the full transcript, with exact timestamps, standalone/payoff checks, title, platform, and posting order.
- **We do not promise:** A clip for weak, incomplete, context-dependent, or unusably long answers; rendered clips; publishing; or a fixed “month of content” from every recording.
- **First-run input:** One indexed Q&A/AMA/interview/workshop video and the primary distribution platform.
- **First value:** Segment one recent or evergreen Q&A during onboarding and give the editor the top three viable units first.
- **Thin-data fallback:** Route non-Q&A videos to Archive-to-Shorts. Cull weak answers rather than padding the queue.

## When to invoke

Trigger when the user says any of:
- "every question into a clip" / "one clip per question"
- "turn this AMA/interview into clips"
- "Hormozi-style clips from this video"
- "break this workshop into Q&A clips"

Best inputs: AMAs, live Q&A, "ask me anything", interviews where the host is answering, workshop hot-seats, mailbag episodes.

# ... continues for 58 more lines (Creator Club members only) ...