The same repo was posted twice, and each time it gained over a thousand stars: Scenario's "open-sourced an entire 3D studio"

On Oct 30, the CEO of AI game art company Scenario posted on X: "We just open-sourced an entire 3D studio." The repo this post promoted had already been promoted a month earlier with the claim "open-sourced an entire game studio." After the two posts, stars jumped considerably both times: the first time from 22 to over 900, the second from 1,193 to over 3,000, and it's still accelerating. Below: what it is, where the stars came from, who else is doing the same thing, and what you can borrow if you want your own open-source project to grow this way, and what you can't.

A studio drawn as a tree of folders

Oct 30 15:21 (UTC), Emm (@emmanuel_2m, Scenario CEO, about 62K followers on X) posted, opening with: "We just open-sourced an entire 3D studio." Then came a directory tree drawn with 📁 icons: animation, art, modeling, materials and lighting, scenes, pipeline. Six "departments," each with two very specific-sounding roles, such as "rig any character," "motion from a video," "retopology and UV baking," "export game-ready assets." The bottom layer was "expert tools": Blender, Maya, ZBrush, Unreal, Unity, Godot, Roblox. A demo video was attached, and the last line was:

Comment "3D" and I'll send you the GitHub repo.

—comment "3D" and I'll DM you the repo link.

The main post contained no link. To get the link you had to comment, and the more comments, the further the algorithm pushed it. According to the third-party site artrealmai, within 10 hours the post had 62K views and 2,300 bookmarks (secondhand from the third-party site, not verified).

Scrolling back, on Sep 24 Emm had posted an almost identical line: "We just open-sourced an entire game studio. Introducing GameDev OS." Nine "roles"—2D art, 3D art, environment art, art director, sound, video, marketing art, technical director, cost management—ending with "Comment "OS"." The repo was the same: scenario-labs/skills.

What it actually is

An Agent Skills collection. Install it into Claude Code, Codex, or Cursor with a single npx skills add scenario-labs/skills. It splits into two halves:

• Generation skills (about 80 of them): let the agent generate images, video, audio, and 3D models. It picks the model, quotes the price before spending, and keeps the same character and brand looking consistent across every image. This half runs entirely through Scenario's own MCP service and requires an account and credits.
• Expert tools: seven software families, each with "one main skill + 8 to 14 expert skills," operating directly on Blender, Unity, Godot, and others on your machine via each software's scripting interface or MCP bridge. This half does not require a Scenario account.

MIT license, 60+ releases, with CI and security-score badges. Overall it looks like a serious piece of engineering rather than a demo.

Put plainly: this is a company using a free open-source front door to acquire customers for its paid generation service. The open half makes people willing to install and bookmark; the paid half sits at the most-used "generate" step.

Where the stars came from

First, the curve (GitHub, daily stars):

In the last 7 days it gained 1,748, while the 7 days before that gained only 106. The latest version is a bug-fix release from 10-29. This wave had nothing to do with code updates; it was all driven by posts. The fork-to-star ratio is about 9%, similar to new repos of this size, so no sign of star farming.

A few specific channels:

The CEO's own account and a fixed template. Emm has been writing long X posts about "AI game art workflows" since 2022, with 62K followers who are essentially game and 3D practitioners. The same template used twice, and both times it matched a jump.

Big-account reshares. Stability AI founder Emad Mostaque reshared it; Digg's AI hot page listed it with Robert Scoble as a source; Chinese AI news accounts also passed it along attributed to Scoble.

Brand account reposts with the link a few days later. 11-02 @Scenario_gg reposted, and it hit the trending chart the same day.

Spread across platforms. LinkedIn (employees resharing), Instagram Reels, YouTube Shorts, and Threads all had people relaying it in ranking-list format. After that came a cluster of aggregator sites that auto-generate articles from trending charts and hot X posts.

The trending chart spreads it on its own. After 11-02 made the chart, daily gains went from over a hundred to over six hundred. Much of the later growth likely came from the trending chart itself (an inference; no hourly breakdown is available).

What didn't work: Skills directory sites mostly indexed it, one showing "3 installs, 63 views"; Reddit had a few scattered posts, and no hot thread on HN turned up.

One detail is telling: in the September wave, the repo was only 40+ days old, it rose to 900+ and then stopped, never making the trending chart. In the late-October wave, the repo was already 80 days old, and once the X buzz connected to the trending chart, it was amplified a second time. (Inference: GitHub's trending chart is not very friendly to very new repos, though there is no official statement on this outside.)

Who else is doing the same thing

"Having an agent operate Blender" was already done by others; single tools have reached 33K stars. Scenario didn't create a new capability; what it did was packaging: chaining generation, modeling, retopology, rigging, and export into one pipeline, named by "department."

The most telling row in this table is the fourth: a community collection with no company and no CEO megaphone also gained 1,329+ the same week. Vertical skills for game development already have real demand.

Why this one

• Narrative: "Behind one agent sits an entire studio." By 2026 everyone was installing skills, but most skills were individual tools; drawing them as an org chart let readers see at a glance "what I can do if I install this." artrealmai's take: most AI game tools stop at the image-generation box, while this one also covers the tedious middle steps—retopology, UVs, rigging, export presets.
• Volume that looks substantial: 80+ skills, 7 software families, 60+ versions. The urge to bookmark comes from "save it now, you'll need it someday."
• Not all ads: the expert-tools half works without signing up, which lowers resistance to "this is just a sales pitch."
• Distribution: this is the main factor. The same repo under a different name, with a different directory tree, posted again, can spark another wave. The stars were mainly driven by the narrative and the CEO's account, not by organic spread after people used it.

If it were you

Verdict: building an "open-source 3D studio" yourself makes little sense. Half its stars came from Scenario's own accounts and reshares by Emad and Scoble-type figures, which you won't get; and single tools for Blender or Unity are already taken. What's worth copying is the packaging: organize a bunch of skills into a vertical "studio" by "department / role," and do it for an industry or ecosystem it doesn't cover.

Who it fits: developers who work in a specific industry and know its real workflows: video editing, e-commerce product pages, short dramas, indie games, architectural visualization. Or people fluent in the Chinese toolchain: Cocos, WeChat mini games, Jianying, and domestic models like Kling, Jimeng, Hunyuan 3D, and Tripo (I haven't seen anyone doing this, so I'm guessing it's still an open gap).

Who it doesn't suit: people with no audience who aren't willing to spend two or three weeks posting consistently; people who want to repackage generic skills again (the official library already has 187K stars).

How to do it:

• Pick one industry, map its real roles, and build 2 to 3 skills per role that actually run end to end. Better few and usable than padding to 80 empty shells.
• At least half the skills should work without depending on any paid service, so they're usable right after install.
• Put the 📁 directory tree and a 30-second demo video on the first screen of the README, plus a one-line install command.
• Ship release automation and CI so the version number keeps climbing and the repo looks actively maintained, which it is.

How to get it seen:

• Copy its template on X directly: "We just open-sourced an entire ___ studio" + a directory tree + a video. Comment-for-link works poorly when you have few followers. Instead, leave the link out of the main post and put it in the first reply.
• In Chinese-speaking circles, post to Jike, V2EX, and Xiaohongshu AI-tool topics. In English, post to X and to the relevant industry subreddits. The official community and user group of whatever software your skills operate is the most accurate audience.
• Let the repo sit for a while before the big post, gathering some stars, and wait a month or two so the attention lines up with trending charts. A small soft launch in between works as a test run, which is exactly the role Scenario's first wave played.
• A month later, change the theme (a new set of "departments") and post again. The same repo can be harvested more than once.

Window: from now until year-end. Agent skills are still at peak heat, and the "vertical studio" framing hasn't been copied to death yet. Once every industry has someone posting "we open-sourced an entire ___ studio," the headline stops working.

Signs you're reading it wrong: two posts in, stars stall at a hundred or two and nobody reshares. That means the people in your niche don't use coding agents, or your account can't reach them. Or a pile of same-named, same-template repos show up within a month, the headline is worn out, and you need a new narrative.