viverse-auth

Integrate VIVERSE SDK authentication and SSO into web experiences.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill resolves the complexity of integrating VIVERSE authentication into web applications, ensuring reliable SSO and robust user profile recovery across different SDK versions and iframe environments.

Core Features & Use Cases

  • Robust Auth Handshake: Implements mandatory iframe handshake delays and domain-specific client initialization to prevent common connection failures.
  • Canonical Profile Recovery: Uses a multi-strategy fallback chain (Avatar SDK, getUserInfo, getUser, API) to ensure user identity and avatar data are retrieved even when specific methods fail.
  • Use Case: A developer building a VIVERSE World app can use this to ensure that user login state is maintained, profile names are displayed correctly without exposing raw account IDs, and the user experience remains consistent across sessions.

Quick Start

Use the viverse-auth skill to initialize the VIVERSE client and retrieve the current user profile using the robust multi-strategy fallback chain.

Frequently Asked Questions about viverse-auth

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

FAQPage Schema
How do I integrate VIVERSE SSO authentication into a web application?

VIVERSE SSO integration is handled by initializing a secure client, managing session state persistence, and retrieving user profiles. It ensures reliable login state maintenance across sessions for web-based experiences.

Why does VIVERSE authentication fail inside an iframe environment?

Iframe authentication failures occur when mandatory handshake delays and domain-specific client initialization are missing. Implementing strict compliance requirements for iframe-based environments prevents these common connection failures.

What is the best way to retrieve user identity data when the VIVERSE SDK getUserInfo method fails?

User identity recovery uses a canonical multi-strategy fallback chain. It queries Avatar SDK, getUserInfo, getUser, and API sequentially to ensure profile and avatar data are retrieved even when specific methods fail.

Can I use VIVERSE login to display user profile names without exposing raw account IDs?

VIVERSE login supports canonical profile recovery to display user profile names correctly. This multi-strategy approach enriches identity data while preventing the exposure of raw account IDs across different SDK versions.

Does VIVERSE authentication support cross-platform identity resolution for web-based experiences?

VIVERSE authentication supports cross-platform identity resolution by managing secure client initialization and session state persistence. This ensures consistent user identity and avatar data across different platforms and SDK versions.

What are the limitations of using VIVERSE SDK for single sign-on in web apps?

VIVERSE SDK single sign-on requires strict compliance with iframe handshake delays and domain-specific initialization. Without these mandatory steps, users may experience connection failures or incomplete user profile data recovery.