0xsline/OpenChatCut / src/agent/skills/product-ad-video-script
product-ad-video-script
VerifiedTurn a product into ad angles, hooks, scenes, and CTA.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
| references/ad-script-framework.md | markdown | 9.1 KB |
references/ad-script-framework.md
View on GitHub# Evidence-Grounded Short-Video Ad Framework
Use this reference to turn verified product information into distinct ad angles, select the most defensible one, and map it to assets and an OpenChatCut timeline.
## 1. Build the product fact sheet
Record each fact with its source before writing hooks.
| Field | What to capture | Acceptable evidence |
|---|---|---|
| Product | Name, category, and what it does | User brief, product page, visible UI or packaging |
| Audience | Who it is explicitly for | User brief, page copy, documented customer segment |
| Problem | Friction the product addresses | Stated use case or directly observed workflow |
| Outcome | Concrete change the user can expect | Supported benefit, not an invented guarantee |
| Mechanism | Feature or process that creates the outcome | Visible interface, documented behavior, product media |
| Differentiator | Why this option is meaningfully different | Verifiable comparison or unique product behavior |
| Proof | Demo, measurement, testimonial, specification, or artifact | Supplied or visible evidence with usable rights |
| Offer | Price, trial, bundle, deadline, or availability | Current user-provided or product-page terms |
| Limits | Eligibility, conditions, exclusions, and uncertainty | Fine print, user notes, absent evidence |
Label every working statement:
- **Verified:** directly supported by a cited source or visible asset.
- **Observed:** visible in supplied media, but not necessarily a general product promise.
- **User-claimed:** provided by the user and attributed accordingly.
- **Assumption:** useful for planning but unverified; never present it as fact in the ad.
- **Unknown:** required information is missing; omit the claim or ask for clarification.
## 2. Define audience, problem, and outcome
Write one sentence for each:
- **Audience:** the narrowest viewer who will recognize the situation immediately.
- **Problem:** one costly, annoying, slow, risky, or confusing moment they already experience.
- **Outcome:** one visible or understandable improvement the verified mechanism can support.
A strong positioning line follows: **For this audience, the product changes this problem into this outcome through this verified mechanism.** If any element is an assumption, keep it out of final copy until confirmed.
## 3. Generate 2–4 distinct angle families
Choose genuinely different reasons to care, not minor rewrites of one hook.
| Angle family | Core question | Best evidence |
|---|---|---|
| Problem–solution | “Tired of this recurring friction?” | Before/after workflow, pain demonstration |
| Product demonstration | “Can it actually do the key job?” | Screen recording, product handling, result reveal |
| Outcome-led | “What changes after using it?” | Supported result, time/process comparison, finished artifact |
| Differentiator or objection | “Why this instead of the obvious alternative?” | Side-by-side behavior, specification, transparent limitation |
Do not force all families. Discard any angle that depends on unavailable proof, an unsupported comparison, or a claim too qualified to communicate clearly.
## 4. Score and select the angle
Score each candidate from 1 (weak) to 5 (strong).
| Criterion | Selection test |
|---|---|
| Evidence strength | Can every important claim be traced to a source or visible proof? |
| Audience relevance | Will the intended viewer recognize the problem or desire quickly? |
| Hook clarity | Is the value understandable without setup or jargon? |
| Visual demonstrability | Can available assets show rather than merely assert the claim? |
| Distinctiveness | Is this meaningfully different from the other candidates? |
| CTA fit | Does the promised next step naturally follow from the angle? |
| Safety | Can it run without prohibited, misleading, or overbroad claims? |
Prefer the highest defensible total, not the most sensational hook. Break ties with evidence strength, then visual demonstrability. Record why the winner beat the alternatives and which assumptions remain.
## 5. Hook rules
- Lead with the viewer’s situation, a visible result, a credible surprise, or the product in action.
- Communicate one idea in the first beat; avoid stacked benefits.
- Make the hook understandable with sound off using a concise caption or visual action.
- Match the hook to what the next beat proves; no bait-and-switch.
- Use specifics only when verified. Avoid fake urgency, absolute superiority, guaranteed outcomes, and invented social proof.
- Keep qualification close to the claim when it changes the claim’s meaning.
Useful structures include: **recognizable problem → consequence**, **result → how**, **product action → payoff**, and **common objection → evidence-backed answer**.
## 6. Build the beat map
Use 4–7 beats; duration follows comprehension and available evidence rather than a rigid formula.
| Beat | Job | Typical visual evidence |
|---|---|---|
| Hook | Earn attention and state why the viewer should care | Result first, problem moment, decisive product action |
| Context | Identify the viewer and situation | Relevant environment, interface state, concise caption |
| Mechanism | Show what the product does | Screen recording, product shot, annotated action |
| Proof | Support the promised value | Live demo, artifact, measured comparison, attributed quote |
| Benefit | Translate the mechanism into the supported outcome | Before/after sequence, reduced steps, completed result |
| Objection | Resolve the most likely credible hesitation | Condition, limitation, workflow detail, differentiator |
| CTA | Ask for one proportionate next action | Product view, URL or handle supplied by user, offer terms |
Each beat should advance the argument. Remove repeated claims, decorative scenes without a job, and any beat the available assets cannot support.
## 7. Choose proof and demo options
Use the strongest evidence available:
1. **Direct demonstration:** show the action and result in one continuous or clearly sequenced flow.
2. **Interface walkthrough:** show the relevant control, state change, and output; crop only for clarity.
3. **Artifact proof:** reveal the actual output, package contents, report, or completed work.
4. **Measured comparison:** show units, method, conditions, and source; avoid implying universal results.
5. **Attributed testimony:** use only supplied, authorized wording; do not upgrade an opinion into a fact.
6. **Specification proof:** display the verified feature or material and explain why it matters.
Editing can clarify evidence but must not fabricate causality, conceal a material condition, or turn separate events into a false continuous demonstration.
## 8. Handle one objection
Select the objection most likely to block the CTA: trust, effort, fit, price, learning curve, compatibility, or limitation. Answer it with evidence or a transparent condition. If no supported answer exists, omit the rebuttal or state the limitation plainly; do not invent reassurance.
## 9. Write a proportionate CTA
Ask for one action that matches the viewer’s evidence level: learn more, view the product, compare details, try an available feature, or use a verified offer. Include deadlines, prices, eligibility, and availability only when current and sourced. Never manufacture scarcity.
## 10. Map evidence to OpenChatCut
For every spoken or on-screen claim, identify:
- source and label: verified, observed, user-claimed, assumption, or unknown;
- supporting asset: supplied video, image, screen recording, product/page capture, text, or audio;
- timeline treatment: trim, crop, caption, callout, side-by-side, freeze, speed change, or simple transition;
- readability need: caption length, contrast, safe placement, and enough hold time;
- integrity check: the edit preserves order, scale, conditions, attribution, and limitations.
Use existing assets first. Request or create only media required by the chosen script. Do not add unsupported logos, endorsements, results, interface states, or synthetic “proof.”
## Claim safety gate
Before approval, verify that every material claim is sourced, appropriately qualified, and visually honest. Reject or rewrite claims involving guaranteed results, health or financial outcomes, superiority, endorsements, pricing, scarcity, or quantified performance unless the evidence explicitly supports the exact wording and context. Preserve user-provided legal or brand constraints.
## Output template
- **Fact sheet:** product; audience; problem; outcome; mechanism; differentiator; proof; offer; limits; source and label for each.
- **Angle candidates:** 2–4 family names, viewer insight, hook, required proof, key assumption, and scorecard totals.
- **Selected angle:** choice, evidence-based rationale, rejected alternatives, and unresolved assumptions.
- **Script:** beat number; purpose; voiceover or dialogue; on-screen text; evidence source; estimated duration.
- **Visual plan:** asset; in/out range or still; timeline treatment; claim supported; integrity note.
- **Objection and CTA:** objection, supported response, single next action, and verified offer conditions.
- **Final QA:** first-beat clarity; sound-off comprehension; claim traceability; proof visibility; pacing; CTA clarity; brand and safety constraints.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |