Three.js glTF and animation
Gives model instances independent animation while retaining deliberately shared geometry and textures. It handles cancelled loading and cleanup so removing one character does not break the rest of the cast.
threejs-gltf-animation
See how it helpsWhen is it useful?
Use when animated model clones share skeleton state or fail during removal.
What does it help you do?
- Matches loaders and decoders to the installed Three.js revision.
- Tracks shared geometry, materials and instance-owned skeletons.
- Manages animation blends, cached actions and canceled loads.
Try asking this
Load three glTF guards with idle, walk and attack clips. Blend one guard into an attack while another walks, then remove the attacker. Check that the remaining skeletons animate independently, shared textures survive and a cancelled replacement load creates no stray guard.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Three.js — gltf animation
Use when integrating Three.js glTF, skinned models, animation clips or compressed assets.
Version and project gate
Inspect Three.js revision, renderer/backend, addons import style, bundler, color-management conventions, animation loop owner, scene scale, glTF/decoder versions and existing physics wrapper. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Pin loader/addon and decoder versions to the installed revision. Inventory shared geometry/material/skeleton ownership. Bind animation mixers to the intended instance, define clip transitions and cleanup cached actions. Keep loading errors and canceled scene ownership visible.
Deliver
An asset/animation contract and a model integration that survives independent instance removal. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A shallow clone of a skinned hierarchy may share skeleton state unexpectedly; an unloaded texture is not proof of disposed GPU resources.
Acceptance scenario
Animate two instances independently, remove one during a blend and reload the scene after a failed model request. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Vex. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Task-specific official references
Included files 1
SKILL.md