CtrlK
BlogDocsLog inGet started
Tessl Logo

animejs-animation

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

48

Quality

36%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/animejs-animation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

22%

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 is too vague and lacks concrete actions, explicit trigger guidance, and distinguishing details. It reads more like a tagline than a functional skill description. Without a 'Use when...' clause and specific capabilities listed, Claude would struggle to reliably select this skill from a pool of similar frontend/animation skills.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about JavaScript animations, GSAP, motion effects, scroll animations, or keyframe-based transitions.'

List specific concrete actions the skill performs, e.g., 'Creates keyframe animations, builds scroll-triggered transitions, animates SVG paths, configures easing functions, and orchestrates complex animation timelines.'

Specify which animation library or framework this skill covers (e.g., GSAP, Anime.js, Framer Motion) to improve distinctiveness and reduce conflict with general frontend skills.

DimensionReasoningScore

Specificity

The description says 'creating complex, high-performance web animations' which is vague. It does not list any concrete actions like 'create keyframe animations', 'animate SVG elements', 'build scroll-triggered transitions', etc.

1 / 3

Completeness

The description weakly addresses 'what' (creating web animations) but completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also vague, so this scores a 1.

1 / 3

Trigger Term Quality

It includes some relevant keywords like 'JavaScript', 'animation', and 'web animations' that users might naturally say, but misses common variations like 'CSS transitions', 'motion', 'easing', 'GSAP', 'keyframes', 'animate', or specific library names.

2 / 3

Distinctiveness Conflict Risk

While 'JavaScript animation library' narrows the domain somewhat, it could easily overlap with general CSS/frontend skills, UI component skills, or other animation-related skills. It doesn't specify which library or what distinguishes it from general web development skills.

2 / 3

Total

6

/

12

Passed

Implementation

50%

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 decent starting point for anime.js usage with one good executable example and clear section organization. However, it suffers from motivational/marketing language that wastes tokens, incomplete actionable guidance (only one code example for a skill claiming 'advanced' scope), and missing validation/verification steps. The 'Strict Rules' section is more aspirational than instructive.

Suggestions

Replace vague mandates in 'Strict Rules' (e.g., 'feel bespoke') with concrete techniques—provide specific easing values, stagger patterns, or before/after code comparisons that demonstrate quality differences.

Add executable code examples for SVG path animation and advanced staggering patterns, since these are listed as primary use cases but have no concrete guidance.

Add a validation/testing step to the workflow, such as checking animation frame rate with DevTools Performance panel or verifying `will-change` usage doesn't cause layer explosion.

Remove the 'Context' section or merge it into 'When to Use' to eliminate redundancy and improve token efficiency.

DimensionReasoningScore

Conciseness

Contains some unnecessary filler ('jaw-dropping', 'awards-caliber', 'feel expensive') and motivational language that doesn't add actionable value. The 'Context' section largely restates the 'When to Use' section. However, the core technical content is reasonably focused.

2 / 3

Actionability

Provides one executable code example for timelines, but coverage is incomplete—no examples for SVG path animation, staggering patterns beyond the basic one shown, or custom easing definitions. The 'Strict Rules' section uses vague mandates ('feel bespoke, fluid, and heavily polished') rather than concrete techniques.

2 / 3

Workflow Clarity

The 4-step workflow is listed but lacks validation checkpoints—there's no guidance on testing animations, checking performance metrics, or verifying rendering across browsers. For a skill involving DOM manipulation and performance-sensitive operations, the absence of any verification step is a gap.

2 / 3

Progressive Disclosure

Content is reasonably structured with clear sections, but everything is inline in a single file. For an 'advanced' animation skill, there are no references to separate files for SVG animation patterns, easing reference tables, or complex timeline examples that would benefit from being split out.

2 / 3

Total

8

/

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.

Validation10 / 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
sickn33/antigravity-awesome-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.