lyt-video-script

lyt-video-script: Product Short Video Shooting Script

This skill translates confirmed product facts into purchase reasons that target users can see and understand, then organizes those purchase reasons into a shootable, executable, and verifiable e-commerce short video script.

A script is a content hypothesis, not a viral prediction or a sales promise.

General Rules

After entering this skill, first read and comply with ../lyt/references/common-rules.md. This file only supplements the exclusive boundaries, evidence gates, and execution process for product short video scripts; in case of conflict, the stricter constraints on facts, compliance, and executability shall prevail.

Usage Boundaries

Only handles:

Generating a complete shooting script based on an existing product, images, link, materials, or selling points
Organizing existing product copy, voiceover scripts, or content ideas into shootable storyboards
Generating product video scripts with a real person on camera, only hands shown, or no people
Generating scripts for organic traffic, product clicks, ad creatives, or influencer seeding scenarios
Generating lines, on-screen text, and Chinese back-translation in the target market language
When the user explicitly requests it, generating multiple single-variable test angles for the same product

Does not handle:

Recommending categories or products from scratch; transfer to lyt-product-selection
Judging whether a product can be tested or is viable; transfer to lyt-product-validation
Diagnosing product main images, detail pages, or product first screens; transfer to lyt-page-diagnosis
Analyzing views, completion rate, clicks, add-to-cart, or order data for published videos; transfer to lyt-data-analysis
Directly generating, shooting, or editing videos
Non-product personal IP, knowledge voiceover, and general self-media copy

The user does not need to complete product validation first to invoke this skill. As long as there is already a specific product and the goal is to generate a shooting script, proceed directly; however, do not infer that the product is worth doing just because a script can be generated.

Supported Inputs

Product images, product screenshots, product links, supply chain materials, or product descriptions
Confirmed functions, materials, specifications, selling points, audiences, and usage scenarios
Country/region, platform, target language, and video goal
Existing product copy, voiceover scripts, storyboard drafts, or shooting ideas
Shooting conditions: people, location, equipment, duration, props, whether to show face, and post-production capabilities
Target style: UGC, usage demonstration, pain point solution, comparison, review, scenario, detail proof, or other styles

Do not modify original attachments. Original identifiers such as product name, SKU, item number, brand, model, specifications, link, and target market shall be retained as-is.

When to Read the Knowledge Pack

Except for out-of-scope transfers, after entering the product short video script scenario, read references/product-video-script.md。

When the user requests multiple script versions, A/B testing, test metrics, or continue/pause conditions, then read ../lyt/references/experiment-rules.md。

Basic Axioms

Fact axiom: A script may only use confirmed product information, and must not fabricate functions, materials, certifications, reviews, sales, or usage effects.
Audience axiom: A product selling point can only be converted into a purchase reason when it enters a specific audience and usage scenario.
Visual axiom: A short video is first and foremost visible actions, processes, changes, and results, not a product introduction rewritten as a voiceover.
Single-proposition axiom: A short video should prioritize validating one core purchase reason, not stack all selling points at the same time.
Consistency axiom: The people attracted by the opening, the problem shown in the body, the solution provided by the product, and the final call to action must be consistent.
Executability axiom: A script that cannot be filmed within the user's existing personnel, location, equipment, budget, and time is not an effective script.
Verifiability axiom: A script is a hypothesis about content performance awaiting validation, not a guarantee of traffic or sales.

Decision principles

First extract product facts, then decide the content angle.
First determine the video objective, then design the opening.
Organize content according to "audience → scenario → problem → product action → visible result."
Product selling points must be transformed into actions, details, comparisons, or evidence in the shots.
Efficacy and promises without supporting evidence must not enter the dialogue or on-screen text.
Voiceover cannot replace product demonstration, and on-screen text cannot replace key shots.
The opening must not only create retention but also be relevant to the product purchase reason.
A script should retain only one main content mechanism.
Filming conditions are constraints before script generation, not an additional check after generation.
When batch testing different angles, each video should change only one main variable.

First-round response gate

When there is no specific product, first ask the user to provide product images, links, product names, or materials; do not select products on your own.
When product materials are available, first extract "visible facts / user statements / inferences / unknowns," and do not write appearance guesses as functional facts.
Only ask about the key gaps that most affect the script. Priority: target market/platform → video objective → filming conditions → target audience/scenario → style.
When the style is unspecified and would change the filming approach, ask the user whether they want UGC, usage demonstration, pain-point solution, comparison, review, scenario, detail proof, or a custom style.
When the user explicitly requests "direct generation" or leaves the choice to the Agent, you may generate after making minimal assumptions, but the assumptions must be explicitly written in the script brief.

Execution process

Identify the task mode: generation from product, conversion of existing copy into storyboard, target-language localization, or multi-angle testing.
Extract product facts and mark unknown information and expression risks.
Determine the country/region, platform, target language, video objective, and filming conditions.
Establish the hypothesis of "audience—scenario—need—product solution."
Choose one main content mechanism and distill one core purchase reason.
Transform the core purchase reason into visible shot actions, dialogue, on-screen text, and sound.
Scale down the filming plan according to the user's people, location, equipment, props, duration, and post-production capabilities.
Check whether the opening, audience, scenario, product action, purchase reason, and CTA are consistent.
Check risks in efficacy, certifications, price, discounts, reviews, comparisons, and localized expression.
Output a script that can be filmed directly, explaining the content hypothesis this video is validating.

Output requirements

By default, generate only one complete script. Generate multiple scripts only when the user explicitly requests batch, multiple versions, A/B, or multi-angle testing.

Tier	Applicable scenario	Output
Lightweight	Product or key conditions insufficient	Fact extraction + one key gap + next step
Standard	Product, goals, and shooting conditions sufficient	Script brief + storyboard table + shooting checklist + risks + validation hypotheses
Test group	User explicitly requests multi-angle testing	Shared baseline + multiple single-variable scripts + test cards

Standard output structure:

# 产品短视频脚本：{产品名}

## 产品事实与待确认信息
{已确认事实、用户陈述、未知信息和不得使用的表达}

## 脚本简报
{国家/平台、目标语言、视频目标、人群、场景、风格、时长、拍摄条件、核心购买理由}

## 拍摄脚本
| 时间 | 画面与动作 | 景别/机位 | 口播或声音 | 屏幕文字 | 产品信息 | 剪辑提示 |
| --- | --- | --- | --- | --- | --- | --- |

## 拍摄清单
{产品、道具、人物、场地和需要预先准备的素材}

## 事实与合规风险
{不得讲、待确认、需替换的表达}

## 本条验证什么
{一个内容假设 + 对应的用户行为}

Handoff rules

Trigger condition	Next step
User has no specific product and wants to find a direction first	Hand off to `lyt-product-selection`
User really wants to judge whether the product can be tested	Hand off to `lyt-product-validation`
User wants to diagnose the main image, detail page, or product first screen	Hand off to `lyt-page-diagnosis`
User provides playback, completion, click, add-to-cart, or order data for a published video	Hand off to `lyt-data-analysis`
User only says the video has no traffic and no orders, but the object, action, and data are unclear	Hand off to `lyt-problem-clarifier`

When handing off, retain the product, country/platform, confirmed facts, script hypotheses, expression risks, and the most critical gap.

Prohibitions

Do not fabricate product features, materials, dimensions, certifications, test results, user reviews, sales, discounts, or scarcity.
Do not guess efficacy, audience, materials, or scope of application from the product's appearance.
Do not use "guaranteed to go viral," "guaranteed to sell," "will definitely convert," or "the platform will definitely give traffic" to describe scripts.
Do not pile all selling points, content mechanisms, and target audiences into the same video.
Do not write only voiceover; you must specify shootable visuals, actions, props, and shots.
Do not automatically generate multiple scripts when the user only wants one script.
Do not copy competitors' lines, brand identity, user reviews, or protected creative expression.
Do not judge that a product is worth doing or can make money just because you can generate a script.