viverse-storage

Name: viverse-storage
Availability: InStock
Author: viverseofficial

Persist user game state to VIVERSE cloud via CloudSaveClient SDK.

2|1|Updated Mar 28, 2026

Search Tags:#persistence #storage #save-data #cloud-save #viverse #cloudsaveclient

Ready to run

npx skills add https://github.com/viverseofficial/viverse-sdk-skills --skill viverse-storage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: viverse-storage
Source: https://github.com/viverseofficial/viverse-sdk-skills/tree/main/skills/viverse-storage
Command: npx skills add https://github.com/viverseofficial/viverse-sdk-skills --skill viverse-storage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of maintaining consistent user progress across different devices and sessions by providing a robust, cloud-backed storage solution that handles authentication, local fallbacks, and data merging.

Core Features & Use Cases

Cloud Persistence: Securely save and retrieve game states like inventory, scores, and settings to the VIVERSE cloud.
Guest-to-Cloud Merging: Automatically promotes local guest progress to the cloud upon the user's first successful authentication.
Resilient Save Patterns: Implements safe exit-save mechanisms using fetch with keepalive to ensure data integrity during page transitions or closures.

Quick Start

Use the viverse-storage skill to initialize the CloudSaveClient with your app ID and synchronize the local game state with the cloud storage.

Frequently Asked Questions about viverse-storage

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

FAQPage Schema

How do I save game state to the cloud for VIVERSE apps?▼

To save game state to the cloud for VIVERSE apps, you use the CloudSaveClient SDK to perform secure upsert and retrieval operations. This requires a valid VIVERSE access token and a registered 10-character Studio app ID to persist user-scoped data.

How does cross-device synchronization work for cloud save data?▼

Cross-device synchronization works by managing local-to-cloud data merging for authenticated users. When a user logs in, the CloudSaveClient SDK automatically promotes and merges local guest progress into the cloud, ensuring consistent game state across all devices.

Can I use local storage as a fallback before a user authenticates with VIVERSE?▼

Yes, local storage serves as a fallback for guest users before authentication. The storage skill handles guest-to-cloud merging automatically, promoting local progress to the cloud upon the user's first successful authentication to prevent data loss.

How do I prevent data loss during page transitions when saving to the cloud?▼

To prevent data loss during page transitions, implement resilient exit-save mechanisms using fetch with keepalive. This ensures data integrity and reliable cloud persistence even if the user closes the page or navigates away before the upsert operation fully completes.

What do I need to set up cloud persistence for a VIVERSE application?▼

To set up cloud persistence, you need a valid VIVERSE access token and a registered 10-character Studio app ID. You use these credentials to initialize the CloudSaveClient SDK and securely synchronize your local game state with the cloud infrastructure.

What is the best way to handle user-scoped application data in VIVERSE?▼

The best way to handle user-scoped application data is using the CloudSaveClient SDK for cloud persistence. It manages secure upsert and retrieval operations, cross-device synchronization, and local-to-cloud data merging for authenticated users automatically.