Skip to content

gooseworks-ai/goose-skills / skills/video/write-video-ad-script

write-video-ad-script

Verified

Write or revise a short-form ad from a sourced angle and reference. Plan connected words, product proof and sound; expose production gaps before script review.

references/hook-families.md

View on GitHub
# Hook families

**Summary.** The hook is the first second: the picture, the spoken line and the on-screen
words, together. Pick the angle by what the viewer already knows, pick one family below,
and make all three channels say the same thing. Give every concept 3 or 4 hooks from
different families. Write from the buyer's words and the product's facts; this file has
no example lines to copy.

## Pick the angle type by awareness

| The viewer… | Stage | angle_type |
|---|---|---|
| doesn't know they need it | Unaware | story, curiosity, identity, desire |
| feels the problem | Problem-aware | problem_fix |
| knows the kind of solution | Solution-aware | demo, how_it_works, old_vs_new (never a named rival) |
| knows the product | Product-aware, most aware | proof, offer, objection |
| hears something new | Any | news |

Food, fashion and lifestyle often win on desire or sensory detail, with no problem at all.

## Families

T1-T5 is the recognition tier (next section). On-screen words in beat 1: 8 or fewer.

| Family | Stage | Picture (frame 1) | Spoken | On-screen | Avoid |
|---|---|---|---|---|---|
| Relatable moment (T1) | Unaware, problem | The viewer's own habit, mid-action | Names that habit in buyer words | The habit | A mood shot with no action |
| Call-out (T2) | Problem | The situation the line names | Names the viewer's exact situation | Who it's for | Broad labels; a hypothetical "If you…" |
| Number or stake (T3) | Solution, product | The thing being counted | One sourced number | The number | Any number no fact or quote backs |
| Confession | Unaware, problem | Speaker caught in the admission | Admits something slightly embarrassing | The admission | Invented history or results |
| Cold open / mid-action | Unaware | The event already moving | Starts mid-sentence, no setup | Where or when | Setup before anything happens |
| Result first | Problem, product | The after state, before the setup | The outcome, then rewind | The after | A result nothing backs |
| Demo first | Solution | The product doing the thing | Points at it | What to watch for | Talk before the proof is visible |
| Visual-only | Any | A pattern break that needs no words | None, or one word late | Optional, 4 words | A pretty shot that says nothing |
| Named enemy | Problem, solution | The usual option failing | The category's one shared complaint | The complaint | Naming a rival brand |
| Contrarian / stop | Solution | What the viewer usually does | The opposite of category wisdom | The habit to stop | No real reason behind it |
| Mistake / warning | Problem, solution | The mistake happening | "Don't do what I did", protective | The mistake | Fear, shame, scare numbers |
| Old vs new | Solution | Old way and this way side by side | Compares the two fairly | Old / new labels | A rival's name; a rigged test |
| Overheard / social | Product | Someone else reacting | Another person's reaction does the work | The reaction | Invented testimonials |
| Secret / insider | Unaware | The hidden detail, half shown | Lets the viewer in | A tease, not the answer | A "secret" everyone knows |
| Specific question | Problem | The thing the question is about | A question only this viewer asks, answered within 5 s | The question | "Have you ever…" (T5) |
| Reveal delay | Any | The setup, answer hidden | Promises what the end shows | The promise | An end that never pays it off |
| List or time-box | Solution | Item one already in view | A short list or a short time | The count | Padded items |
| Bold claim | Product | The proof of the claim | One claim the body earns | The claim | Anything the facts don't back |
| Direct ask | Most aware | An action the viewer can copy | A tiny thing to do along | The ask | An ask that is really the CTA |
| Founder origin (T4) | Product | Founder with the original problem | Why it was made | The problem | Direct-response objectives |

## Recognition ladder

1. **T1.** The viewer sees themselves doing the thing.
2. **T2.** The line names who it is for, so the right viewer stays.
3. **T3.** A concrete, sourced number or stake.
4. **T4.** Founder origin: slow to recognise. Fine for brand campaigns, weak for direct response.
5. **T5.** A generic question or statement: scroll-past. Rewrite it.

Prefer T1-T3. A T4 hook on a direct-response ad, or any T5 hook, is a weak hook.

## Hook rules

- Beat 1's picture, spoken line and on-screen words say the same thing. It works muted.
- Spoken hook: 12 words or fewer. Beat 1 on-screen: 8 or fewer; later beats: 13 or fewer.
- One device per hook: a call-out, a number or a question, not a stack.
- **"If you…"** only when the same line names a concrete moment. Never a hypothetical.
- Line 1 opens a question the last third answers. Add one turn near the middle: a reveal,
  a surprise or a "but". Each line earns the next; cut any line a viewer could leave after.
- The body shows one demo or one true proof. At most two features, each pushed through
  "so what?" until it reaches what it does for the viewer.
- Where the recipe allows, show the product in beat 1 and name it by beat 2. No brand name
  as the first words unless the format is built on the brand mark.
- Use the buyer's nouns, exaggerations and numbers. No invented proof, quotes, scarcity,
  fear or competitor names.
- Different families across one concept's hooks, and across the concepts' top hooks.

## Dead openers (the rule check flags these)

"Introducing…", "Meet…", a greeting, "In a world where…", "Imagine…", "Picture this…",
"Say goodbye to…", "Are you tired of…", "Tired of A, B and C", "Have you ever…", "Did you
know…", "Struggling with…?", "Looking for…?", "What if I told you…", "Stop scrolling".
Each one delays the point or reads as an ad in the first second.

## Dead ideas

A founder over generic b-roll; a captioned screen recording as the whole idea; a lazy
before/after split; a slow-motion pour; waking refreshed by a window; a vague testimonial
over product shots; a family laughing around the product; a logo reveal as the payoff.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall