toolkit-build-and-package

Classify project directories into editing, PlayCanvas sync, or upload folders.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the confusion surrounding project folder structures by automatically identifying whether a directory is intended for editing, PlayCanvas synchronization, or final VIVERSE deployment.

Core Features & Use Cases

  • Automated Classification: Instantly determines if a folder contains source code, sync-ready assets, or production-ready build output.
  • Workflow Routing: Guides users to the correct next step, such as building, syncing, or publishing, based on the folder's contents.
  • Use Case: If you are unsure if your current folder is ready for upload or if it still requires a build step, this skill analyzes the file structure and provides clear, actionable instructions to prevent deployment errors.

Quick Start

Use the toolkit-build-and-package skill to analyze the current folder and determine if it is ready for VIVERSE publishing.

Frequently Asked Questions about toolkit-build-and-package

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

FAQPage Schema
How do I know if my VIVERSE project folder is ready for final upload or needs a build step?

Classifying your VIVERSE project folder involves analyzing file patterns and metadata to distinguish between source workspaces, PlayCanvas sync-ready assets, and production-ready build outputs, guiding you to the correct build, sync, or publish action.

What is the difference between a PlayCanvas sync folder and a final VIVERSE deployment directory?

A PlayCanvas sync folder contains sync-ready assets for intermediate synchronization, while a final VIVERSE deployment directory contains production-ready build output intended for direct publishing to the VIVERSE platform.

How to classify VIVERSE SDK project directories for correct deployment workflows?

Classify VIVERSE SDK project directories by analyzing detected file patterns and project metadata to route them into editing, PlayCanvas synchronization, or final upload folders, ensuring correct deployment workflows and preventing publishing errors.

Can I use my current source workspace directly for VIVERSE publishing?

You cannot use a source workspace directly for VIVERSE publishing if it lacks production-ready build output; the toolkit analyzes the directory contents and instructs you to perform a build step before attempting final upload.

Why does my VIVERSE deployment fail when uploading from an editing directory?

VIVERSE deployment fails when uploading from an editing directory because it contains source code rather than production-ready build output, requiring you to route the project through the correct build or PlayCanvas sync workflow first.