Skip to content
Back to search

video-director

SkillWorks with Claude CodeGitHub

A Claude skill for directing, building and verifying code-rendered videos (HTML/Canvas → MP4): principles, gated workflow, QA scripts and evals.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/win4r--video-director/badge.svg)](/listings/win4r--video-director)

HTML

<a href="/listings/win4r--video-director"><img src="/api/listings/win4r--video-director/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

In Claude Code, select **Claude Opus 5.5** and copy the skill folder into your personal skills (or into a project's `.claude/skills/`):

git clone https://github.com/win4r/video-director.git
cp -R video-director/video-director ~/.claude/skills/

In the Claude apps, zip the inner `video-director/` folder and upload it as a custom skill.

The scripts need `ffmpeg`/`ffprobe` and Python 3 with `numpy` and `Pillow`. Rendering HTML films needs Node with Playwright and Chromium (or use Remotion). `faster-whisper` is optional, for checking narration, and any text-to-speech works for voice.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 104 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # [🚀Bilibili profile](https://space.bilibili.com/3493277319825652)
  2. # [🚀Watch the video on Bilibili](https://www.bilibili.com/video/BV1bQ4n6GENf/)
  3. # video-director
  4. **Primary model: Claude Opus 5.5 · For Claude Code**
  5. **English** | [简体中文](README.zh-CN.md) | [日本語](README.ja.md)
  6. **video-director is built primarily for Claude Opus 5.5 in Claude Code.** It guides the model to create short videos as code (HTML, Canvas, SVG, Three.js, GSAP or Remotion), rendered frame by frame to MP4. It covers launch films, promos, explainers, data stories, kinetic type, character and illustrated shorts, loops and social reels.
  7. The skill treats **Claude Opus 5.5** as the director and coding agent: plan the film in numbers, build it deterministically, then measure what it can't watch or hear. It holds principles with their reasons, a workflow with a gate at each phase, and two QA scripts. It deliberately ships no shot library to copy.
  8. ## Animation demo
  9. ### Hand-drawn city
  10. [![Animation demo: a hand-drawn floating city comes to life in color](assets/demo.gif)](assets/demo.mp4)
  11. [Watch the original MP4 (30 seconds, 720 × 720, 60 fps)](assets/demo.mp4)
  12. ### 3D character animation
  13. [![3D character animation: a small orange character working at a laptop](assets/character-demo.gif)](assets/character-demo.mp4)
  14. [Watch the original MP4 with audio (16 seconds, 1920 × 1080, 24 fps)](assets/character-demo.mp4)
  15. ## What's inside
  16. | Path | What it is |
  17. |---|---|
  18. | [`video-director/SKILL.md`](video-director/SKILL.md) | The stance, the per-film dials (clock, continuity, register, text policy), 13 principles, the build contract, the brief structure and the definition of done |
  19. | [`video-director/references/`](video-director/references/) | Templates (treatment, timeline, facts, delivery report), craft numbers, sound, the QA catalogue and critic rubric |
  20. | [`video-director/scripts/`](video-director/scripts/) | `check_timeline.py` validates the plan before any code; `qa_video.py` measures the render: hook text size and contrast, frame 0, flashes, cuts, freezes, loop seam, loudness, silences, contact sheets |
  21. | [`video-director/evals/`](video-director/evals/) | Three test briefs with graders |
  22. | [`METHODOLOGY.md`](METHODOLOGY.md) | The research the skill was distilled from: what drives quality across eight public repositories |
  23. ## Recommended model: Claude Opus 5.5
  24. **Recommended setup: Claude Code with Claude Opus 5.5 selected.** Give Opus 5.5 a video brief; the skill guides it through planning, writing the animation code, rendering, checking the result and revising specific defects. Other capable coding agents can also follow the workflow, but **Claude Opus 5.5 is the primary intended model**.
  25. This is an instruction-and-QA skill, not a bundled model or hosted video-generation service. Its output still depends on the available code execution and rendering tools.
  26. ## Install
  27. In Claude Code, select **Claude Opus 5.5** and copy the skill folder into your personal skills (or into a project's `.claude/skills/`):
  28. ```bash
  29. git clone https://github.com/win4r/video-director.git
  30. ```
  31. ```bash
  32. cp -R video-director/video-director ~/.claude/skills/
  33. ```
  34. In the Claude apps, zip the inner `video-director/` folder and upload it as a custom skill.
  35. The scripts need `ffmpeg`/`ffprobe` and Python 3 with `numpy` and `Pillow`. Rendering HTML films needs Node with Playwright and Chromium (or use Remotion). `faster-whisper` is optional, for checking narration, and any text-to-speech works for voice.
  36. ## Use
  37. With **Claude Opus 5.5** selected in Claude Code, ask for a video in plain words; the skill is designed to respond even to a one-liner:
  38. - "Make a 15 second looping launch video for our CLI. Everything you need is in the README."
  39. - "I need a ~30 second narrated explainer on how a bloom filter works, 16:9."
  40. - "A 20-second Reel from subscribers.csv for our public account. Keep it honest."
  41. It also reviews and fixes existing coded videos ("this feels slow", "the text is unreadable"). You can run the checks yourself:
  42. ```bash
  43. python3 video-director/scripts/check_timeline.py timeline.json
  44. ```
  45. ```bash
  46. python3 video-director/scripts/qa_video.py film.mp4 --out qa/ --beats timeline.json
  47. ```
  48. ## Eval results
  49. Each round ran the three briefs once per configuration. Script checks graded the measurable assertions; blind graders that didn't know which run was which graded the rest and picked the film they'd post.
  50. | Round | Compared | Assertions passed | Blind preference | Cost |
  51. |---|---|---|---|---|
  52. | 1 | Skill vs no skill | 28/28 vs 25/28 | 2–1 for the skill | about 2× the time and tokens |
  53. | 2 | Current skill vs round-1 skill | 30/32 vs 26/32 | 3–0 for the current skill | about the same |
  54. Round 1 showed the skill catching craft basics (a black first frame, text under the Reels caption, quiet audio). It also showed two gaps: a tagline held back until 11 s, and an explainer that never said "false positive". Round 2 added the rules that fixed them. The hook and any call to action are on screen by 3 s with the sound off, at measured size and contrast. The terms the audience searches for are said and shown. Labels never sit on numbers that are still counting. With one run per configuration, treat these as a direction, not a measurement. The guidance for character and illustrated films, revisions and live pages was added after round 2 and hasn't been evaluated yet. These results do not establish a controlled comparison of Claude Opus 5.5 against other models.
  55. ## Development
  56. The tests build their own films with ffmpeg, then check both scripts and the skill's documents. CI runs them on every pull request.
  57. ```bash
  58. pip install numpy Pillow pytest
  59. ```
  60. ```bash
  61. pytest -q
  62. ```
  63. ## License
  64. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.