Update to HeyGen

{
  "description": "Create and confirm a four-view product reference sheet (front, side, back, close-up) from real product images before HeyGen video generation; never invents a product. Use when a UGC format skill asks for a product reference sheet, or the user asks for one.",
  "included_files": [],
  "name": "product-reference",
  "skill_md_contents": "---\nname: product-reference\ndescription: Create and confirm a four-view product reference sheet (front, side, back, close-up) from real product images before HeyGen video generation; never invents a product. Use when a UGC format skill asks for a product reference sheet, or the user asks for one.\n---\n\n# Product Reference\n\nCreate one approved product sheet so the same real product appears in every generated clip. The user sees and confirms the product views before any video is generated; this reduces changed shapes, labels, controls, and invented sides in the final video.\n\n## 1. Obtain real product evidence\n\nA real product image is required. Never generate a product from a name or description, substitute a lookalike, or fill a gap with a stock image. Accept evidence from:\n\n- **Chat attachments:** import each once with `import_asset_from_chat` as the calling workflow describes.\n- **The user's HeyGen assets:** an image the user uploads or picks in `open_asset_library` (opened with the photo request when available), if it can be supplied to image generation, for example through a returned URL.\n- **Official product images online, including from a page the user linked:** when the user supplied no photos (the UGC default) or asks you to find them. Read pages with authorized access only; never bypass access controls. Say you are using official images found online, and show them with the sheet so the user can confirm the exact product and variant in the same approval. Ask for a photo only when no official image can be found. When you ask, add one short tip — \"A clear photo of just the product on a plain background works best. Add one photo of any side or state you want shown, such as the back or the lid open.\" — and open `open_asset_library` in the same turn when it is listed.\n\nClassify every supplied image before it becomes an input to the sheet or to video:\n\n- A clean single product in one state: use it as supplied.\n- A composite showing one product in several parts or states, such as a closed product beside its removed cap, applicator, lid, or refill: split it into single-state references.\n- Several products, shades, sizes, or variants: isolate the one the user asked for.\n- A banner, collage, or text-heavy graphic: a source of claims and details only, unless a clean single-product region can be isolated.\n\nWhere code can run, crop the exact region from the original so the real label and color survive; otherwise isolate the product with image editing and compare the result with the original for shape, color, and label. Ask for a clean photo only when neither works. Never pass a composite, multi-product, or banner image on as an exact-product reference: generation copies extra parts, extra products, and staging such as drips or splashes. One clean front view often beats several mixed images. When a supplied image cannot serve as a reference, say in one sentence how it is used, such as \"I'll use the banner for its claims only.\"\n\nThen record which sides the evidence actually shows. Infer any side the evidence does not show, mark it as inferred, and keep it out of the video unless the user approves it; name it in the calling format's approval message, which also invites photos of that side.\n\nRaise a mechanics question only when an image leaves an action genuinely ambiguous, such as a pump, twist cap, latch, or port, and put it in that same approval message.\n\n## 2. Write the product truth sheet\n\nInspect the real reference and record a compact written description: object count, silhouette, proportions, colors, material, finish, closures, controls, visible lettering, scale, orientation, and absent features. Mark each side **photographed** or **inferred**; never describe a rear label or hidden port as known from a front view. Define handling states explicitly (cap attached, cap removed beside the bottle, lid resting open) and one size anchor: hand-relative for a handheld product, or relative to familiar surroundings (a countertop, doorway, or seat height) for a larger one; do not invent dimensions. Record part counts, attachments, and the side of each asymmetric part positively (one bottle with one pump fixed to it; one handle on the right when the logo faces the camera) so every storyboard and prompt can restate them; a positive statement of structure works better than a list of things to avoid.\n\nSeparate visible facts, user-confirmed mechanics, and claims (supplied wording kept exact). Preserve genuine branding when supplied; never ask the model to erase labels while claiming fidelity, and never introduce another brand. If lettering cannot survive generation, choose angles that reduce it or disclose the limitation. The truth sheet is the source for every storyboard, prompt, and spoken line; revise it only when new evidence resolves an uncertainty. It is text; the reference sheet below is the image. Neither establishes performance, ingredients, or fit.\n\n## 3. Generate the 2×2 reference sheet\n\nGenerate with the host's OpenAI image generation, preferring GPT Image 2.5 in its quality-oriented \"sunburst\" variant at high quality; if model or quality selection is not exposed, do not invent parameters or claim a setting was applied, and never stretch the result. Supply real images through the supported image input; a filename in a prompt conditions nothing. If a check fails, regenerate once with one targeted correction from the original inputs, never by editing a drifted output; if that still fails, show it and name the remaining issue. Show the actual sheet, never rejected drafts. When size is selectable, request a square canvas such as 1920×1920; otherwise use the largest square size offered.\n\nRequest one image, four equal panels:\n\n| Position | View |\n| --- | --- |\n| Top left | **Front:** straight-on, full product, labels readable |\n| Top right | **Side:** true profile, full product |\n| Bottom left | **Back:** straight-on, full product |\n| Bottom right | **Close-up:** one detail actually visible in the evidence, such as a control, texture, closure, or label |\n\nPrompt rules:\n\n- State the purpose first: a product identity reference sheet, not an advertisement.\n- Number every input and give it a role: \"Image 1 is a strict photographic reference for the exact product. PRESERVE its shape, proportions, colors, materials, controls, and every visible letter exactly. Images 2–N are additional real views of the same product.\" Restate the truth sheet's visible facts in words.\n- \"Exactly one product per panel; the same product in all four panels.\"\n- Plain neutral grey (#DCDCDC) seamless background, even soft studio light, a soft contact shadow, no props, hands, or people.\n- Whole product inside each panel with margin; thin plain gutters; nothing crosses a gutter.\n- \"No added text, labels, watermarks, or price tags.\" The product's own printed lettering is the only text and must match the evidence; never mirror it.\n- For an inferred side: \"Render this side plainly, continuing the visible form and materials. Add no text, logo, seam, port, button, or feature that is not visible in the supplied images.\"\n\nFor a wearable (Try-On), show the garment or accessory alone, laid flat or on an invisible form, never on a person; the character sheet controls the wearer.\n\n## 4. Check, then show\n\nBefore showing the sheet, compare it with the source images: silhouette and proportions, colors, control and part counts, label spelling and placement (zoom when available), no mirrored text, no duplicate product, no invented features on inferred sides, and a close-up that matches a real detail. If the generated sheet cannot hold fidelity, offer to use the original photos alone as references.\n\n## 5. Confirm with the user\n\nWhen called from a UGC format, show the sheet in that format's single approval message, beside the script and settings. Used on its own, ask: **\"Does this match your product? Approve, or tell me what to change.\"** Either way, name each inferred panel inside the same question and offer three answers: approve all including the inferred views, approve but keep the inferred views out of the video, or request changes. A plain \"approve\", or skipping this confirmation, covers the sheet but not the inferred views.\n\n## 6. Hand off the approved sheet\n\n- In UGC formats, the original product photos that match each clip's product state and the approved sheet are inputs to that clip's storyboard image, which becomes the clip's only reference image. Restate the truth sheet's visible facts in every prompt that shows the product.\n- Only when no storyboard can be used, transfer the approved sheet to HeyGen honestly: use a returned public HTTPS URL only if HeyGen can access it, `import_asset_from_chat` only when the host accepts the returned file object, or the genuine raw-upload workflow. Never treat an OpenAI file identifier as a HeyGen `asset_id`. Record the real `asset_id`; if no transfer path exists, tell the user and continue with the original photos alone. Put the matching original photos first in `reference_images` as the authority for shape and branding. Where code can run, crop the approved sheet into single-view panel images (no redrawing, so the approval holds) and add only the panels for what that clip shows, in the matching state. Otherwise add the whole sheet and state: \"Image N is a product reference sheet for angles only. Show exactly one product in a single full frame; never show panels, split views, grey backgrounds, or duplicate products.\"\n- **Inferred-panel lock:** never put an unapproved inferred view into a storyboard, or send an unapproved inferred panel, or a whole sheet containing one, to video. Never direct a shot that shows an unapproved inferred side; choose angles the evidence supports.\n- Record in the production ledger: evidence sources, truth sheet, photographed and inferred sides, sheet version, `asset_id`, and approval, including any approved inferred panels.\n"
}