Assemble a 3D-CGI app sizzle — nano-banana CGI plates (blank-glow floating phone + smoky-black studio + amaranth rim-light + placeholder burst shapes) plus PIL compositing of the REAL App Store screenshots onto the bezel + burst-out overlays, driven by Kling 3.0 i2v steady-float per beat with a per-beat Ken-Burns FFmpeg push-in fallback when Kling garbles the UI, then VO/music mix (sidechain duck, loudnorm) + 1.15x speed + anti-AI grain finalize. The on-screen UI, instructor faces, and wordmark are ALWAYS real assets composited via PIL — never AI-rendered. The paid steps (plates, i2v clips, VO, music) are separate capabilities; this ships the config + PIPELINE + FREE assembly and the recipe orchestrates the spend. Use for the cgi-app-sizzle video format.
64
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/ads/capabilities/render-cgi-sizzle/SKILL.mdAssembles the 3D-CGI app sizzle video format: a gold-trimmed phone floats in a smoky-black studio while six app features demo one per beat — each beat bursts REAL App Store UI elements out of the phone in 3D with amaranth rim-light + bokeh, then everything collapses back into the screen at a climax ("200+ classes. One app.") + a brand end card over a premium-tech bed. It reads as an Apple-keynote product film, not UGC and not a physical-product shoot.
This capability ships the recipe (scripts/config.example.json) + a config→step map
(scripts/PIPELINE.md) + the FREE-assembly how-to (scripts/README.md). It documents the
FREE, deterministic assembly between the paid model calls:
--anchored on beat 1 so the phone/studio stay
identical across beats.scene-NN-composite.png;
bake real burst-out overlays (e.g. climax instructor portrait tiles, rim-light baked before
rotation) around the plate. The on-screen UI + faces + wordmark are ALWAYS real assets —
never AI-rendered, so no claim is invented and nothing reads fake.zoompan, heavier on the climax) — the shipped demo used this
path for the feature beats.See scripts/README.md for the full FREE-assembly detail and scripts/PIPELINE.md for the
config-field → source-step map.
Config-and-PIPELINE capability (no re-built runnable pipeline here). Copy
scripts/config.example.json → config.json, edit the brand/beats/screens, and follow
scripts/PIPELINE.md:
VO first (locks the timeline) → nano-banana CGI plates → PIL screen composites → burst-climax overlays → Kling i2v clips (Ken-Burns fallback per garbled beat) → PIL end card → captions → sidechain-ducked mix → 1.15x speed + grain.
Output: 1080x1920, ~22.6s H.264 (+ AAC music). 6 feature beats + PIL end card.
8866b2a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.