CtrlK
BlogDocsLog inGet started
Tessl Logo

animejs-animation

Advanced JavaScript animation library skill for creating complex, high-performance web animations.

40

Quality

40%

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 ./skills/animejs-animation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Scale 1-3

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

The skill provides a reasonable starting point for anime.js usage with one good executable example and clear organization, but it leans too heavily on motivational/aspirational language ('jaw-dropping', 'bespoke', 'ABSOLUTE MANDATE') at the expense of concrete, actionable guidance. Key advertised capabilities like SVG morphing, interactive animations, and advanced easing are mentioned but not demonstrated with code. The workflow lacks validation checkpoints.

Suggestions

Add executable code examples for SVG path animation and interactive/input-responsive animations, since these are listed as key use cases but have no concrete guidance.

Remove or significantly trim the motivational language ('jaw-dropping', 'awards-caliber', 'ABSOLUTE MANDATE') and replace with specific, actionable criteria for what makes a good animation (e.g., target frame rates, specific easing parameter ranges).

Add a validation/testing step to the workflow, such as checking animation performance with browser DevTools or verifying animations render correctly across target browsers.

Include a concrete example of custom cubicBezier or spring easing with parameter explanations, since the skill emphasizes advanced easing as crucial but only shows one spring example without explaining the parameters.

DimensionReasoningScore

Conciseness

The skill includes some unnecessary padding ('lightweight but extremely powerful', 'jaw-dropping', 'awards-caliber') and motivational language that doesn't add actionable value. The 'When to Use' section is reasonable but the 'Context' section is largely redundant with it. The 'ABSOLUTE MANDATE' rule is verbose and stylistic rather than instructive.

2 / 3

Actionability

There is one concrete, executable code example showing timeline usage with staggering, which is good. However, the skill lacks examples for several mentioned use cases (SVG path animation, morphing shapes, spring/elastic easing variations, responsive input handling). The guidance around performance ('use will-change') is concrete but thin; the SVG and interactive sections are vague descriptions rather than executable instructions.

2 / 3

Workflow Clarity

The 4-step execution workflow provides a reasonable sequence (Identify → Define → Orchestrate → Implement), but it lacks any validation or verification steps. There's no guidance on testing animations, checking for performance regressions, or verifying the output works correctly. For a skill involving DOM manipulation and performance-sensitive operations, the absence of feedback loops is a gap.

2 / 3

Progressive Disclosure

For a skill with no bundle files and under 50 lines of core content, the organization is appropriate. Sections are well-labeled and logically ordered (Context → When to Use → Workflow → Rules → Limitations). There are no deeply nested references or monolithic walls of text.

3 / 3

Total

9

/

12

Passed

Description

22%Scale 1-3

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

This description is too vague and lacks the concrete actions and explicit trigger guidance needed for effective skill selection. It reads more like a tagline than a functional description, failing to specify what concrete tasks it performs or when Claude should select it. The absence of a 'Use when...' clause and specific capability listing significantly weakens its utility.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about JavaScript animations, GSAP, Anime.js, scroll animations, or motion effects on web pages.'

List specific concrete actions instead of vague claims, e.g., 'Creates keyframe animations, builds scroll-triggered effects, implements easing functions, animates SVG paths, and configures animation timelines.'

Include the specific library name(s) this skill covers (e.g., GSAP, Framer Motion, Anime.js) to improve distinctiveness and trigger term quality.

DimensionReasoningScore

Specificity

The description says 'creating complex, high-performance web animations' which is vague. It doesn't list any concrete actions like 'create keyframe animations, build scroll-triggered effects, animate SVG elements'. The phrase 'advanced JavaScript animation library skill' is abstract.

1 / 3

Completeness

The 'what' is only vaguely stated ('creating complex, high-performance web animations') and there is no 'when' clause at all. There are no explicit triggers or 'Use when...' guidance, which per the rubric should cap completeness at 2, and the weak 'what' brings it down to 1.

1 / 3

Trigger Term Quality

It includes some relevant keywords like 'JavaScript', 'animation', and 'web animations' that users might naturally say. However, it's missing common variations like specific library names (GSAP, Anime.js), 'CSS transitions', 'motion', 'easing', 'keyframes', or file/framework references.

2 / 3

Distinctiveness Conflict Risk

The mention of 'JavaScript animation library' provides some specificity that distinguishes it from general coding or CSS skills, but it could easily overlap with general JavaScript skills, CSS animation skills, or front-end development skills.

2 / 3

Total

6

/

12

Passed

Validation

90%

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

Validation — 10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
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.