viverse-skill-router

VIVERSE skill routing resolves overlapping requests by analyzing workspace dependencies and file paths to deterministically hand off tasks to the correct downstream skill. This ensures the appropriate CLI or publishing skill is invoked based on your project context.

To publish a VIVERSE world, the router detects your project type by analyzing workspace signals and dependencies. It then directs your publishing request to the appropriate general SDK or specialized PlayCanvas Toolkit skill.

You need to route VIVERSE multiplayer features when general SDK and PlayCanvas Toolkit functionalities overlap. The router resolves this ambiguity by analyzing your project context to ensure the correct multiplayer skill is invoked.

Yes, you can use the VIVERSE router to determine the correct skill by describing your project type and current requirements. It analyzes workspace configuration and user intent to provide a deterministic skill hand-off.

Deterministic skill hand-off relies on analyzing workspace configuration and dependency signals, meaning it requires clear project context to function correctly. It cannot route effectively if your project type signals are ambiguous or missing.

The best way to resolve ambiguity between VIVERSE SDK and PlayCanvas features is to use a routing skill that analyzes workspace signals. It provides a clear decision-making framework for overlapping features like leaderboards and multiplayer.