One repo, four posts: how video-director got 369 stars in the packed "Claude makes videos" niche

A Claude Code skill that makes Opus 5.5 act as a director, rendering short videos frame by frame into MP4 with code, plus two QA scripts. It got 9 stars in 369 days, but in this niche that's a modest start: the top peers sit at 10k to 80k stars. Where the stars came from is clear: the author posted four times on X, and an English YouTube roundup brought a second wave. Below: what it is, where the stars came from, who it's competing with, and whether you should build a similar one.

Four posts

In the early hours of Oct 2026 28, the Chinese AI creator "AI超元域" (called win4r on GitHub, 77.9k YouTube subscribers) created the video-director repo. Half an hour later he posted the first tweet on X: "I open-sourced a video production Skill built specifically for Claude Opus 5.5." It got about 40 stars on day one.

Oct 29, second post, different angle: "Finally, no more making videos by gacha pulling."

Oct 31, third post: "Let Claude be the director and shoot videos with code!" with two demos from the README: a hand-drawn floating city slowly colored in (30 seconds), and a 3D little orange figure typing on a computer (16 seconds). That day it gained 114 stars, its biggest day so far. A commenter asked the sharp question underneath: "Does the check step have the model look at rendered frame captures, or just check the code and timeline?"

Nov 5, fourth post, another tone: "Found a super useful open-source project: video-director." It was still his own repo.

By Nov 6 it had 369 stars and 33 forks on GitHub (11-06).

What it is

A skill you install in Claude Code. Say something like "make a 15-second looping release video for our CLI tool" or "make a 30-second narrated explainer on Bloom filters, 16:9", and it has the model first lay out the timeline with numbers, then write HTML, Canvas, Three.js, or Remotion animation code, render frame by frame into MP4, and finally run scripts to check the result, fixing whatever is wrong.

It differs from peers in two main ways:

• It doesn't give you a shot library or a style library. The README's second paragraph says it "deliberately ships no shot library to copy." The author distilled the rules that 8 similar open-source repos (lemo-opuscar, video-shotcraft, claude-motion, animate, and others) each worked out on their own into 13 principles and checkpoints for each stage, with sources in METHODOLOGY.md.
• It lets the model "see" and "hear". qa_video.py measures what the model can't perceive: whether the first frame is black, whether text in the first 3 seconds is big and clear enough, white flashes, whether the picture froze, loop seams, loudness, and silent stretches.

The README also includes a self-test table: with the skill installed versus without, assertions passed 28/28 vs 25/28, and blind-review preference 2 vs 1; version two vs version one, 30/32 vs 26/32 on assertions, and blind-review preference 3 vs 0. The author wrote himself: "each configuration was run only once; treat it as a direction, not a measurement."

Where the stars came from

Lining up daily star counts against posting times shows a close match:

The first four days brought about 190 stars, mostly pushed by the author on X. After 11-02, another hundred-plus stars came in, mainly from that English roundup video. Skill directories like TypingMind, trendshift, and mcpmarket auto-indexed it, and a post on r/claudeskills about "9 animation skills" mentioned it. I found no Hacker News or Product Hunt listing and no separate reshare by a major English account.

The "QA only" angle didn't cause the star growth. Peers in the same period that went with style libraries and plug-and-play use grew 5 to 10 times faster. Its star curve tracks only posting and the roundup video. The differentiation did matter in one way: it let the roundup author write a one-line blurb that didn't duplicate anyone else's, so it got picked for the list.

No updates since version 10-30. On 11-05 someone filed the first issue, pointing out a bug in the loudness check of qa_video.py: when the true peak is exactly 0.0 dBTP, Python treats it as "no value," so a file that should be flagged for clipping passes instead. On 11-06, someone also submitted a Japanese README. People are using it, but not many.

Who it's competing with

"Have a coding agent write animation code and render it into MP4" has been a category since HeyGen open-sourced HyperFrames in 2026 March. After Opus 5.5 launched, making videos became its showcase demo, and similar skills clustered in 9 and October. A list called awesome-claude-video-skills already collects 180 repos. Star counts around 11-06:

By stars, it ranks middle-to-low among its peers. I found no copycat repos following it; if anything, it's itself a "distilled version" of the peer repos.

What the author has

Whether you can follow this depends partly on what's here. win4r has 23 repos with about 10k stars combined; the top two are AISuperDomain (1,995) and ClawTeam-OpenClaw (1,471). 1,954 GitHub followers, 77.9k YouTube subscribers, and the same name on Bilibili. His usual pattern is building a Claude / OpenClaw-related tool and promoting it on his own channel and X, and most of his repos stop gaining stars soon after.

In other words, 369 stars roughly equals what "a Chinese big creator seriously builds one repo in a saturated niche and posts it four times" gets. Someone without this audience copying the approach won't get that first wave.

If it were you

Grade C: you can learn two moves, but building another video skill in this niche isn't worth it. There are over a hundred of them, the top ones got a head start of months, and even the author only got three hundred-plus stars from four posts.

Good fit for: AI tool creators with a few thousand followers who want another open-source project in their portfolio, or developers with a mature video/animation workflow who will seriously build measurement scripts and comparison tests.

Bad fit for: people with no posting channels hoping to get their first stars from "yet another Claude video skill"; people who can only write prompts and can't build check scripts that produce real numbers.

How to do it: don't make a content library, make a meta-layer. Pick a niche already crowded with skills (not necessarily video; it could be slide decks, landing pages, or data charts), distill the rules that 5 to 10 top repos each worked out into a sourced methodology, then write scripts to measure what the model can't see, and pair it with a with-vs-without comparison table. That way you don't have to compete with the leaders on style count, and you can still claim a spot in the roundups. Its own gaps are also an opening: 10-30 it has stopped updating, the scripts have known bugs, and it doesn't cover vertical short-video platform details or evaluation of character animation. But a successor relying on continuous updates to accumulate stars won't move fast.

How to get users: copy its posting rhythm. One repo, three or four posts, a different hook each time ("no more gacha pulling," "let AI be the director," "found a great project"). Put a directly playable GIF at the top of the README, since that becomes your post material. If you have no audience, the more effective step is sending the repo to the English YouTube and Medium authors who make "N GitHub repos" roundups; that's where its second wave came from. Also prepare the metadata once so skill directories can auto-index it.

When to move: the video niche has already passed its peak. Taking the "distill + QA" move to another niche works best while that niche's top skills have just appeared and roundup authors are still looking for "the different one." That's usually within one or two months after the leaders launch.

Signs you misjudged: ① It or similar QA/review-route repos like motion-video-kit see daily star gains back above 50 before December, which would show the "meta-layer" itself has demand, not just roundup spillover; ② a same-niche skill launched after it, with no big creator promoting it, passes a thousand stars within a month, which would show the niche isn't saturated yet; ③ Remotion or HyperFrames officially builds finished-video QA into the framework, and then the "meta-layer" position is gone.

Data and sources

• Repo, README, issues: github.com/win4r/video-director (GitHub, 11-06:369 stars, 33 forks, last commit 10-30).
• Daily star counts: day-by-day records from 10-29 to 11-06.
• X: @AISuperDomain posts 10-28, 10-29, 10-31, 11-05; post views and likes not obtained.
• AI LABS video: youtube.com/watch?v=oTWUyW_bR-g, published 11-02, about 11-06k views as of 87.
• Competitor star counts: each repo's GitHub page, around 11-06.
• Whether the author separately covered this repo on Bilibili, WeChat Official Account, or his own YouTube is unverified; actual usage can't be determined.