Babylon.js model loading
Loads 3D models with their textures and animations as a complete, usable unit. It clarifies what instances share and what must stay independent when characters are spawned or removed.
babylonjs-gltf-assets
See how it helpsWhen is it useful?
Use when importing glTF assets or sharing models between several Babylon.js scene objects.
What does it help you do?
- Checks installed loaders, compression dependencies and external asset requirements.
- Distinguishes instances, clones and shared skeleton or material state.
- Handles cancelled loads and cleanup without exposing half-ready objects.
Try asking this
Import a glTF robot squad with walking and attack animations. Remove one robot while the others keep moving, then simulate a missing texture and cancel a second load. Show a useful loading error and keep already loaded robots intact.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Babylon.js — gltf assets
Use when loading Babylon models, animations, textures or streamed scene content.
Version and project gate
Inspect package.json and lockfile, Babylon package family and exact version, engine creation, WebGL/WebGPU choice, canvas hosting, loaders, physics plugin version and asset ownership. Keep Babylon Lite and the full engine APIs distinct. 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
Inventory the loader and compressed-asset dependencies already installed. Define asset-container ownership, instance versus clone needs, animation-group bindings and skeleton sharing. Handle failed or canceled loads without publishing a half-ready gameplay object. Keep external URLs and CORS requirements explicit.
Deliver
An asset import contract and a model integration with visible loading, failure and cleanup states. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Cloning transforms does not necessarily make materials, geometry or skeleton state independent.
Acceptance scenario
Load two instances, animate them separately where required, unload one and confirm the other remains intact. 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 Ziva. 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.
Included files 1
SKILL.md