Setup guideAPI setup
0/4
  1. Choose API pathAPI is the route.
  2. Copy OpenAPI pathFirst machine contract is ready.
  3. Read API keysScopes and bearer auth are clear.
  4. Ready to runYou have enough context to call v1.
SkillsZebrafish UGC Variant

Zebrafish UGC Variant

Use for one or more short UGC-style product ads, TikTok/Reels/Shorts creative, hook exploration, unboxing or review-style pieces, authorized testimonials, and paid-social variants that should feel native to their context.

Raw

One strong variant is valid. Do not force a presenter, fixed duration, stock hook taxonomy, CTA, or pack of outputs. Add Cinematic Scene or Product Demo Film guidance only when that craft genuinely drives the result.

Follow the shared production kernel from the Zebrafish root. This skill owns UGC judgment; the current production owns its treatment, script, prompts, references, timing, claims, budget, and variants.

Load by Need#

NeedRead
Define audience, tension, offer, source boundaries, or variant shapeShape
Write the hook, performance, proof, framing, edit, copy, captions, or soundCraft
Prepare prompts, references, state handoffs, live-model preflight, or dispatchGeneration
Compile the review contract or judge an actual artifactCritique
Diagnose and repair a weak or failed variantPolish

Load only the modules needed for the current action. Before spend-bearing video generation, read Generation and Critique so the prompt packet and observable acceptance contract agree. References are one level deep and self-contained.

Non-Negotiables#

  • Ground every factual spoken, captioned, or visible claim in supplied or Project sources. A generated demonstration or presenter reaction is not independent product, clinical, or customer proof.

  • Establish authorization before using a real person's likeness, voice, testimonial, or persona.

  • Keep the opening frame, first requested action, speech, visible text, and sound state compatible.

  • Review the exact final bytes with the shared actual-artifact harness. Technical validity cannot waive extra anatomy, impossible contact, identity or product drift, false proof, malformed text, masked speech, or a broken hook-to-payoff transition.

  • Deliver only the generation and SHA-256 that match the final review receipt admitted by application code.

Choose direct operations or workflows from live capabilities. Stop rather than guess when material claims lack sources, allowed identity use is unclear, the provider rejects the proposed reference strategy, budget approval is absent, or required media cannot be inspected.