CLAUDE VIDEO SKILLS

With Claude Opus 5.5, a short motion-graphics clip usually needs nothing but a good prompt: of the 330 videos in our index, only 7 creators named a skill or render framework. Most of the skills below were written for earlier models, and 168 of them predate Opus 5.5. They still matter in three places: when timing has to be frame-exact (a render framework), when the video is long or narrated (a pipeline that handles script, voice and captions), and when you're working with footage you already have (editing skills).

A skill is a folder of instructions and scripts that a coding agent loads when a task calls for it. For video, that usually means three things: how to structure a composition, how to render it to MP4, and the house style: which easing curves to use, how long a title should hold, how big captions should be. Without a skill, Claude improvises all three every time. With one, it follows a playbook.

The 180 repositories here range from full rendering frameworks with tens of thousands of stars to single-purpose skills that do one thing, like adding captions or cutting silence. Most target Claude Code; many also work with Codex and other agents that read the same skill format.

WHERE TO START

If you want Claude to make motion graphics or a launch video from scratch, start with a rendering framework and its official skill: HyperFrames if you want Claude to write HTML and CSS, Remotion if you'd rather it write React. The all-in-one kits in Frameworks & toolkits bundle scripting, voiceover and rendering into one pipeline if you want everything wired up for you.

If you already have footage, look at Editing: these skills drive FFmpeg or an editor to cut, caption and add B-roll. For vertical social video, Shorts & social has skills tuned for 9:16 pacing and on-screen captions.

HOW THIS LIST IS BUILT

The list of repositories comes from the community-maintained awesome-claude-video-skills list, which is dedicated to the public domain. We refresh each repo's stars, language, license and last commit from the GitHub API, and write the one-line and short summaries ourselves from each project's own README.

We haven't installed and tested every entry. Read a project's README and code before giving an agent the permissions it asks for.

ATTRIBUTION

Every project belongs to its authors and links to its repository. Descriptions quoted from GitHub belong to their authors; our summaries are our own. Repository list: awesome-claude-video-skills (CC0 1.0).