I used to rewatch a winning video five times trying to feel why it worked. Now I read it. Paste a link, get the transcript, the beats, and the frameworks, in three minutes.
I used to rewatch a winning video five times, trying to feel out why it worked. A transcript with the beats marked tells you more in three minutes than an hour of rewatching ever did.
This is the study tool built into my own dashboard. Paste a link, get the full transcript, the hook mechanics named, every beat with a timestamp and its job, and the frameworks the creator is using, whether they know it or not.
One rule makes it useful. The moves are shared property. The sentences aren't. It shows you exactly what to steal and what to leave alone.
Rewatch the video with a notepad, pause every ten seconds, try to write down the structure. You'll quit at minute four.
Paste the link, get the transcript and the full breakdown, save the template. Three minutes per video.
Every outlier your watchlist catches gets broken down automatically, and the templates feed your blueprint library. Study happens while you sleep.
It pulls the transcript and metadata, names the hook mechanics in the first minute, maps every beat with its retention job, identifies the real frameworks present, writes a words-free template, and tells you what to steal and what to leave.
--- name: video-breakdown description: Paste a link to any video and get the full transcript plus a breakdown of its hook mechanics, beat-by-beat structure, the named frameworks it uses, and a reusable template you can write your own video into. Trigger on "break down this video", "why did this video work", "study this video", "what's the structure of this". --- # Video Breakdown The fastest way to learn structure is to read a winner with the sound off — as words, as beats, as mechanics. This skill turns any video link into a study you can build from. ## Before you start Get the full transcript through a connected tool (YouTube transcript connector, a research API like ScrapeCreators via a connector hub, or the free repo at github.com/drleadflow/thumbnail-system-starter which has this built in). Manual fallback: paste the transcript. Never analyze from the title alone or from memory of the video. Pull the title, channel, and view count too. Context matters: a 2M-view video from a 10M-sub channel and one from a 20K-sub channel are different lessons. ## Step 1: The hook (first 60 seconds) Quote the opening lines briefly, then name the mechanics at work — curiosity gap, receipt, contrarian claim, callout, visual proof, open loop — and explain in one line each why it holds attention. Note exactly when the video first promises the payoff and when it first withholds it. ## Step 2: The beats Walk the whole video and mark each beat with a timestamp, a name, and its retention job: hook, context, proof, open loop, pivot, re-hook, payoff, close. Note transitions — how the video moves from one beat to the next without losing people. Usually 6–12 beats. ## Step 3: The frameworks Name every recognizable framework: Problem-Agitate-Solve, Open Loop + Delayed Payoff, Proof Before Promise, Rate of Revelation, Before/After/Bridge, the Rule of Three, whatever is genuinely present. For each: where it appears, how it's executed here. Don't force frameworks that aren't there — an honest "this is a straight tutorial" is a finding. ## Step 4: The template Rewrite the structure as a reusable skeleton: each beat as a name + instruction + `[placeholder for the creator's own material]`. Structure only — zero words, facts, or claims from the source. Someone should be able to write a completely different video into it. ## Step 5: What to steal, what to leave Three sentences: the mechanic worth stealing, the thing that's specific to this creator (don't copy), and the one move most people would miss. ## Rules - Mechanics are shared property. Sentences aren't. Quote only what's needed to show a mechanic, and keep quotes short. - If the transcript is missing or partial, say so and analyze only what's real.
Inside the AI CEO Lab I teach how to wire study, blueprints, and scripts into one agent-run pipeline. Or we build it for you.
One email a week. What changed, why it matters, what to do about it. Skip it and find out the hard way.