DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check an AI motion video against the mog gates with Motionmaxxing

Run the render checks and page-chrome lint on an AI-made video to see which tells it fails.

  • Content
  • Intermediate
  • 1 hour
  • From the README
  • Claude Code

Who it is forA video editor or reviewer who has an AI-generated motion graphics clip and needs to know why it looks mid before reworking it.

The problemA generated video can look finished while still showing corner labels, dead frames, long end holds, or deck layouts, and nobody has measured it.

The outcomeA list of gate results (G0 to G5) with the numbers behind each, plus the lint hits, so you know what to fix first.

What you need first

  • Node 22+
  • Python 3
  • ffmpeg
  • Go
  • An agent that reads a SKILL.md folder, such as Claude Code
  • A brand website URL or a brief for the film
  • An ElevenLabs key, only if you want generated voice and sound

Steps

  1. Copy the AI-made MP4 and its HTML source into a working folder. (inferred, check the README)
  2. Run look.py on the MP4 to get the render results for G0, G2 and G3. (inferred, check the README)
  3. Run lint.mjs on the HTML source to list page-chrome hits for G5. (inferred, check the README)
  4. Open the contact sheet and judge G1 (proof readable) and G4 (one hero per frame) by eye.
  5. Note each failed gate and the number behind it in a short report.

Prompt for your agent

Using the motionmaxxing skill from Tejashmakwana/motionmaxxing, run look.py and lint.mjs on <path to video and HTML source>. Report each gate G0 to G5 with its number and pass or fail, and say which two gates need a human look. Verify that every number in the report came from a script output.

Caveat. The lint cannot see text inside an image or a canvas, and the README says it is a lead rather than a verdict.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page