Oil Motion

Why it's ranked here

The system earns attention for the hard gates baked into its pipeline rather than for the AI generation step itself, which is really just a wrapper around a third-party video model. Before batch production starts, a script hashes every approved pilot artifact and refuses to continue if a single byte changed. Adjacent video segments are checked with a similarity and error metric before they ship, not eyeballed. Delivery format, sprite sheet or compressed video, is chosen by a budget script rather than left to guesswork. MIT licensed, which keeps adoption low-friction.

What's good

The byte-level check before batch production is the standout piece: it hashes the exact first frame, last frame, contract file, and pilot clip that a human signed off on, and blocks any run that doesn't match those hashes exactly. The continuity check between video segments compares brightness, structure, and color statistics between the last frame of one clip and the first frame of the next, giving a numeric pass or fail instead of a guess. Credential handling stores generation-service keys through the operating system's own secure store and raises an error rather than silently writing them to a plain configuration file.

Tradeoffs

It only works inside an AI agent environment that can read its instruction file and run shell commands, so it isn't something a person launches directly the way they would a CLI tool or library. The generation step depends on a paid third-party video and image API, ZenMux or MiniMax by default, which is an ongoing external cost and dependency the repository itself doesn't control. Running it locally means installing Python, ffmpeg, and a handful of Python packages, plus a Node.js runtime just for the one page that stores API keys. The documentation is written primarily in Chinese, which will slow down teams that don't read it.

How to use it well

This fits teams already working inside an agent-based coding setup who want a scroll- or pointer-driven hero animation built from AI-generated footage without hand-tuning chroma key thresholds or writing a state machine for playback. It is overkill for a simple looping background video or a one-off social clip, and it doesn't replace a video editor for content that isn't going to respond to user input. Budget for the external generation service's cost and for a first pilot segment before committing to a full multi-segment sequence, since the pipeline is built to block cheaply rather than fail expensively later.

Observed

License

MIT

Interface

Agent skill (SKILL.md) with an OpenAI-compatible agent manifest, not a standalone CLI or library

Runtime dependencies

Python 3 with Pillow, NumPy, and PyYAML, plus system ffmpeg and ffprobe binaries

Credential storage

OS keyring backend (SecretService, Keychain, or Credential Manager); no plaintext fallback if unavailable

Additional platform requirement

Node.js 22.18 or newer for the local API-key configuration page

Documentation language

Primarily Chinese, including the README and skill instructions

Delivery formats produced

WebP sprite atlas, chroma-key MP4, or fully baked MP4, chosen automatically by a budget script