How the Asset Library works

What is on it

Parts for making video with code. Each one is a kind of thing (a Remotion piece, an HTML page that renders to video, a shot recipe, GSAP motion, a three.js scene, a Blender skill, a starter, an agent skill, a tool) and does one job: a title, a lower third, a background that moves. Pick the kind or the job, then open a part for its details.

Ours

Three Remotion pieces we wrote for our own videos. One file each. Read them and try them. Their license is on its way.

Start here

Twenty Remotion pieces we would reach for first.

Remotion pieces

A piece is here when its author says, in a license file, their README or their package file, that you can use it, and when it rendered on our machine. The license covers the code. Pictures, logos and names inside a demo belong to whoever owns them, so swap in your own.

Packs

A pack is one open-source project that we read file by file. Everything in it is listed: every skill, recipe, block and tool. We ran what we could, and each pack says which parts those were. An agent skill is a set of instructions your agent will follow, so each pack also says what it sends off your machine.

No preview yet

Most of what is in a pack has no picture yet. A skill or a recipe is words, and we have not rendered every block. Their name and one line are what there is to go on.

Link only

Some entries are here to learn from. One pack states no license at all. One is AGPL, which asks that anything built on its code be shared the same way. And a few single entries sit inside a project that says the part belongs to someone else. Those get a link and no copy button.

Two licenses underneath

Two licenses sit under many of these, apart from the one on each entry. Remotion is free for individuals and small teams, and a company may need to buy one: remotion.dev/license. GSAP costs nothing, commercial work included, and is not open source: gsap.com/standard-license.