video-director
An instruction-and-QA skill that guides a coding agent to plan, build, render and verify short videos written as code (HTML/Canvas/SVG/Three.js, GSAP or Remotion) and rendered to MP4. It also covers reviewing and fixing existing coded videos.
What it can touch
| files | write |
|---|---|
| network | github.com |
| shell | runs commands |
| secrets | none found |
What it actually does
SKILL.md and its reference files are long craft guidance: workflow phases, timing and typography numbers, sound and loudness targets, honesty rules for on-screen facts, and a critic rubric. Two local Python scripts back them up. - check_timeline.py reads a timeline.json and prints errors and warnings. - qa_video.py runs ffmpeg/ffprobe on a rendered MP4 through subprocess argument lists (no shell=True). It analyses frames and audio, then writes contact-sheet JPEGs and report.md/report.json into an output folder. - The eval scaffold scripts only copy fixture files into the working directory. The instructions direct the agent to run these scripts, render with Playwright or Remotion, use local TTS, optionally browse primary sources for facts, and spawn a critic subagent. Nothing reads credentials, contacts hidden hosts, sets up persistence or contains hidden instructions. No invisible characters or prompt-injection text were found.
What the check found
Nothing above the low level.
Keep an eye on it
This check is of one commit. Watch video-director and we'll email you if a later commit changes what it can touch.
Made this? Add the badge
[](https://plugsday.com/tools/win4r-video-director)About this check
Checked November 2, 2026 at commit 4747e5c15350, 59 files. Rules for known red flags, then two Claude reviews, one of them told to assume the author is malicious. A later commit hasn't been checked. How checks work.