CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lottie-bodymovin

Use when implementing Disney's 12 animation principles with Lottie animations exported from After Effects

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/lottie-bodymovin/SKILL.md

The canonical home for this skill is lottie-bodymovin in calesthio/OpenMontage

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-structured catalog with genuinely executable code for most principles. Its weakest point is the absence of an overall workflow tying AE authoring, export, and runtime control together, along with duplicated playback-speed examples and uninitialized variables in snippets.

Suggestions

Add an overarching workflow section (author in AE with these techniques, export via Bodymovin, then control at runtime with the lottie API) to sequence the two halves of the skill.

Consolidate the setSpeed examples repeated in sections 1, 6, and 9 into the Timing section or the Key Lottie Features list.

Initialize or consistently name the animation instance (e.g., show how 'anim' is obtained from lottie-web or lottie-react) so the runtime snippets are copy-paste ready.

DimensionReasoningScore

Conciseness

The body is terse bullets and code with no padding or explanation of concepts Claude already knows, but setSpeed examples are duplicated across the Squash and Stretch, Slow In and Slow Out, and Timing sections, which could be consolidated.

4 / 5

Actionability

Most guidance is real, executable code (playSegments, goToAndStop, addEventListener, AE expressions) plus a complete lottie-react setup, but snippets use inconsistent, never-initialized variables ('lottie.', 'anim.', 'mainAnim.') so they are not fully copy-paste ready.

4 / 5

Workflow Clarity

Each principle section lists steps, but the skill is a catalog with no overarching sequence (AE authoring, export, then runtime control) and no integration guidance; checkpoints are implicit. No destructive or batch operations exist, so no validation cap applies.

3 / 5

Progressive Disclosure

A single file organized into 14 clear, well-navigable sections with no nested references; however, at roughly 160 lines it exceeds the under-50-line simple-skill exception, and AE-side versus runtime-side material could arguably be split.

4 / 5

Total

15

/

20

Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-targeted description with a clear niche and explicit trigger clause. Its main weaknesses are a single generic action verb rather than a list of concrete capabilities, and a missing 'what' statement separate from the 'when' clause.

Suggestions

State the what separately and concretely, e.g. 'Provides After Effects expressions and runtime API techniques for each of Disney's 12 animation principles. Use when implementing...'.

Add missing trigger synonyms such as 'Bodymovin', '.json animation', or 'web animation' to broaden natural-term coverage.

Mention the split of guidance (AE authoring vs. runtime playback control) so the skill's scope is explicit from the description.

DimensionReasoningScore

Specificity

The description precisely names its domain ('Disney's 12 animation principles with Lottie animations exported from After Effects') but offers only one generic action ('implementing') without listing concrete capabilities such as AE expressions, runtime playback control, or interactivity.

3 / 5

Completeness

An explicit and specific 'Use when...' clause is present, and the what ('implementing Disney's 12 animation principles with Lottie') is embedded in that clause; however, the what is not stated as an independent capability statement, so it falls short of the anchor requiring both clearly and explicitly.

4 / 5

Trigger Term Quality

'Lottie', 'After Effects', and 'animation principles' are natural terms users would say in this domain, but 'Bodymovin' (present in the skill name yet absent from the description) and other synonyms like '.json animation' are missing.

4 / 5

Distinctiveness Conflict Risk

The combination of 'Lottie', 'After Effects', and 'Disney's 12 animation principles' defines a clear niche with distinct triggers and minimal conflict risk with any other skill.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

calesthio/OpenMontage

Path

.claude/skills/lottie-bodymovin/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.