onetake gives Claude a continuity test for product videos

A common failure in AI-generated product videos appears at every scene boundary: title card, fade, interface shot, fade, feature card, fade, logo. The individual shots may look polished, yet the sequence behaves like a slideshow because each scene replaces the last. onetake, a Claude Agent Skill whose repository showed 747 GitHub stars at the time of writing, treats those boundaries as design constraints.

A Claude Agent Skill packages instructions, scripts, and resources that a compatible coding agent can load for a specialized task. onetake uses that format to produce 15- to 30-second launch films, teasers, and feature demos built around one continuous virtual camera. Its verification loop measures whether each beat visibly grows from the previous one.

Continuity becomes the constraint

Every transition must preserve an element already visible on screen and transform it into the next beat. The repository demonstrates several forms of this visual carry:

• A prompt bar opens into an application window, which reflows into a phone.
• A bar collapses into a line that crosses a desk and becomes the next scene’s first grid line.
• A card expands into a page or fills the frame to reveal the following scene.
• The final cast of elements folds into the product lockup.

One virtual camera follows those transformations without cutting. It anticipates where an element will land, pans or whips toward it, adds slight handheld drift, reacts to impacts, and pauses between larger moves. Those periods of stillness keep the continuous take legible and give faster motion room to register.

The oracle can reject a render

The technical centerpiece is a verification loop called the oracle. Before a human reviews the film,