CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lottie

Expert guidelines for implementing performant Lottie animations on the web

Quality

68%

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

Quality

Content

75%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.

The body is a well-organized, code-first reference: executable examples cover the common React cases, performance and accessibility guidance is concrete, and structure is clear throughout. The main improvement opportunities are trimming the redundant Best Practices Summary, completing imports in the later snippets, and splitting some full worked examples into reference files to shorten SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean: terse bullets and code with no padding explaining what Lottie is or how libraries work. Minor trims remain — the "You are an expert in..." preamble and the 10-item "Best Practices Summary" that restates every preceding section. Not 5 due to that duplicated summary; not 3 since nearly every other token earns its place.

4 / 5

Actionability

Concrete install commands and copy-paste-ready TSX for the common cases: basic usage, playback control, lazy loading with IntersectionObserver, hover mode, reduced-motion fallback, error fallback, preloader, and cleanup. Minor gaps: later snippets (SegmentAnimation, AnimationWithFallback, ScrollLottie) omit imports and use untyped props, keeping it below the fully-executable anchor 5.

4 / 5

Workflow Clarity

Sections are thematically sequenced (format → install → usage → performance → interactivity → accessibility → loading → size → cleanup) and each topic's guidance is unambiguous, with error handling (onError), reduced-motion checks, and unmount cleanup present as checkpoints. Not 5: no explicit end-to-end implementation sequence with validation steps; not 3: checkpoints are present, not missing or merely implicit.

4 / 5

Progressive Disclosure

Scored against the actual bundle: a single SKILL.md with no reference files, all content inline in one well-sectioned document with clear headers and easy navigation. The ~300 lines are on the long side — full interactivity and accessibility component examples could live in reference files — but placement and structure are good, matching anchor 4 rather than 5 (the under-50-lines simple-skill exception does not apply) or 3 (structure is more than 'some').

4 / 5

Total

16

/

20

Passed

Description

48%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.

The description identifies a clear niche (Lottie animations on the web) but is a single generic phrase: it lists no concrete capabilities, includes no explicit "Use when..." trigger guidance, and omits common trigger variations like dotLottie or .lottie. It is serviceable but well below the quality of the reference good examples.

Suggestions

List 3-4 concrete capabilities in the description (e.g., 'Render dotLottie animations in React and vanilla JS, control playback, lazy load offscreen animations, and add reduced-motion fallbacks') so the 'what' is specific rather than a restatement of the domain.

Add an explicit trigger clause, e.g. 'Use when the user mentions Lottie, dotLottie, .lottie/.json animation files, lottiefiles.com, or wants animated icons/loaders on the web', to answer 'when should Claude use this' and lift completeness above the cap of 3.

Include natural trigger variations and file extensions (Lottie, dotLottie, .lottie, lottiefiles) so the skill fires on the phrasings users actually say.

DimensionReasoningScore

Specificity

"Expert guidelines for implementing performant Lottie animations on the web" names the domain (Lottie, web, performance) but the only action is the generic "implementing"; no concrete capabilities like playback control, lazy loading, or renderer selection are listed. Anchor 2 ("Names the domain but actions are minimal or generic") fits better than 3, which requires at least 1-2 concrete actions.

2 / 5

Completeness

The "what" is clear (guidelines for performant Lottie implementation on the web), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4, since the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"Lottie animations" and "the web" are natural terms users would say, but common variations are missing: dotLottie, .lottie, lottiefiles, or animation-related phrasing. Matches anchor 3 ("Some relevant keywords but missing common variations or synonyms").

3 / 5

Distinctiveness Conflict Risk

"Lottie" is a distinct niche technology with minimal conflict risk against unrelated skills. Not 5 because the description is terse enough that it could overlap with a generic web-animation or performance-optimization skill, and no distinct concrete triggers are stated.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

Mindrally/skills

Path

lottie/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.