mcpField
S
script-breakdown

script-breakdown

github.com/tubelabhqOther4713 installsUpdated today
Repository

About script-breakdown

script-breakdown is a skill that maps how a video's transcript holds attention into a reusable structure. It examines one to three videos and labels beats such as hooks, stakes, re-hooks, and payoffs in order.

Key features

  1. 01Analyzes one to three videos
  2. 02Quotes the exact opening 30 seconds
  3. 03Labels narrative beats in sequence
  4. 04Builds reusable layouts from shared beats

Use cases

  1. 01Study how a video sustains viewer attention
  2. 02Turn a transcript into a reusable outline
  3. 03Compare structures across several videos

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tubelabhq/youtube-research-skills --skill script-breakdown

After installing, type/script-breakdownin Claude Code to confirm it loaded.

Details

From the project README

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

# 🎬 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].

Comments

Markdown supported