Remotion publishes a set of agent skills defining best practices for working in Remotion projects, aimed at agents like Claude Code, Codex, Kimi Code and Cursor, and offered as an option when a new Remotion project is created. The notable thing is how they are cut: not one project skill, but several scoped to the problem in front of the agent.
The split is by failure mode rather than by feature list. One skill covers compositions, animations, layout, typography, media elements, effects, audio, fonts and timing. Another covers geographic work — static maps, animated routes and markers, Mapbox, MapLibre, MapTiler, GeoJSON and 3D flyovers with CesiumJS. Another is for when elements are not selectable or editable as expected, which is a symptom rather than a topic. A documentation-search skill fetches any page as Markdown so an agent can look up current API references and component props before implementing, and an upgrade skill handles Remotion, related packages and the installed skills themselves.
Scoping by symptom is what makes retrieval cheap at the moment of need, which is the argument in Genkit adding progressive disclosure for agent skills, and the maintenance problem it creates is the one named in hundreds of agent skills being a lifecycle problem. The skills hub tracks both.
This is product documentation listing skills and their intended use, without measured effects on agent output quality. The condition to watch is whether the skills declare which Remotion versions they were written against, because documentation packaged as a skill goes stale exactly like documentation.