script-breakdown — Claude Code skill: video structure
The script-breakdown Claude Code skill maps the structure of YouTube videos and helps outline scripts. It responds to requests to inspect a hook, a beat sheet, or videos from a channel or niche.
MIT ★ 288 updated 2026-11-15
/plugin marketplace add TubeLabHQ/youtube-research-skills
/plugin install youtube-research@tubelabWhat script-breakdown does
The skill labels transcript beats in sequence, from the opening hook through promises, stakes, open loops, proof, re-hooks, payoffs, and calls to action. It turns those labels into a reusable layout. The opening hook is quoted exactly.
It can cover one to three videos. When given a channel or niche, it selects videos to examine; layouts based on shared elements require multiple videos. A script skeleton is included only when a topic is supplied. The skill requires TubeLab MCP.
What it helps with
- map the structure of a YouTube video
- compare the beats used across a channel's videos
- identify how a niche's top videos hold attention
- turn a video layout into a script outline
Example prompts for the agent
- Break down this YouTube video's hook and structure from its transcript.
- Compare the beat layouts of top videos in this niche.
- Draft a script skeleton about launching a product using these videos' shared structure.
How to install script-breakdown
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 script-breakdown -a claude-code3Manually: put the files in place
~/.claude/skills/script-breakdown/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/script-breakdown/
1Skills CLI (Vercel)
npx skills add TubeLabHQ/youtube-research-skills --skill script-breakdown -a codex2Manually: put the files in place
.agents/skills/script-breakdown/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add TubeLabHQ/youtube-research-skills --skill script-breakdown -a cursor2Manually: put the files in place
.cursor/skills/script-breakdown/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install TubeLabHQ/youtube-research-skills skills/script-breakdown2Manually: put the files in place
.github/skills/script-breakdown/SKILL.md1Skills CLI (Vercel)
npx skills add TubeLabHQ/youtube-research-skills --skill script-breakdown -a gemini-cli2Platform CLI
gemini skills install https://github.com/TubeLabHQ/youtube-research-skills --path skills/script-breakdownManually: put the files in place
.devin/skills/script-breakdown/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 script-breakdown
How do I install script-breakdown in Claude Code?
Run /plugin marketplace add TubeLabHQ/youtube-research-skills, then run /plugin install youtube-research@tubelab.
What does script-breakdown do?
It labels a video's transcript beats and arranges them into a reusable layout. With a supplied topic, it can also draft a script skeleton based on that layout.
What does script-breakdown need to work?
It requires TubeLab MCP.
Source text
SKILL.md · MIT
---
name: script-breakdown
description: Use when the user wants to break down a YouTube video's hook, structure or beat sheet, see how the top videos in a niche or channel are built, or outline a new script. Requires the TubeLab MCP.
license: MIT
metadata:
author: tubelab
version: "5.0"
requires: tubelab-mcp
---
# Script Breakdown
## Overview
How a video holds attention, mapped from its transcript into a structure the user can reuse. Strong videos cycle through promise, stakes, re-hooks and small payoffs before the final payoff. Showing where each one lands is the point. The hook is the exact first 30 seconds, quoted. Transcripts are free to read.
## Workflow
1. Clarify scope only if needed. Read 1 to 3 videos. If the user names a channel or a niche instead, pick the videos yourself. For a channel, take its best videos of the last three months by ratio, which is a free read. For a niche, take the top outliers from one search. Say which you picked and why.
2. Tag every beat in order with one type: hook, promise, stakes, open loop, proof, re-hook, mini-payoff, payoff, or call to action. Types repeat, and a long video has 10 to 20 beats.
3. Turn the beats into a layout someone could reuse. With several videos, keep only the parts they share.
## Output Format
```markdown
# 🎬 Script Breakdown: {video, channel or niche}
- **Main finding:** {one sentence}
- **Videos picked:** {only if you chose them: which, and why in one sentence}
## [{title}]({video url}) · [{channel}]({url}) · {views, ratio, length}
- **Hook (0:00 to 0:30):** "{word for word}"
- **What it does:** {one sentence}
| Time | Beat | What happens |
|---|---|---|
| [{m:ss}]({link to that moment}) | {type} | {a few words or a short quote} |
## 🗺️ Layout
Hook 0:00 → Promise {m:ss} → ... → Call to action {m:ss}
## 📝 Script Skeleton
{Only if the user gave a topic. Build it on the layout.}
```
- Length: about 700 words per video.
- Language: plain words and short, complete sentences. Nothing compressed.
- Bullets: one fact each, under 25 words, except quotes and verbatim titles. No extra sections or bullets.
- If it runs long, cut whole rows. Never cut the hook, 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.
- Quotes: the hook and short lines only. Never paste the full transcript.
## Common Pitfalls
- Do not search without `publishedAtFrom` and `classificationQuality` at `"neutral"` or above, or the results fill with low-effort videos.
- Do not pick videos by raw views. A high ratio shows the structure worked for that channel, not just that the channel is big.
- Do not paraphrase the hook. The exact words are the finding.
- Do not name a beat by its topic. Name what it does to keep the viewer watching.
- Do not stop at the first payoff. Late re-hooks are what hold a long video.
- Do not call a layout a pattern from one video.
- Do not trust numbers in captions. Check them against the description, and mark unclear words [unclear].
© tubelab · MIT · TubeLabHQ/youtube-research-skills