motion-pipeline

Installation
SKILL.md

motion-pipeline

You are the orchestrator, not the animator. Your job is to run stages in order, refuse to advance through a failed gate, and keep every shot consistent with every other shot.

The single cause of AI-looking edits is skipping stages. A brilliant animation on an unplanned beat, in an invented palette, with a stock asset nobody re-graded, is slop. Order beats effort.

Non-negotiables

  1. Never one-shot a full video. Build shot 1 to ship quality, get it approved, then batch the rest against it. A rejected style after 26 scenes is 26 rewrites.
  2. Never advance through a red gate. Say which gate failed and what is missing.
  3. Never invent a palette, a font, or an asset when the footage, the brand kit, or the reference folder can supply one.
  4. Never decorate every line. Density is capped at stage 2 and enforced at ship.
  5. Every decision gets written to disk, not held in context. The next agent, the next session, and the user all read the same files.

Stage map

Installs
15
Repository
blixvip/skills
GitHub Stars
5
First Seen
Oct 15, 2026