跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

ecommerce-product-montage

Assemble product footage, UGC, and b-roll into a conversion-oriented montage with a hook → pain → demo → proof → CTA rhythm. Use for 带货混剪, 产品混剪, 商品短视频, 种草视频, ecommerce montage, product reel, UGC cutdown, or when the user wants selling footage cut into a short that converts.

AI 与智能体2.2ksrc/agent/skills/ecommerce-product-montage/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/0xsline/openchatcut/ecommerce-product-montage/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Ecommerce Product Montage

Use this workflow when the goal is a short that sells, not just one that looks good. The failure mode to avoid is a pretty montage with no sales spine: strong footage, pleasant cuts, and zero reason for the viewer to act.

This workflow decides structure and sequencing for selling footage. It does not write the ad copy — when the hook, angles, or CTA text are not given, hand off to product-ad-video-script for the script, then come back here to assemble. It does not re-explain music tooling — for beat-driven placement use beat-sync-montage or music-intelligence.

This is a OpenChatCut-native workflow. Use the current project, source assets, asset-frame inspection, AV/script context, and OpenChatCut editing tools.

When to switch workflows

  • No script yet, only a product/offer → product-ad-video-script first, return here to cut.
  • Music should drive the cut placement → beat-sync-montage (and music-intelligence for tools).
  • Many clips, no selling intent, just the strongest cut → multi-clips-to-reels.
  • N distinct selling variants from one pool → batch-montage-variants, using this workflow per cut.

Workflow

  1. Fix the one job the edit must do: which objection it dissolves or which action it drives (save, tap, buy, follow). If the brief names none, propose one and confirm.
  2. Inventory the material by sales role, not by file: hero demo, UGC reaction, proof (review/result), context b-roll, price/offer card. See references/material-roles.md. Footage that fills no role is parked, not force-inserted.
  3. Lay the sales spine before cutting: hook (0–3s, the open loop) → pain/context → demo → proof → CTA. See references/sales-spine.md. Every beat maps to a spine position; a clip with no spine position is cut.
  4. Lead with the hook from a real moment, not a title card. The first three seconds either open a loop ("you are doing X wrong") or show the payoff; a logo sting as opener loses the scroll.
  5. Place the demo where the viewer is curious, not where the script says "demo." Demo proves the hook; if the hook is a result, demo the path to it.
  6. Insert proof as a pattern interrupt, not a block. One real review line or result frame beats a stacked proof montage. See references/proof-placement.md.
  7. Hold the CTA long enough to read. Price, offer, and the exact action each get a legible beat; a CTA flashed for one cut is a CTA nobody acts on.
  8. Keep claims grounded. Do not manufacture prices, guarantees, medical, or earnings claims the assets do not support. Pull offer text from the product page or user notes; if absent, ask.
  9. QA by the spine, not by the cut list: can a cold viewer state the offer and the action after watching once? If not, the edit sells nothing.
  10. Report the spine coverage and any role with no usable footage, so a thin section is flagged before shipping.

Plan Format

  • The one job this edit does
  • Material inventory by role, with what is missing
  • Spine map: timestamp → spine position → which clip → why it earns that slot
  • Hook type (open loop / payoff) and the moment used
  • Proof placement and the interrupt it creates
  • CTA beats: price, offer, action, each with duration
  • Risks: ungrounded claims, thin demo, CTA too short, hook that does not land

Rules

  • Spine over polish. A serviceable cut in the right spine position beats a beautiful cut that breaks the argument.
  • Hook is a moment, not a card. Open on footage that creates tension or shows the result; title cards come later if at all.
  • One job per edit. An edit trying to handle every objection handles none. Pick the one that converts this audience.
  • Proof interrupts, it does not pile. One credible proof point lands harder than five weak ones.
  • CTA must be legible. Price, offer, and action each get a readable beat; never flash the CTA.
  • Claims stay grounded. No invented price, guarantee, medical, or earnings claim. Ask when the asset is silent.
  • Park, do not force. Footage that fits no spine position weakens the edit; leave it out and say so.

相似的 Skill

brand-guidelines
anthropics/skills180k

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

AI 与智能体

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

AI 与智能体

template-skill
anthropics/skills180k

template-skill

Replace with description of the skill and when Claude should use it.

AI 与智能体

mcp-builder
anthropics/skills180k

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI 与智能体

algorithmic-art
anthropics/skills180k

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

AI 与智能体

academy-guide
anthropics/skills180k

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

AI 与智能体