viverse-cli-publish

Name: viverse-cli-publish
Availability: InStock
Author: viverseofficial

Publishes Playcanvas Toolkit builds to the VIVERSE platform via CLI.

2|1|Updated Mar 28, 2026

Search Tags:#automation #publishing #deployment #cli #playcanvas #viverse

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @viverse/cli.

What problem does it solve?

This skill simplifies the deployment of local PlayCanvas Toolkit builds to the VIVERSE platform, removing the complexity of manual CLI configuration and environment verification.

Core Features & Use Cases

Automated Deployment: Handles the authentication, app creation, and publishing process for local build folders.
Environment Validation: Automatically checks for necessary prerequisites like Node.js versions to ensure a smooth upload.
Use Case: A developer has a finished local build folder and needs to deploy it to a new VIVERSE world without manually navigating the CLI or Studio interface.

Quick Start

Use the viverse-cli-publish skill to upload the folder named dist to my existing VIVERSE app.

Frequently Asked Questions about viverse-cli-publish

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

FAQPage Schema

How do I deploy a local PlayCanvas build to VIVERSE from the command line?▼

To deploy a local PlayCanvas build to VIVERSE, use this skill to automate authentication, app creation, and publishing via the CLI. It uploads your local build directory directly to the VIVERSE platform without manual configuration.

Do I need the @viverse/cli package to publish a VIVERSE app?▼

Yes, you need the @viverse/cli package installed to publish a VIVERSE app. The skill also requires a valid local build directory and automatically validates your Node.js environment to ensure a smooth deployment sequence.

Can I automate VIVERSE world creation and deployment without using the Studio interface?▼

You can automate VIVERSE world creation and deployment entirely via CLI, bypassing the Studio interface. This skill handles the full publishing sequence, authenticating your account and creating the app target for your local build folder.

What is the best way to upload a dist folder to an existing VIVERSE app?▼

The best way to upload a dist folder to an existing VIVERSE app is using this CLI skill. It streamlines the workflow by validating prerequisites, handling authentication, and deploying the local PlayCanvas Toolkit build output directly.

Why does my VIVERSE CLI publishing workflow fail during environment validation?▼

VIVERSE CLI publishing fails during environment validation if necessary prerequisites are missing. The skill automatically checks for required conditions like valid Node.js versions to prevent upload errors before initiating the deployment sequence.

Does the viverse-cli-publish skill support manual environment configuration overrides?▼

The viverse-cli-publish skill removes the complexity of manual CLI configuration by automating environment validation and deployment. It requires a valid local build directory to execute the publishing sequence rather than relying on manual setup.