viverse-avatar-sdk

Load authenticated VIVERSE avatars into Three.js scenes with animation retargeting.

2|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/viverseofficial/viverse-sdk-skills --skill viverse-avatar-sdk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: viverse-avatar-sdk
Source: https://github.com/viverseofficial/viverse-sdk-skills/tree/main/skills/viverse-avatar-sdk
Command: npx skills add https://github.com/viverseofficial/viverse-sdk-skills --skill viverse-avatar-sdk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the complexity of loading, animating, and troubleshooting VIVERSE user avatars (GLB/VRM) within 3D web environments, preventing common issues like T-poses, invisible meshes, and incorrect bone mapping.

Core Features & Use Cases

  • Robust Avatar Loading: Implements secure, authenticated loading of GLB/VRM models with automatic fallback to placeholders.
  • Advanced Animation Retargeting: Provides manual animation sampling patterns to bypass limitations in standard animation components, ensuring smooth VRMA/GLB motion.
  • Use Case: A developer building a social 3D space can use this skill to ensure every authenticated user's unique avatar is correctly rendered, scaled, and animated regardless of whether the user is using a standard GLB or a VRM-backed model.

Quick Start

Use the viverse-avatar-sdk to load the authenticated user avatar into the current Three.js scene and apply the walk animation cycle.

Frequently Asked Questions about viverse-avatar-sdk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load authenticated VIVERSE user avatars into a Three.js scene?

To load VIVERSE user avatars, you implement secure authenticated access to fetch GLB and VRM models, managing the 3D asset lifecycle to correctly render and scale unique user avatars within your Three.js environment.

Why do VRM and GLB avatars appear in T-poses with invisible meshes in PlayCanvas?

T-poses and invisible meshes occur due to incorrect bone mapping and lack of rendering fallbacks. Normalizing bone hierarchy and implementing robust avatar loading with placeholder fallbacks resolves these 3D rendering issues.

Can I retarget VRMA animations onto VIVERSE avatars without standard component limitations?

Yes, you can bypass standard animation component limitations by using manual animation sampling patterns for VRMA and GLB motion retargeting, ensuring smooth avatar animation cycles in web environments.

What is the best way to manage 3D asset lifecycle for VRM and GLB avatars?

The best way to manage 3D asset lifecycle is through secure profile data access and robust loading protocols that handle bone hierarchy normalization and rendering fallbacks for authenticated VIVERSE avatars.

Does the VIVERSE avatar integration support both PlayCanvas and Three.js environments?

Yes, VIVERSE avatar integration supports both PlayCanvas and Three.js environments, handling complex animation retargeting, bone hierarchy normalization, and rendering fallbacks across these 3D web frameworks.

When do I need bone hierarchy normalization for 3D avatars?

You need bone hierarchy normalization when loading GLB or VRM formats to prevent incorrect bone mapping and T-poses, ensuring authenticated user avatars are correctly rendered and animated in 3D scenes.