CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

threejs-animation

Three.js animation - keyframe animation, skeletal animation, morph targets, animation mixing. Use when animating objects, playing GLTF animations, creating procedural motion, or blending animations.

Quality

75%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/threejs-animation/SKILL.md

The canonical home for this skill is threejs-animation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized, highly executable Three.js animation reference with strong copy-paste-ready examples throughout. Its main weaknesses are the fully monolithic 550-line inline structure with no reference files, and a procedural-math section that spends tokens on concepts Claude already knows.

Suggestions

Move the "Procedural Animation Patterns" section (smoothDamp, Spring, Oscillation) to a reference file or drop it — this is standard math Claude already knows and costs ~80 lines of context.

Split advanced topics (Skeletal Animation details, Animation Utilities, Performance Tips) into a reference file (e.g., references/advanced.md) linked from SKILL.md, keeping SKILL.md as a lean overview with Quick Start and core mixer/action usage.

Add one explicit end-to-end workflow for the most common task (load a GLTF, create a mixer, play a named clip, update in the render loop) with a checkpoint for the empty-animations case, instead of spreading the steps across separate sections.

DimensionReasoningScore

Conciseness

The body is mostly lean, comment-dense code that assumes Three.js knowledge, but the ~80-line "Procedural Animation Patterns" section (smoothDamp implementation, a Spring class, and sine/circular/figure-8 oscillation) explains standard math Claude already knows. That is more than the "minor instances of over-explanation" of anchor 4, fitting anchor 3's "includes some unnecessary explanation or could be tightened".

3 / 5

Actionability

Nearly all sections provide concrete, executable code (Quick Start, KeyframeTrack types, GLTF load-and-play, crossfade, blending), covering the common cases. Minor gaps keep it below 5: the AnimationMixer example uses an undefined `clock` immediately after the skill recommended `THREE.Timer`, and the GLTF example resorts to a `window.mixer = mixer` storage hack.

4 / 5

Workflow Clarity

Sequences are implicit rather than explicit: the mixer pattern (create mixer → clipAction → play → update each frame, with a helpful "Required!" callout) and the GLTF section show a workable order, but there is no explicit step-by-step workflow with checkpoints (e.g., for setting up blending or debugging an empty animations array beyond one `clips.length > 0` guard). This fits anchor 3's "sequence present but checkpoints missing or implicit".

3 / 5

Progressive Disclosure

There are no bundle files at all (no references/, scripts/, or assets/), so the entire ~550-line reference is inlined in SKILL.md with good section headers but no offloading. Content that clearly belongs in separate files (procedural math patterns, performance tips, skeletal-animation deep dive) is inline, matching anchor 3's "content that should be separate is inline"; structure is too good for anchor 2's "minimal structure".

3 / 5

Total

13

/

20

Passed

Description

83%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 is strong: it names four concrete capabilities and provides an explicit, natural-language "Use when" clause with multiple trigger phrases. Its only weaknesses are verb-less topic listing in the capabilities segment and some missing common synonyms (character animation, rigging, skinning) that would improve trigger coverage.

DimensionReasoningScore

Specificity

"keyframe animation, skeletal animation, morph targets, animation mixing" lists four distinct concrete capabilities with only minor gaps (e.g., playback control and performance tuning are not mentioned). It falls short of 5 because these are topic nouns rather than concrete actions, and above 3 because it covers far more than 1-2 actions.

4 / 5

Completeness

Both questions are answered explicitly: the "what" is stated concretely ("keyframe animation, skeletal animation, morph targets, animation mixing") and the "when" is an explicit "Use when..." clause with multiple concrete trigger phrases ("animating objects, playing GLTF animations, creating procedural motion, or blending animations"). This matches the anchor-5 example structure.

5 / 5

Trigger Term Quality

"animating objects", "playing GLTF animations", "creating procedural motion", "blending animations" are phrases a user would naturally say, alongside domain keywords like "morph targets" and "skeletal animation". Common variants such as "character animation", "rigging", "bones", or "skinning" are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

"Three.js animation" carves a clear niche, but the skill body itself notes a sibling skill "threejs-fundamentals" covering "Clock and animation loop", indicating minor overlap risk with closely related skills. It is far more distinct than the anchor-3 "somewhat specific" case and just short of minimal conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (560 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/threejs-animation/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.