--- name: video-ad-script-type-picker description: Use when you want several truly different video ad scripts from the same research. Picks script types from 14 in four groups (talk, show, story, teach) that fit how much the buyer knows and what you can prove, spreads the batch so each ad holds attention and sells a different way, and sets each script's starting and ending tone. Checks the batch against its own list before handing it back. --- # Video ad script type picker Write four scripts from one round of research with one recipe and you get one ad four times. A script type is a different shape for the same truth: a different thing for the viewer to watch, a different beat doing the selling, a different way in. Types from different groups look like different ads to viewers and to the ad platform. This skill picks types and gives each one's recipe. Pair it with a script-writing skill. The type sets the opening, beat order, person and tense, and the selling beat. The rules on facts never change. Every type uses the same nine beats (opening, problem, promise, how it works, doubt, proof, offer, guarantee, call to action), in the order taught in Blue Sense Digital's public masterclass "How To Write Meta Ads That Scale", and says where it changes that order. ## Before you start This skill runs on its own. What's below makes the result better, but none of it is required. **Works best with** (or they can paste their own instead): - **A buyer brief**, made by the [Buyer brief writer](https://useaiblocks.com/skills/buyer-brief-writer): who it's for, how much they already know, and what will move them. **Makes it better (optional):** - **Customer words** (yours): reviews, testimonials, support tickets, survey answers or call transcripts. Export them or paste them in. **Recommended steps before this one** (optional; do each once, then reuse what it makes): 1. **A buyer brief** with the [Buyer brief writer](https://useaiblocks.com/skills/buyer-brief-writer). Bring customer words. It uses your brand brain. 2. This one. How to start: 1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In Claude Code, look in the project too for these by name. 2. **If something is missing, advise, don't block.** In one short message, say this skill works on its own and will be better with a buyer brief, customer words. They can attach them, paste them, or say where they are (in Claude Code, a file path). Name the recommended steps above as a suggestion, with their links. Then ask: "Add them, or shall I go ahead with what you've given me?" If their message already says to go ahead, skip this and start. 3. **When they say go ahead,** do the whole job with what you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it. Keep the answer tight: say each point once, merge steps that give the same thing, and aim for under 700 words unless the job truly needs more. In CHECKS MISSED, name only the checks that failed, or write “none”. **Tools that do this best:** - **Any good chat AI:** Claude, ChatGPT and Gemini all follow this skill well, so use the one you already have. - **Meta Ads Manager:** Its A/B test splits one audience between your ads and changes one thing, so the result is fair. ## What you need This skill runs on its own. If something marked required below is missing, ask once, in one short message, for only the few facts you can't work without, or let them paste their own version in plain words. Then carry on with what you have, and mark each gap `MISSING:` or `[inferred]`. - **Concept** (required): the buyer, the reason they buy, the offer. - **Awareness and length** (required): how much the buyer knows (unaware of the problem, aware of it, aware of fixes, aware of you, ready to buy), and the length. - **What you can supply** (required): points from the buyer's timeline (Before, Trigger, Tries, Last doubt, After), a true cause, process facts, a real customer account, something you can film working, time points, offer terms, a real shortcoming. - **How many scripts** (optional): default 4. ## Steps 1. **Shortlist.** Skip any type whose needs aren't met; never fake a need. A need counts as met only when a supplied fact states it as that: a Try is something the facts say was tried and dropped, a Before is a habit the facts describe. Never stretch a review's side remark into a Try or a Before, and never add details the facts don't give (where things sat, how many, how long). Name the exact fact and its source next to each type. Skip types that don't suit the buyer's awareness, and types too long for the ad (stories need about 45 seconds or more; a time-lapse needs 60 or more). | Group | Type | Selling beat | Opens on | Suits buyers | Needs | |---|---|---|---|---|---| | Talk | Straight case | strongest beat | Before, said to "you" | aware of the problem or of fixes | a Before point | | | Doubt first | doubt | the Last doubt, granted | aware of fixes or of you | a Last doubt | | | Flaw first | doubt | a real shortcoming | aware of you or of fixes | a real shortcoming | | | Offer up front | offer | the terms | aware of you, or ready | terms worth leading with | | Show | Show it working | proof | the demo, mid-action | aware of fixes or of you | a result you can film | | | Day in use | proof | a moment of an ordinary day | aware of fixes or of you | when and how it's used | | | Line-up | proof | the options and the tests | aware of fixes | a real test or checkable facts | | | Making of | how it works | a decision in making it | aware of fixes or of you | a real process fact | | Story | Mirror | problem | a scene from their life | unaware of the problem | a habit from before they knew why | | | Turning point | problem | the Trigger day | unaware, or aware of the problem | a real Trigger with stakes | | | Tries in a row | how it works | the first try | aware of the problem or of fixes | two Tries | | | Someone noticed | proof | another person noticing | aware of the problem | a real customer account | | Teach | The real cause | how it works | what most people don't know | aware of the problem or of fixes | one true cause | | | Time-lapse | how it works | the first point in time | aware of the problem or of fixes | time points you can back | 2. **Spread the batch.** Take one type from each group where the needs allow. Use at least three different selling beats in a batch of four. No two scripts may open on the same timeline point or the same fact. If a group has no type that qualifies, take a second type from another group with a different selling beat, and say why. 3. **Load each type's recipe** from `references/types.md` and write the script with the paired writing skill. 4. **Set the tone.** Each script gets a starting tone (opening and problem) and an ending tone (offer and call to action). The turn happens at the promise and how it works, which stay plain and clear. | Starting tones | Ending tones | |---|---| | fed up, worried, curious, amused, matter of fact | relieved, confident, pleased, proud, matter of fact | Rules: the starting tone must match something research shows customers feel, and it only works on a true fact (worry with nothing at stake is made-up urgency). Stay with what people do about the problem, never with how bad they are (no pity, no shame, no claim the viewer has a condition). The brand's voice wins: if it rules out worry, take the nearest allowed tone and say so. Words carry the tone, not adjectives; the pictures follow it. The doubt beat is respectful; proof, offer and guarantee are steady and exact. 5. **Check it.** Run the checks in "Check before you hand it back" and fix any that fail. A need you had to stretch counts as not met: swap that type or skip it. List any check still missed under CHECKS MISSED, one line each, or write "none". ## What you hand back Hand it back in exactly this layout, with these labels in this order: ``` Batch: scripts . () | selling beat: | opens on: | tone: -> | needs met: (one row per script) Spread: , , Skipped types and why CHECKS MISSED ``` Then the scripts, if a writing skill is paired. ## After this When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own: - **Set up AI to work for you** with the [AI workflow handoff planner](https://useaiblocks.com/skills/ai-workflow-handoff-planner). It takes the plan. - **Make an offer people want** with the [Lead cost and friction planner](https://useaiblocks.com/skills/lead-cost-and-friction-planner). It takes the plan. - **Plan what to test** with the [Reach-before-repeat planner](https://useaiblocks.com/skills/reach-before-repeat-planner). It takes the plan. - **Write the ad copy** with the [Story image ad writer](https://useaiblocks.com/skills/story-image-ad-writer). It takes the plan. - **Understand your buyers** with the [Customer discovery interview planner](https://useaiblocks.com/skills/customer-discovery-plan). It takes the plan. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring. ## Check before you hand it back - Each script would be called a different ad from its neighbours. - Each type's needs are met by facts that were supplied and say exactly that, named with their source. Nothing is inferred from a side remark. - At least three selling beats and, where possible, all four groups. - No two scripts open on the same point or fact. - No example from the recipes appears in a script. ## If something is missing Write `MISSING: ` and skip the type. A "Someone noticed" or "Turning point" type without a real account turns into filming notes for a real customer, with blanks for their details. ## Avoid - Faking a process fact, shortcoming, test or customer story to fit a type. - Picking types because they sound fresh rather than because they fit.