# lottiefiles-animation-review

Diagnoses why an animation differs, fails, or renders poorly, and recommends the next step without editing it (needs LottieFiles Engine tools installed).

Skill by LottieFiles. Category: Testing.

## Install

Project (for this project only):

```sh
npx skills add lottiefiles/creator-agent-plugin --skill lottiefiles-animation-review
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add lottiefiles/creator-agent-plugin --skill lottiefiles-animation-review -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 1. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/lottiefiles/creator-agent-plugin/lottiefiles-animation-review)

## Source

[Open the source](https://github.com/lottiefiles/creator-agent-plugin/tree/HEAD/content/skills/animation-review). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: lottiefiles-animation-review
description: Inspect, review, compare, or diagnose an animation result with installed Engine tools. Use when the user asks why an animation differs, fails, renders poorly, or needs a quality review.
---

# Animation review and diagnosis

Use `engine_docs` to discover the installed Engine contract. Use `engine_document` to inspect, `engine_exec` to render or inspect when the contract requires it, and `engine_job_status` or `engine_job_result` for async work. Read [the contract reference](../../references/tool-contract.md) before a tool call.

1. Inspect the source, result, and reported symptom before you diagnose.
2. Compare the smallest relevant artifact, frame range, or property set.
3. Separate confirmed facts from hypotheses. State the evidence for each finding.
4. Do not change the animation during a review unless the user asks for a fix.
5. If a tool returns an async job, inspect the job result before you report a render or export failure.
6. Recommend the smallest safe next action and identify any missing input.

Do not claim visual correctness from metadata alone. Do not expose private document content in diagnostics.
````

- Previous: [k6-test-planner](https://syn4pse.dev/terminal/k6-test-planner.md)
- Next: [lottiefiles-animation-workflows](https://syn4pse.dev/terminal/lottiefiles-animation-workflows.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
