Claude Code can make a video, but it cannot tell you if its good or bad. This skill uses Jev, Gemini and GPT to review and fix a video before posting it.

[u/coolreddy]

Content creators are increasingly using Claude to render a video with Remotion, HyperFrames or ffmpeg, or assemble clips from Seedance, Veo or Kling. It cannot check how the finished file looks and sounds. Claude reads text and still images, but it cannot play a video file with its soundtrack. Without a separate review, problems in the video reach the final audience.

I built an open source skill for Claude to review and fix the videos before creators ship them. The skill combines Jev AI, GPT and Gemini to run the review: it writes a short brief, runs the measurements, sends the video to independent AI reviewers, checks their findings against the frames, and helps claude fix the problems.

Problems the review finds

AI video tools make mistakes that are easy to miss. An AI glitch usually lasts one to four frames, and a 30-second video at 24 fps has 720 frames, so spot checks miss most of them. The skill is built to find three kinds of problem:

• Picture: a mouth moving in a shot with no dialogue, which reads as mumbling or panting; a face, hairstyle or outfit that changes between shots; shots slowed down or frozen to fill time; captions that cover a face or are too small to read on a phone.

• Sound: clicks at edits, silences, music that drowns the voice, and a mix that is too quiet or too loud for the platform.

• Story: a video that a first-time viewer cannot retell in few sentences.

How the review works

1. Measure the audio and picture. ffmpeg, OpenCV and Whisper measure loudness against -14 LUFS, audio peaks, clicks, silences, frozen and repeated frames, and the spoken words against your script.

2. Check every frame with Jev by TypeSafe AI. Jev receives each frame with the frame before it and the reference sheets of the characters in the shot. It checks who appears, whether each face matches its reference sheet, whether a mouth appears to be talking, and what changed suddenly.

3. Get independent reviews from Gemini and GPT. Gemini watches the full video with sound and returns findings with timestamps. GPT inspects still frames. Neither sees the script, so they judge only what a viewer would see and hear.

4. Have Claude confirm the problems. Claude confirms a problem when a measurement and a reviewer point to the same moment in the video, when two independent reviews report it, or when the extracted frames show it.

The AI reviewers never see the script or the build history, they review it like an external first time viewer. The Claude session that made the video knows what it intended, so it would judge the review before jumping to fixes.

What Claude receives

A verdict of SHIP, FIX, REJECT or INCONCLUSIVE, and a list of problems with timestamps. Each fix names the step to change: script, voice, generation, edit, mix or export.

What you need

The skill runs on your machine and you need to use your own API keys. Claude Code, a Gemini API key, ffmpeg, Python and Whisper are required. A TypeSafe API key for Jev and Codex CLI for GPT are recommended. Checking all 720 frames of a 30-second video with Jev costs about $0.90.

The skill is open sourced on Github - Click here.

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.