trend-report — Claude Code skill for YouTube trend reports
trend-report — a skill for Claude Code that finds standout videos and recurring patterns in a YouTube niche. It turns a trend request into a dated report with examples and video ideas.
MIT ★ 288 updated 2026-11-15
/plugin marketplace add TubeLabHQ/youtube-research-skills
/plugin install youtube-research@tubelabWhat trend-report does
The skill builds a dated report on videos performing well in a YouTube niche. It ranks candidates against each channel’s usual results rather than by raw views alone. The default window is the last month, and a pattern needs three successful videos from different channels.
The report includes video examples, view counts, and opening lines from transcripts when available. It examines topics, title structures, hook openings, and emotional triggers, with evidence for each finding. For a named channel, it compares videos with that channel’s usual output and suggests about six video concepts with opening lines.
TubeLab MCP is required. The skill uses it to search for videos and gather report data.
What it helps with
- find standout videos in a YouTube niche
- compare a breakout video with its channel’s usual output
- identify recurring topics and title structures
- draft video concepts from successful examples
Example prompts for the agent
- Write a trend report for the home workout niche covering the last month.
- Explain why this video outperformed the channel’s usual videos.
- Research my channel and suggest video ideas based on successful examples.
How to install trend-report
1Plugin marketplace
/plugin marketplace add TubeLabHQ/youtube-research-skills/plugin install youtube-research@tubelabThis installs the whole youtube-research plugin with all its skills
2Skills CLI (Vercel)
npx skills add TubeLabHQ/youtube-research-skills --skill trend-report -a claude-code3Manually: put the files in place
~/.claude/skills/trend-report/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/trend-report/
1Skills CLI (Vercel)
npx skills add TubeLabHQ/youtube-research-skills --skill trend-report -a codex2Manually: put the files in place
.agents/skills/trend-report/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add TubeLabHQ/youtube-research-skills --skill trend-report -a cursor2Manually: put the files in place
.cursor/skills/trend-report/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install TubeLabHQ/youtube-research-skills skills/trend-report2Manually: put the files in place
.github/skills/trend-report/SKILL.md1Skills CLI (Vercel)
npx skills add TubeLabHQ/youtube-research-skills --skill trend-report -a gemini-cli2Platform CLI
gemini skills install https://github.com/TubeLabHQ/youtube-research-skills --path skills/trend-reportManually: put the files in place
.devin/skills/trend-report/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about trend-report
How do I install trend-report in Claude Code?
Add the marketplace with /plugin marketplace add TubeLabHQ/youtube-research-skills, then install the skill with /plugin install youtube-research@tubelab.
What does trend-report do?
It finds successful videos in a YouTube niche and produces a dated report with examples, recurring patterns, and video ideas. It judges performance against each channel’s usual results, not just view counts.
What does trend-report need to run?
It requires TubeLab MCP.
Source text
SKILL.md · MIT
---
name: trend-report
description: Use when the user wants to know what works now in a YouTube niche, why a video blew up, which hooks to copy, or a trend report. Requires the TubeLab MCP.
license: MIT
metadata:
author: tubelab
version: "5.0"
requires: tubelab-mcp
---
# Trend Report
## Overview
A dated report on what is winning in a niche right now. Rank winners by ratio, because a video that beats its own channel's average says more than a big view count. A pattern needs three winners from different channels. To explain why one video blew up, compare it with its channel's normal videos.
## Workflow
1. Clarify scope only if needed. Default to the last month. If given a channel, use its own videos as the baseline for the top finding, not as winners.
2. Search for outliers. Keep at most 2 winners per channel. Two or three searches are enough.
3. Quote each top winner's opening from its transcript, word for word. If there is no transcript, give no hook. Fetch and view each winner's thumbnail, and say so if one fails to load.
4. Work out the winning patterns: the topics, the title formulas written with bracketed slots, how the hooks open, and the emotional triggers, each with what shows it.
5. If given a channel, say in one or two sentences what it should lean into and what to add, citing a winner. Then write about six video ideas, each with one line on what it does and a suggested opening line.
## Output Format
```markdown
# 📈 Trend Report: {niche or [channel](url)} · {date}
- **Top finding:** {one sentence, with numbers}
- **Sample:** {n} winners from {window}
## 🔥 Trending Videos
### 1. [{title}]({video url})
[]({video url})
- [{channel}]({url}) · {date}
- **Views:** {views} | {ratio}X Outlier
- **Hook:** `{first sentence or two, word for word}`
- **Why it worked:** *{one short line}*
## 🔍 Winning Patterns
- **Topics:** {the winning topics, in one line}
- **Titles:**
- `{formula with [SLOTS]}`
- **Hooks:** {how the hooks open, with the key moves in bold and short quoted phrases}
- **Triggers:** {trigger} ({what shows it}), {trigger} ({what shows it})
- **For your channel:** {what to lean into, citing a winner and its ratio, and what to add}
## 💡 Video Ideas Based on Research
1. **{Title}**
- {what the video does, in one line}
- Opening line: `{suggested first line}`
```
- Length: about 700 words. Five trending videos, three to five title formulas, about six ideas.
- Language: plain words and short, complete sentences. Nothing compressed.
- Bullets: one fact each, under 25 words, except quotes, verbatim titles and formulas. No extra sections or bullets.
- If it runs long, cut whole items. Never cut proof, and never squeeze sentences.
- Links: link every video, channel, moment, brand and offer you cite, built from IDs, handles and links in the data. Never guess one.
- Thumbnails: use the 320px `mqdefault.jpg` image, on its own line under the heading, linked to the video.
## Common Pitfalls
- Do not search without `publishedAtFrom` and `classificationQuality` at `"neutral"` or above, or the results fill with low-effort videos.
- Do not promise the user a small channel's multiple. It proves a format, not an expected result.
- Do not count videos for another audience or language, the user's sister channels, or paid placements (huge views, almost no likes) as winners. The language tag can call a Hindi or Urdu video English, so check the title and thumbnail.
- Do not copy a winner's title. Keep what made it work and change the topic.
© tubelab · MIT · TubeLabHQ/youtube-research-skills