generating-ugc-videos

Files (6)

• SKILL.md
• eval_cases.json · evals/
• mode-review.md · references/
• mode-try-on.md · references/
• mode-tutorial.md · references/
• mode-unboxing.md · references/

SKILL.md (first lines)

# UGC Video

Turn a product into a video of a creator on camera.

Videos that do not have a person on camera with a product are out of scope — those should be generated by the `generating-videos` skill. 
A produced advertisement in the brand's voice — a commercial, TV ad or brand film where the person plays a role in the brand's spot rather than a creator sharing their own take — belongs to `generating-ad-videos`, even when a presenter is on camera.

**Settled for every job — never ask about these, and never re-decide them:** the delivered video is
`9:16` unless the user explicitly asked for `16:9` · the clip model is `seedance-2.0-fast` with audio
on, unless the user named one ·
storyboard sheets are `gpt-image-2` at `16:9` · how many clips there are comes from the length · the
clips are always joined, hard cuts, no transitions.

## Workflow

### Step 1: Read what you have

- **A product image or URL** → hand it to `analyzing-products` for what the product is, how a person
  physically uses it, which parts open or move, and what must stay identical wherever it appears.
- **Run `image_analysis` on every image supplied**, not only the product — what each one shows, and
  whatever the product facts leave out.
- **What each image is for comes from the brief, not from its contents.** A person in a frame does
  not make it a casting photo, and a second object does not make it a prop.
- **No product** → don't guess at one. It becomes the first thing Step 2 asks for.

### Step 2: Interview

**Skip this when the brief already settles the video** — a clear product, a clear format, a length.

Otherwise ask once, bundled into a single message, always with a free-text way out.

| Ask | When |
| --- | --- |
| **The product** — a link or a photo | Neither was supplied. Offer to wait for an upload; a photographed product beats a described one. |
| **How long** | The brief doesn't say. Offer 15s, 30s, 45s or 60s, and let them type their own. |
| **Whether the person in a supplied photo should be the creator** | An image with a person in it was supplied and the brief doesn't say who they are. Ask rather than assume either way. |
| **Whether they have a photo of the delivery package** | The brief is about opening a package and none is attached. If they have one, **wait for it to arrive** before building anything — a promised photo is not a photo. If they don't, a plain unbranded box stands in. |

When the user waives questions, take 15s, say in one sentence what you took, and keep going.

### Step 3: Select the mode and read the corresponding reference file

| The ask is about… | Mode | Reference |
| --- | --- | --- |
| Holding the product and talking about it | **review** | `references/mode-review.md` |
| Opening the package it arrived in | **unboxing** | `references/mode-unboxing.md` |
| Wearing it — clothing, shoes, jewellery, accessories | **try-on** | `references/mode-try-on.md` |
| Showing how to use it, one step at a time | **tutorial** | `references/mode-tutorial.md` |

**Where two rows both fit, these win:**

- **A sealed package is opened on camera** → **unboxing**.
- **The product ends up worn** → **try-on**, even when a bag is opened to reach it.
- **Numbered steps, or "how do I use this"** → **tutorial**, whatever the tone.
- **Nothing to open, wear or work through** → **review**.

### Step 4: Write the product description

Write one description and reuse it unchanged in every storyboard — rephrasing it between calls reads as a different product.

- **Material and finish**, surface by surface — matte or gloss, brushed, woven, translucent, or
  whatever this one actually is: *"brushed steel barrel, matte soft-touch collar, a woven wrist
  strap"*.
- **Size** — its width and height, and how it sits against a hand: *"sits in a closed palm, roughly
  9 cm tall and 4 cm across"*. Give the real measurements rather than likening it to another object,
  which the model renders inconsistently.
- **Two to five visual anchors** — features you can verify in the product image and nothing else:
  exact colours, the shape of a closure or handle, the gauge of a chain or strap, a surface finish, a
  distinguishing mark.
- **The product mechanism** — how it's built and how it works: the parts that move, how they open or
  close, and where anything dispenses: *"hinged lid at one end, folds back flat; the brush sits inside
  the cap"*.
- **What may be done with each part** — which parts are fixed to it, and the whole of what the moving
  ones allow. Nothing later does anything to the product that isn't on this list.

**Don't transcribe what the label says**, even where the product facts spell it out. Spelling out the
printing invites the model to redraw it, and redrawn text comes back warped. The facts may name it;
the description never repeats it.

### Step 5: Write the concept

**What the user asked for wins.** Wherever the brief is specific — a scenario, a shot list, a named
place, a line they want said, a mood — follow it exactly and keep following it for the rest of the
job. Everything it doesn't cover is yours to decide.

**Who the creator is, and where.** A brief that names them — the founder, the owner, a customer, a
specialist, someone the audience would recognise themselves in — settles it. Where it doesn't, pick
whoever this video is most believable coming from, and put them where it would actually happen: a
room, a workshop, a shop floor, a street, outdoors, etc.

**How many clips.** One storyboard becomes one clip. `list_video_models` gives the clip model's
shortest and longest clip — read them there rather than assuming. Make each clip as long as the model
allows and let the leftover be the last one; where that leftover falls under the minimum, give the
last clip the minimum anyway and let the video run slightly over. On a 4–15s model: 30s is two clips
of 15, 50s is 15, 15, 15 and 5, and 18s is 15 and 4.

**What the story can hold.** A **primary action** is one continuous motion at one object — picking a
thing up, tilting it, putting it on, pointing at it. Each one needs two seconds where possible, three at most, so a clip's
length is the number of primary actions it can carry. Write the story to that number.

These never render, so no part of the story asks for them:

- Anything finer than a whole hand movement — working a clasp, a zip, a drawstring, a pump head.
- Two motions treated as one, or a second object handled in the same breath as the first.
- **A change of state.** Where the product needs to be open, worn or empty, the panel arrives with it
  already so; the transition itself is never rendered.
- **No going back.** Once open, worn or emptied, it holds that state — nothing later reseals, removes
  or restores it.

**Write the concept down.** It is the one description of the video, and every step after this works
from it rather than deciding again:

- who the creator is
- how many clips, and how many seconds each
- what happens in each clip, following the mode guide's arc, within what that clip's length can hold
- roughly how many words each clip can carry, from its seconds

The clip lengths and the story are settled here. How each clip divides into panels is not — that is
the storyboard's to work out. Where the story itself has to change, change it here and say so.

From SupercmoHQ/superCMO-skills, Apache-2.0.

More from SupercmoHQ/superCMO-skills