gooseworks-ai/goose-skills / skills/video/write-video-ad-script
write-video-ad-script
VerifiedWrite 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/buyer-and-mechanism.md
View on GitHub# Buyer perspective and the product's role
**Summary.** Human speech can still leave a buyer asking “what does this do for me?”
Build the message from a specific consumer's situation, then explain the supported
connection between the product and that situation. Preserve natural conversation;
do not turn the explanation into a feature list or a product quiz.
## Establish the buyer's case
Use the current audience decision and relevant evidence from
the `ad-angle-miner` skill. A historical brand profile may describe a broader audience
than today's campaign. Record which audience this script serves; do not silently
overwrite historical research. Write a short case containing:
- The person's role and the task or decision they face now.
- The inputs or possessions they already have, and what they currently do with them.
- The constraint that makes that approach inadequate, and the output they need.
- Why that difference matters to them in this situation.
For a work product, retain the actual object of the work: which product, assets,
brief, variation, claim or handoff. “Need more content” is not a buyer case. For a
consumer product, retain the actual routine or decision rather than inventing an
extraordinary anxiety. Pain is optional; discovery, desire and a practical question
can provide the case. Use only details that clarify this buyer's choice.
Source questions with their replies and context. Check role, category and task fit.
A large agency's process may supply vocabulary without representing a small brand's
budget or decision. Written social posts have unverified authorship and are not
spoken references, product proof or a license to invent a customer testimonial.
## Explain the connection in the ad
Privately map the supported path from the buyer's action or input, through what the
offering does, to what they receive and why it helps here. Then put the useful part
of that explanation into the **actual words or feasible visible actions**. Private
briefs, claim ledgers and a website card cannot supply missing comprehension.
- A software explanation can identify the supplied assets, the work performed and
the resulting output. Use current documented workflow; avoid memory perfection,
effortless output, unverified fidelity or guaranteed business results.
- A consumer product explanation can connect its supported purpose, relevant
formulation or design and actual use to the person's question. Preparation alone
is not a benefit explanation. An ingredient list alone is not a causal explanation.
- Separate documented operation, advertiser-stated purpose and observed effect.
Explain only what the evidence supports. Do not invent scientific causality or
claim that a taste test demonstrates a later physiological result.
Give the listener an ordinary reason to need the explanation. Their question should
follow what they heard or saw, rather than request the sponsor's exact feature list.
Let the answer change the next turn. Neither skepticism nor approval is mandatory.
An interviewer may openly represent the sponsor and explain it directly.
Use [human speech and behavior](human-behavior.md) throughout. The October 2026 human
review accepted improved speech while rejecting explanation depth and vague buyer
problems. Preserve that separate finding: a model's naturalness score must not erase
it, and partial acceptance is not approval of the complete ad.
## Check comprehension and time separately
Read only the literal opening, words, feasible actions and ending. State what a new
viewer can infer about the offering, how it helps this particular situation and
which part of the ad establishes that connection. If the answer requires the brief,
repair the explanation. This diagnostic tests communication, not efficacy or sales.
Leave room for replies, actions and the explanation. If the full idea exceeds the
recipe, propose a compatible execution or mark an exploratory longer script as
requiring another production route. Do not silently change fixed limits or remove
the explanation simply to make a count pass. Deliver the complete scripts and
separate human findings, model scores, claims and production readiness.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |