CtrlK
BlogDocsLog inGet started
Tessl Logo

lottie-bodymovin

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

49

Quality

53%

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 ./.agents/skills/lottie-bodymovin/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is a well-organized, mostly lean reference catalog of the 12 principles with many concrete code snippets, but it mixes the imperative 'anim' API with a React component example without bridging them, repeats a few snippets, and keeps all content inline with no progressive disclosure to bundle files.

Suggestions

Bridge the API styles by showing how to obtain the imperative 'anim' (e.g., lottie.loadAnimation) or how to get the animation instance from the React <Lottie> component, so the setSpeed/playSegments/goToAndStop examples are fully copy-paste ready.

De-duplicate the repeated setSpeed guidance into one 'Controlling playback timing' reference instead of restating it in Squash, Slow In/Out, and Timing.

Move the longer After-Effects-side setup details (e.g., the Overshoot expression, 3D/Solid Drawing steps) into a references/ file and link to it from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is largely lean bullets and code with no padding about what Lottie is, but 'setSpeed' is repeated across the Squash, Slow In/Out, and Timing sections and a few sections (Appeal, Solid Drawing) carry generic conceptual bullets, matching the 'mostly efficient but could be tightened' anchor rather than the 'every token earns its place' level.

2 / 3

Actionability

Many concrete executable snippets appear (e.g., 'anim.playSegments([0, 10], true)', 'anim.setSpeed(0.5)'), but the imperative 'anim' object is never shown being obtained and the React '<Lottie>' implementation example does not bridge to it, so examples are not fully copy-paste ready — matching the 'concrete guidance but incomplete; missing key details' anchor.

2 / 3

Workflow Clarity

Content is organized as numbered principles 1–12 plus an implementation section, giving topic sequence, but there is no end-to-end workflow with validation checkpoints or feedback loops, matching the 'steps listed but checkpoints missing' anchor rather than the level-3 explicit-validation example.

2 / 3

Progressive Disclosure

Sections are well-organized, but everything lives inline in a single ~140-line SKILL.md with no references, scripts, or assets to offload detail, matching the 'some structure but content that should be separate is inline' anchor; it is not level 1 because it is organized rather than a monolithic wall of text.

2 / 3

Total

8

/

12

Passed

Description

57%

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

The description targets a clear, distinctive niche with natural trigger terms and an explicit 'Use when' clause, but it states only a single bundled action and folds the 'what' into the 'when', leaving the capability description thin.

Suggestions

Lead with a concise capability clause (e.g., 'Implement all 12 Disney animation principles as Lottie/Bodymovin vector animations from After Effects.') before the 'Use when ...' trigger so 'what' and 'when' are both explicit.

Add common trigger variations such as 'Bodymovin', 'vector animations', and 'AE animation export' so the description matches more natural phrasings.

List two or three concrete actions (e.g., 'author squash/stretch and anticipation, control playback timing, layer interactive scenes') to raise specificity from a single bundled verb to multiple concrete capabilities.

DimensionReasoningScore

Specificity

Quotes 'implementing Disney's 12 animation principles with Lottie animations exported from After Effects' — it names the domain and tool but bundles a single action verb rather than listing multiple concrete capabilities, matching the 'names domain and some actions, but not comprehensive' anchor and falling short of the 'lists multiple specific concrete actions' level above.

2 / 3

Completeness

An explicit 'Use when ...' trigger is present, but the 'what does this do' capability is only embedded inside that fused clause rather than stated as a clear standalone capability, so it does not reach the 'clearly answers both what AND when' level.

2 / 3

Trigger Term Quality

Natural terms like 'Lottie animations' and 'After Effects' are present, but common variations a user might say such as 'Bodymovin' and 'vector animations' are absent, matching the 'some relevant keywords but missing common variations' anchor rather than the full-coverage level above.

2 / 3

Distinctiveness Conflict Risk

The niche of 'Disney's 12 animation principles with Lottie animations exported from After Effects' is specific and unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor; it is not level 2 because the trigger is highly domain-specific rather than broadly overlapping.

3 / 3

Total

9

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
calesthio/OpenMontage
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.