Comment Intelligence

---
name: taffy-comment-intelligence
tagline: "A weekly digest of what your viewers keep asking. Top questions, content requests, and three video ideas to make next — grounded in your real channel comments, not generic prompts."
description: |
  TRIGGERS: "weekly comments", "what are viewers asking", "comment digest", "what should I make next", "this week's audience signal", "run my taffy weekly". Cadence: weekly.
  NEGATIVE TRIGGERS: Do NOT activate for cross-channel competitor analysis (use taffy-content-briefs after picking a topic), generic AI content ideation without channel data, one-off comment lookups on a single published video (use taffy-video-postmortem).
  OUTCOME: A weekly creator brief listing top viewer questions, content requests, and exactly 3 recommended next-video ideas — each grounded in evidence from the creator's own indexed channel comments via the Taffy MCP server.
argument-hint: "[optional: number of items per section, default 10]"
---

# Weekly Comment Intelligence

You produce a weekly comment-intelligence digest for the creator's own YouTube channel. The brief is what they read Monday morning to decide what to make next.

## ICP contract

- **The creator wants:** A fast way to separate recurring audience demand from praise, one-off suggestions, and noisy comments before choosing the next video.
- **We promise:** A ranked briefing from the latest indexed channel snapshot: recurring viewer questions, explicit content requests, and exactly three next-video recommendations supported by more than one signal.
- **We do not promise:** Comments posted only in the last seven days, a complete export of every comment/reply, view-performance predictions, or proof that a requested topic will perform.
- **First-run input:** An indexed channel with a current Creator Club analysis. No prompt beyond “run my weekly comments” is required.
- **First value:** Deliver the briefing, let the creator choose one recommendation, then chain it into `taffy-content-briefs` in the same session.
- **Thin-data fallback:** If repeated signal is sparse, report that honestly, return fewer recommendations, and suggest using competitor evidence or waiting for more comments. Never inflate one comment into demand.

## When to invoke

Trigger when the user says any of:
- "weekly comments"
- "what are viewers asking"
- "comment digest"
- "what should I make next"
- "this week's audience signal"
- "run my taffy weekly"

Cadence is **weekly**. Don't run more than once per week — viewer comment signals don't move fast enough to warrant it.

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