[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CB2QZZZPKS0P8ECQ5QX16P":3,"skill-same:01M7CB2QZZZPKS0P8ECQ5QX16P":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M7CB2QZZZPKS0P8ECQ5QX16P","product-feature-demo-script",null,"Turn verified product features and selling points into visual commercial shot scripts with a clear trigger, product response, and visible user-facing result. Use for product advertisements that need functional demonstrations, interaction, before-and-after change, environmental stress, usage scenarios, or conceptual mechanism visualization instead of repeated rotations, orbit shots, floating packshots, and exterior-only beauty shots. Suitable for phones, cameras, headphones, watches, computers, appliances, tools, cosmetics devices, and other functional products. Never invent unsupported capabilities or performance claims.","VideoVerses\u002FCuti-Harness","VideoVerses","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F175584708?v=4","01M7CAV1DS56HR4KMB99EX9KAH","01M7CAV1EC999NFVVG4K7N1VJS",74,"MIT","https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Fskills\u002Fexternal\u002Fproduct-feature-demo-script\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: product-feature-demo-script\ndescription: >-\n  Turn verified product features and selling points into visual commercial shot scripts with a clear trigger, product response, and visible user-facing result. Use for product advertisements that need functional demonstrations, interaction, before-and-after change, environmental stress, usage scenarios, or conceptual mechanism visualization instead of repeated rotations, orbit shots, floating packshots, and exterior-only beauty shots. Suitable for phones, cameras, headphones, watches, computers, appliances, tools, cosmetics devices, and other functional products. Never invent unsupported capabilities or performance claims.\nmetadata:\n  kind: shot-script\n  version: \"0.2.0\"\n  roles: [guidance, stage_supervisor]\n  scope:\n    type: stage\n    selectors:\n    capabilities:\n      - atomic.text.generate\n      - atomic.video.generate\n      - api.provider.generate\n      - api.ark_protocol.generate\n    artifact_types:\n      - script\n      - storyboard\n      - video_clip\n  hooks: [before_stage, after_stage]\n  shot_script:\n    category: product_feature_demo\n    activation: default\n---\n\n# Product Feature Demo Script\n\nConvert a selling point into an observable event. Make the viewer understand what the product does, how it responds, and why the result matters. Do not use camera movement as a substitute for product behavior.\n\nOwn the visual narrative skeleton, not the spoken copy. Produce the shared `segment_script` first. Let effect Skills modify only selected visual beats, then let `product-voiceover-narration` fill narration into those finalized beats. Do not write final voiceover lines, select a narrator, or alter audio direction.\n\n## Produce the shared segment script\n\nCreate one structure per complete 15-second segment:\n\n```yaml\nsegment_script:\n  segment_id: segment-01\n  duration_seconds: 15\n  purpose: concise commercial purpose\n  beats:\n    - beat_id: segment-01-beat-01\n      start_seconds: 0\n      end_seconds: 3\n      narrative_role: hook\n      selling_point_status: verified\n      visual:\n        scene: visible situation\n        action: visible trigger or product action\n      narration: null\n```\n\nMake beat IDs stable and cover `0-15` continuously without gaps or overlaps. Use `selling_point_status: verified`, `conceptual`, or `unknown`. Keep `narration: null` at this stage; the narration Skill fills it later without redesigning the visual timeline.\n\n## Establish feature evidence\n\nClassify each proposed feature before scripting it:\n\n- `verified`: explicitly supplied by the user or reliably visible in the reference;\n- `conceptual`: a visual metaphor requested by the user that does not assert measured performance;\n- `unknown`: unsupported and forbidden from demonstration or claim.\n\nUse only verified features for factual demonstrations. Label conceptual mechanism views as conceptual in the planning artifact, not as engineering truth. If no feature is verified, demonstrate visible use, material response, ergonomics, assembly, controls, or accessories without inventing a capability.\n\n## Choose one demonstration pattern\n\nSelect the simplest pattern that makes the selling point visible:\n\n1. **Direct function:** a user or object triggers the product and the function visibly operates.\n2. **Trigger-response-result:** show the initiating action, product response, and observable outcome as one causal chain.\n3. **Before-after:** show a credible state change without unsupported competitor comparisons or fabricated metrics.\n4. **Environmental challenge:** place a verified function in a relevant situation such as low light, motion, noise, rain, heat, or workload.\n5. **Conceptual mechanism:** visualize sound, light, heat, airflow, energy, or internal motion only when a literal demonstration is impractical and the representation is clearly conceptual.\n\nDo not repeat the same pattern in every segment when several features are available.\n\n## Write one complete 15-second segment\n\nKeep every provider task at `duration: 15`. A useful functional segment is:\n\n- `0-3s`: establish the user need, situation, or challenge;\n- `3-6s`: show a clear user, object, or environmental trigger;\n- `6-10s`: show the product responding through visible action or a concise conceptual mechanism;\n- `10-13s`: reveal a concrete result the viewer can understand without explanatory text;\n- `13-15s`: return to the intact product and connect the result to a hero or packshot finish.\n\nAdapt the boundaries to the feature, but preserve causal order. Internal beats remain one prompt and one 15-second generation task.\n\nFor a 30-second advertisement with verified functionality, use at least one genuinely functional 15-second segment. Other segments may establish identity, material, lifestyle, or final brand value. Do not require every segment to contain a different feature.\n\n## Make actions specific\n\nState:\n\n- who or what activates the product;\n- the exact physical or interface action;\n- the product's visible response;\n- the resulting change in the subject, environment, captured media, or user experience;\n- the camera position needed to make the causal link readable.\n\nPrefer hands, silhouettes, environment interaction, objects, or product mechanisms when no actor reference is available. Avoid unreadable screen UI, generated text, charts, numerical overlays, and unsupported benchmark imagery.\n\n## Coordinate with effect Skills\n\nDecide the functional script before choosing a visual effect. Use an effect only when it clarifies the response or result. For example, use a compact exploded-view beat to reveal a verified or conceptual cooling structure, acoustic module, optical path, or battery layout; do not add disassembly merely because the product is mechanical.\n\nAn effect Skill may update the `visual` and `effect` fields of an existing beat. It must preserve the beat ID, segment duration, commercial purpose, and verified selling-point basis. After effects are finalized, freeze the visual beats before narration begins.\n\n## Reject empty beauty-shot plans\n\nRevise the plan before generation when:\n\n- all segments consist only of rotation, orbit, push-in, macro, floating, or static packshots;\n- a claimed feature has no visible trigger or result;\n- camera movement is the only action;\n- the same exterior view is repeated from several directions without new information;\n- the script depends on text to explain what the image does not show;\n- the prompt invents a feature, metric, comparison, certification, or internal mechanism.\n\n## Supervise the result\n\nAccept a functional segment only when the trigger, response, and result remain understandable in sequence; the product identity stays consistent; the action supports one primary selling point; and the segment still reads as a commercial rather than a tutorial.\n\nIf the result becomes vague, simplify to one feature, one trigger, one visible response, and one result before increasing prompt detail.\n","# Product Feature Demo Script\n\nConvert a selling point into an observable event. Make the viewer understand what the product does, how it responds, and why the result matters. Do not use camera movement as a substitute for product behavior.\n\nOwn the visual narrative skeleton, not the spoken copy. Produce the shared `segment_script` first. Let effect Skills modify only selected visual beats, then let `product-voiceover-narration` fill narration into those finalized beats. Do not write final voiceover lines, select a narrator, or alter audio direction.\n\n## Produce the shared segment script\n\nCreate one structure per complete 15-second segment:\n\n```yaml\nsegment_script:\n  segment_id: segment-01\n  duration_seconds: 15\n  purpose: concise commercial purpose\n  beats:\n    - beat_id: segment-01-beat-01\n      start_seconds: 0\n      end_seconds: 3\n      narrative_role: hook\n      selling_point_status: verified\n      visual:\n        scene: visible situation\n        action: visible trigger or product action\n      narration: null\n```\n\nMake beat IDs stable and cover `0-15` continuously without gaps or overlaps. Use `selling_point_status: verified`, `conceptual`, or `unknown`. Keep `narration: null` at this stage; the narration Skill fills it later without redesigning the visual timeline.\n\n## Establish feature evidence\n\nClassify each proposed feature before scripting it:\n\n- `verified`: explicitly supplied by the user or reliably visible in the reference;\n- `conceptual`: a visual metaphor requested by the user that does not assert measured performance;\n- `unknown`: unsupported and forbidden from demonstration or claim.\n\nUse only verified features for factual demonstrations. Label conceptual mechanism views as conceptual in the planning artifact, not as engineering truth. If no feature is verified, demonstrate visible use, material response, ergonomics, assembly, controls, or accessories without inventing a capability.\n\n## Choose one demonstration pattern\n\nSelect the simplest pattern that makes the selling point visible:\n\n1. **Direct function:** a user or object triggers the product and the function visibly operates.\n2. **Trigger-response-result:** show the initiating action, product response, and observable outcome as one causal chain.\n3. **Before-after:** show a credible state change without unsupported competitor comparisons or fabricated metrics.\n4. **Environmental challenge:** place a verified function in a relevant situation such as low light, motion, noise, rain, heat, or workload.\n5. **Conceptual mechanism:** visualize sound, light, heat, airflow, energy, or internal motion only when a literal demonstration is impractical and the representation is clearly conceptual.\n\nDo not repeat the same pattern in every segment when several features are available.\n\n## Write one complete 15-second segment\n\nKeep every provider task at `duration: 15`. A useful functional segment is:\n\n- `0-3s`: establish the user need, situation, or challenge;\n- `3-6s`: show a clear user, object, or environmental trigger;\n- `6-10s`: show the product responding through visible action or a concise conceptual mechanism;\n- `10-13s`: reveal a concrete result the viewer can understand without explanatory text;\n- `13-15s`: return to the intact product and connect the result to a hero or packshot finish.\n\nAdapt the boundaries to the feature, but preserve causal order. Internal beats remain one prompt and one 15-second generation task.\n\nFor a 30-second advertisement with verified functionality, use at least one genuinely functional 15-second segment. Other segments may establish identity, material, lifestyle, or final brand value. Do not require every segment to contain a different feature.\n\n## Make actions specific\n\nState:\n\n- who or what activates the product;\n- the exact physical or interface action;\n- the product's visible response;\n- the resulting change in the subject, environment, captured media, or user experience;\n- the camera position needed to make the causal link readable.\n\nPrefer hands, silhouettes, environment interaction, objects, or product mechanisms when no actor reference is available. Avoid unreadable screen UI, generated text, charts, numerical overlays, and unsupported benchmark imagery.\n\n## Coordinate with effect Skills\n\nDecide the functional script before choosing a visual effect. Use an effect only when it clarifies the response or result. For example, use a compact exploded-view beat to reveal a verified or conceptual cooling structure, acoustic module, optical path, or battery layout; do not add disassembly merely because the product is mechanical.\n\nAn effect Skill may update the `visual` and `effect` fields of an existing beat. It must preserve the beat ID, segment duration, commercial purpose, and verified selling-point basis. After effects are finalized, freeze the visual beats before narration begins.\n\n## Reject empty beauty-shot plans\n\nRevise the plan before generation when:\n\n- all segments consist only of rotation, orbit, push-in, macro, floating, or static packshots;\n- a claimed feature has no visible trigger or result;\n- camera movement is the only action;\n- the same exterior view is repeated from several directions without new information;\n- the script depends on text to explain what the image does not show;\n- the prompt invents a feature, metric, comparison, certification, or internal mechanism.\n\n## Supervise the result\n\nAccept a functional segment only when the trigger, response, and result remain understandable in sequence; the product identity stays consistent; the action supports one primary selling point; and the segment still reads as a commercial rather than a tutorial.\n\nIf the result becomes vague, simplify to one feature, one trigger, one visible response, and one result before increasing prompt detail.\n",{"name":5,"metadata":23,"description":7},{"kind":24,"hooks":25,"roles":28,"scope":31,"version":42,"shot_script":43},"shot-script",[26,27],"before_stage","after_stage",[29,30],"guidance","stage_supervisor",{"type":32,"selectors":6,"capabilities":33,"artifact_types":38},"stage",[34,35,36,37],"atomic.text.generate","atomic.video.generate","api.provider.generate","api.ark_protocol.generate",[39,40,41],"script","storyboard","video_clip","0.2.0",{"category":44,"activation":45},"product_feature_demo","default","main","60364690293feed5d9b458e19a441d4d7561e65e","services\u002Fvideo-runtime\u002Fskills\u002Fexternal\u002Fproduct-feature-demo-script",1,"https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness","https:\u002F\u002Fnewai.land\u002Fcuti-harness","https:\u002F\u002Fgithub.com\u002FVideoVerses","2026-10-11 19:27:56",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add VideoVerses\u002FCuti-Harness --skill product-feature-demo-script",{"tool":60,"command":61},"bunx","bunx skills add VideoVerses\u002FCuti-Harness --skill product-feature-demo-script",{"tool":63,"command":64},"pnpm","pnpm dlx skills add VideoVerses\u002FCuti-Harness --skill product-feature-demo-script","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Fskills\u002Fexternal\u002Fproduct-feature-demo-script\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"agents\u002Fopenai.yaml","REFERENCE","参考文档",309,"https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Fskills\u002Fexternal\u002Fproduct-feature-demo-script\u002Fagents\u002Fopenai.yaml",[75,82,89,96,103,111],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7CB3T5C44KCS1RRXMXXNCHF","external-shot-continuity","External continuity review method for long-form video projects.","https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Ftests\u002Ffixtures\u002Fexternal-skills\u002Fexternal-shot-continuity\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7CB3PKKR1JRB3XAG5S9T7NS","independent-story-workflow","Create a three-part story document without paid media generation.","https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Ftests\u002Ffixtures\u002Fdynamic-workflow\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7CB3K7RMRQ4WDYAYNC1S1S0","suno-song","Instruction helper: write a singable original Suno song from Bitwize (verbatim copy), then call suno.generate. Trigger: 原创歌曲, 写歌, Suno lyrics, $suno-song. Not a workflow.","https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Fskills\u002Fexternal\u002Fsuno-song\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7CB3CYCSAQENCW9SB58BYHC","short-drama-workflow","Workflow for producing plot-dense short dramas with character and location reference sheets, complete 15-second Seedance segments, native dialogue, parallel multi-reference T2V generation, duration validation, and final assembly. Use for 爽文短剧、都市反转短剧、对白短剧、连续多段短剧，或用户明确调用 $short-drama-workflow. Do not use for product-centered scenario advertisements.","https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Fskills\u002Fexternal\u002Fshort-drama-workflow\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":18},"01M7CB36GV8A2YX4P41457FRZ6","seedance2","Workflow: 即梦 Seedance 视频创意工作台。图+文案→看图分析→文案扩写→运镜→API生成。 触发词：即梦、Seedance、seedance、视频提示词、AI视频、运镜、短剧广告、$seedance2.","https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Fskills\u002Fexternal\u002Fseedance2\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Fskills\u002Fexternal\u002Fseedance2\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":18},"01M7CB2ZDR784PMJ60NZ616GWQ","product-voiceover-narration","Design concise native voiceover for commercial product-video segments and bind each spoken line to verified selling points, visible actions, and exact timeline ranges. Use when a product advertisement should introduce the product through narration, when Seedance 2.0 should generate picture and voice together, or when product shots need coordinated narration, music, and sound direction. Do not synthesize a separate voice track and never invent product claims.","https:\u002F\u002Fgithub.com\u002FVideoVerses\u002FCuti-Harness\u002Fblob\u002Fmain\u002Fservices\u002Fvideo-runtime\u002Fskills\u002Fexternal\u002Fproduct-voiceover-narration\u002FSKILL.md",[],[]]