Skip to main content

product-ad-video-script

Turn a product into ad angles, hooks, scenes, and CTA.

소스 정보

저장소
0xsline/OpenChatCut
최근 소스 활동
2026년 8월 1일 12:19
감지된 SKILL.md 언어
영어
스타
2,277
포크
345

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
product-ad-video-script
description
Turn a product into ad angles, hooks, scenes, and CTA.
# Product Ad Video Script Use this workflow when the user wants to turn a product, landing page, offer, screenshot, or rough idea into a short ad video plan and script. Use this workflow to plan the ad first, then execute only the assets and edits the chosen script actually needs. ## When to Use - The user provides a product, product page, app, feature, screenshot, or offer. - The user asks for ad copy, hooks, UGC script, promo video, product reel, launch video, or short-form marketing video. - The task needs angles, scene structure, captions, CTA, and visual treatment. ## Workflow 1. Read the product context: what it is, who it is for, core benefit, proof, offer, limitations, and required claims. 2. Extract or infer the customer problem, desired outcome, objections, and strongest differentiator. 3. Pick or propose 2-4 ad angles using [references/ad-script-framework.md](references/ad-script-framework.md). 4. For the chosen angle, write a concise video structure: hook, problem, demo or proof, benefit, objection handling, CTA. 5. Map each beat to required visuals using product/page assets or user-provided media. Generate new visuals only when the script needs them. 6. Create the timeline or present the script first depending on the user's intent. 7. QA claims, readability, pacing, CTA clarity, brand fit, and whether the first seconds explain why the viewer should care. ## Rules - Ground claims in the product page, user notes, or visible assets. Do not invent prices, guarantees, medical claims, revenue claims, or endorsements. - Prefer clear benefits over feature lists. - Keep hooks concrete and viewer-facing. - If required information is missing and affects truthfulness or positioning, ask or label the assumption. - Match the visual plan to what OpenChatCut can make now; do not prescribe external-only steps unless the user asks. - Do not add transitions, effects, music, or voiceover unless the selected script calls for them. ## Output For planning, show angle, target viewer, hook, script beats, visual plan, captions, CTA, and assumptions. For execution, also report what was added to the timeline.
GitHub에서 보기