The Motion Skills standard
Every skill in the library clears the same bar before it's listed. This page is that bar, written down so you can hold us to it.
1. Every skill does a job you have
The library is built around jobs: turn a project into a launch video, notes into an explainer, a spreadsheet into a data video, a script into a short, a document into a narrated deck. Workflow skills do those jobs end to end. Shots and styles exist to serve them, and each one says where it fits. We don't list effects for their own sake.
2. A finished video comes first
We start from a result we'd publish ourselves, then write the instructions and templates that let an agent make it again. Every preview is a real render: a template's own output, or a workflow run on sample material. Previews are rendered from the same download you get, from its own example, and rendered again whenever the template changes.
3. One idea per shot
Each shot says one thing. It builds in, makes its point and settles on a clean final frame, so it cuts straight into a longer video.
4. Motion with restraint
Eased movement, staggered entrances and a clear order of attention. Motion points at the content instead of competing with it, and nothing moves just to look busy.
5. Type and color as a system
Every template draws on one shared kit of fonts and easing, so skills look like they belong together. Colors come from five tested themes, and you can set your own accent, background and text color, or set your brand once and every skill uses it. Chinese, Japanese and Korean text works out of the box.
6. Built for every format it lists
When a skill lists 16:9, 9:16 and 1:1, the layout is designed for each one. It reflows rather than shrinking a landscape frame into a vertical one.
7. One install, nothing else to pay for
A skill runs with Node.js, FFmpeg and Chrome on your own computer. No API keys, no credits, no accounts with other services and no extra licenses. Your material and your data stay on your machine.
8. Checked before it's listed, rechecked when things change
Before a skill goes live we render it and review frames at the key moments. Templates also pass the HyperFrames check (lint, runtime, layout, motion and contrast) in all five themes and every format they list. Workflows are tested end to end on sample material of the kind they take: an article, a code repository, a spreadsheet, a short script or a talking-head clip. The final question is always the same: could this video be posted without changes? Each skill page shows the date of its latest check. Every listed skill is also tested the way you get it: unzipped from its download and run through its own SKILL.md example and gates.
We also score each skill from 1 to 5 on visual quality, stability and how easy it is to customize. A skill needs at least a 4 on visual quality and stability to be listed.
9. Your agent checks its work, and never makes things up
Every SKILL.md tells your agent to look at its own frames before the final render and fix what's cut off or crowded; the director workflows show you a storyboard to approve first. Numbers, quotes, names and claims come from your material only; when something can't be sourced, the agent says so instead of inventing it. Three gates back that up: the HyperFrames check, a layout check (text inside the frame, not cut off, covered or printed over other text) and a pixel check on the rendered video. Each scene also runs as long as its words need, about 0.3 seconds a word, measured rather than guessed.
10. Honest credits and clear limits
When a skill adapts open-source code, the page names the project and its license ships in the download. When a template only learned from a project, we say that instead. A skill can take after a well-known style, but templates never ship another company's logo or trademarked assets, or a pixel-for-pixel copy of a real app's interface. Every skill page also says what the skill is not for, and points to a better skill when there is one.
Questions, or a skill that doesn't meet this bar? Write to hi@claude-motion.com.