omniflash-restyle
Arcads Omni Flash Restyle
Turn raw talking-head footage plus a reference edit into a finished scene-by-scene restyled video, entirely on the Arcads MCP connector plus local ffmpeg. The reference look this skill was built on: hard background replacement per scene, chunky kinetic typography synced to speech, sticker and doodle overlays, retro UI frame devices, aggressive reframing, one visual idea per phrase, style change every 1 to 2 seconds.
All skill outputs are in ENGLISH regardless of conversation language: the style spec, the timeline plan table, every generation prompt, QC notes, and delivery notes. Conversational replies may follow the user's language, but the artifacts are English. No em dashes anywhere in output; use commas, periods, or parentheses.
What Omni Flash can and cannot do (verified, do not re-litigate)
- CAN: multiple timed scene changes in one call. A timestamped multi-scene prompt ("0 to 2s: X. 2 to 4s: Y. 4 to 6s: Z.") executes reliably, including 1 second pacing. This is the default mode. Same internal-timeframe prompt structure as the vox-animated-ad Seedance skill.
- CANNOT: input or output shorter than 3 seconds or longer than 10. Schema: duration integer 3 to 10, referenceVideos as source. The 3 second floor constrains the clip you feed it, never the scene pacing inside it.
- CANNOT: competing simultaneous edits on the same element. "Replace the background AND regrade the whole image" style stacked global instructions drop one silently (verified in earlier sessions). Sequential timed scenes are fine; simultaneous competing transforms are not. One dominant transformation per scene beat.
- KNOWN DRIFT RISK: the person's face. Verified in field use: without countermeasures Omni Flash alters facial features during restyling. The countermeasure is video-as-truth framing (below): the source video is the identity ground truth, still face references stay OUT of standard beats, and every prompt opens with the preservation lock. This is mandatory in every call, not optional polish.
- DO NOT TRUST: audio. Discard generated audio always; relay the source voice in post.
The practical consequence: input length is a chunking problem, not a model problem. 10s or less is one call. 60s is 6 to 7 calls, not 15.