Text To LottieSAFE
Generate production-ready Lottie animations with Claude Code or Codex
Overview
Generate production-ready Lottie animations with Claude Code or Codex
cfeec3b72e1dOBSERVED · 2026-10-20Install
Commands as the repository documents them. They are shown, not run.
npm install
Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| cursor | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: text-to-lottie description: Create, edit, or fix Lottie/Bodymovin JSON animations for the local Skia Skottie player. Use for text-to-Lottie, SVG/logo/type animation, loaders/icons, state feedback, UI microinteractions, lower thirds, diagrams, data/stat/chart animations, product promos, scene/camera motion, visual effects, scene edits, slots/controls, and Skottie debugging. --- # Text To Lottie Author production-ready Lottie JSON for the official local Skia Skottie player. The deliverable is a renderable scene in the player, not isolated JSON. ## Operating Model - Use the official player project and verify in Skia Skottie. Do not hand-roll a custom viewer or switch renderers for verification. - Keep the skill portable across Agent Skills clients. Avoid host-specific commands, command modes, or orchestration conventions in skill instructions. - Prefer fewer questions and stronger defaults. Ask only when a decision changes the output materially, such as transparent vs full-frame background, brand constraints, target format, or supplied source assets. - Prioritize clean, intentional, professional motion over merely satisfying the literal prompt. ## Reference Loading This `SKILL.md` is the thin control plane. Load only one-level references that match the task. Do not open the whole reference library. Always read `references/player-contract.md` before creating, editing, fixing, or verifying a scene. If a routed reference is unavailable, continue using the inline rules in this file. | User intent | References to read when present | | --- | --- | | Any new/edit/fix Lottie scene | `references/player-contract.md` | | JSON structure, keyframes, slots, shapes, assets | `references/lottie-spec-map.md` | | Logo animation | `references/recipe-logo.md`, `references/motion-taste.md`, `references/design-taste.md` | | Typography, title, quote, text reveal | `references/recipe-typography.md`, `references/design-taste.md`, `references/motion-taste.md` | | Lower third, name tag, caption bar, overlay | `references/recipe-lower-thirds.md`, `references/design-taste.md`, `references/motion-taste.md` | | Loader, icon, spinner, badge animation | `references/recipe-loaders-icons.md`, `references/motion-taste.md` | | Success, error, warning, completion, empty state | `references/recipe-loaders-icons.md`, `references/design-taste.md`, `references/motion-taste.md` | | UI microinteraction | `references/recipe-ui-microinteractions.md`, `references/design-taste.md`, `references/motion-taste.md` | | Generic "animate this SVG" or SVG-to-Lottie | `references/recipe-svg-animation.md`, `references/svg-compatibility.md`, `references/motion-taste.md` | | Camera follow, pan, zoom, parallax, scene motion | `references/recipe-camera-scene-motion.md`, `references/design-taste.md`, `references/motion-taste.md` | | Diagram, technical line animation, callout, flow trace | `references/recipe-diagram-technical.md`, `references/design-taste.md`, `references/motion-taste.md` | | Data, stats, KPIs, charts, metrics, dashboard figures | `references/recipe-data-stats.md`, `references/design-taste.md`, `references/motion-taste.md` | | Product launch, feature announcement, social promo | `references/recipe-product-promo.md`, `references/design-taste.md`, `references/motion-taste.md` | | Long text, multiple ideas, list/features/steps, timeline, before/after, problem/solution, quote+proof, recap/story, product walkthrough, multi-language variations, chapters, multi-beat sequence, episode, jump/hard cuts, transition grammar | `references/chapterization-transition-grammar.md`, `references/motion-taste.md` | | Glow, glass, metal, gradient, fill, bubble/burst effects | `references/recipe-visual-effects.md`, `references/design-taste.md`, `references/motion-taste.md` | | SVG input inside logo/icon/UI/lower-third work | The task recipe plus `references/svg-compatibility.md` | | Starter brief or reusable project direction | `references/recipe-starter-projects.md`, `references/design-taste.md`, `references/motion-taste.md` | | Any "premium", "clean", "minimal", "modern", "sleek", or "polished" qualifier | `references/design-taste.md` (restraint defaults), plus the routed recipe | For mixed prompts, choose one primary recipe from the main deliverable, then add secondary references for source format or visual treatment. Examples: SVG logo with glow uses logo as primary plus SVG compatibility and visual effects; product launch with pan/zoom uses product promo plus camera scene motion; technical SVG diagram tracing uses diagram/technical plus SVG compatibility; kinetic title with glass sweep uses typography plus visual effects. ## Workflow 1. Route the task using the table above. Read only the relevant references that exist. 2. Locate the official player project and resolve the target scene using the target precedence below. Before editing, verify the resolved path is `public/projects/<project>/<scene-N>/lottie.json`; re-read that current file immediately before overwriting because the UI can write slot edits back to source. 3. Decide the background policy before authoring. 4. Write or update `public/projects/<project>/<scene-N>/lottie.json` and, when useful, `controls.json`. 5. Validate JSON, run or reuse the dev server, inspect exact frames with `?frame=N`, and fix render/design/motion issues before finishing. ## Inline Rules ### Design Defaults (always apply) These few defaults are non-negotiable and apply to every designed scene. Load `references/design-taste.md` for the full reasoning, especially for any "premium", "clean", "minimal", "modern", or "card" prompt. - Premium means subtract, not add. When a prompt says premium, clean, minimal, modern, sleek, or sophisticated, default to restraint: remove chrome before adding it. Premium is carried by scale, weight, brightness, spacing, and timing, never by cards, borders, dividers, shadows, glow, or stacked tints. - Chrome/container budget is `0` b
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
cfeec3b72e1dfull audit observations/trust-audit/skill/diffusionstudio__text-to-lottie.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-20 | cfeec3b72e1d | SAFE | B | 89 | first audit |
Questions
What does the text-to-lottie — diffusionstudio/lottie skill do?
Generate production-ready Lottie animations with Claude Code or Codex
Is text-to-lottie — diffusionstudio/lottie safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can text-to-lottie — diffusionstudio/lottie access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does text-to-lottie — diffusionstudio/lottie work with?
Its documentation mentions cursor. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (cfeec3b72e1d), read on 2026-10-20. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/diffusionstudio/text-to-lottie/)
Not your listing, or something out of date? Claim or update your listing.