diffusionstudio / lottie

That one skill is a thin router into eighteen separate reference files rather than one long instruction sheet: a player contract and a Lottie JSON spec map, taste guides for design and motion, and recipe files for specific jobs — logos, typography and text reveals, lower thirds, loaders and icons, UI microinteractions, SVG-to-Lottie conversion, camera and scene motion, technical diagrams, data and stat animations, and product promos. The skill loads only the one or two references that match the request instead of the whole library, and its own instructions say to verify every result in the real player rather than building a substitute viewer.

That verification step is the thing to plan around: the deliverable is "a renderable scene in the player, not isolated JSON," so the agent is expected to be working inside a checkout of this Bun/Vite project with its bundled player running, watching public/projects/<project>/<scene>/lottie.json update live. Nothing here needs an account or a paid API — dependency review classed it as a local tool with no credentials required.

READ THE FULL ANALYSIS＋

What happens after generation is on you, not the skill. The README documents how to drop a finished Lottie file into plain web pages, React Native through Skia's Skottie module, iOS, Android, and Flutter — all standard consumption of an ordinary Lottie JSON file. None of that is part of what the skill does; it stops at producing and verifying the animation inside its own player.

Who this fits. Someone already running a coding agent that can open a real project and a dev server, asking for a specific animation — a logo reveal, a loading spinner, a chart — rather than someone who wants a bare JSON snippet handed back with no way to preview it.