deploy-worlds

Deploy Decentraland scenes to World spaces using a NAME or ENS domain.

3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/decentraland/sdk-skills --skill deploy-worlds-decentraland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-worlds
Source: https://github.com/decentraland/sdk-skills/tree/main/deploy-worlds
Command: npx skills add https://github.com/decentraland/sdk-skills --skill deploy-worlds-decentraland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying Decentraland scenes to personal Worlds requires correct ownership checks, worldConfiguration setup, and control over Places listing, which can be error-prone without clear guidance.

Core Features & Use Cases

  • Streamlined World deployment workflow for personal Worlds using a Decentraland NAME or ENS domain.
  • Guidance to configure worldConfiguration in scene.json, including ownership validation and optional skybox or minimap settings.
  • Opt-out of Places listing and built-in deployment validations to catch common issues before publishing.

Quick Start

Configure scene.json with worldConfiguration pointing to your NAME or ENS and then run the publish workflow to deploy your World.

Frequently Asked Questions about deploy-worlds

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

FAQPage Schema
How do I deploy a Decentraland scene to a personal World using an ENS domain?

To deploy a Decentraland scene to a personal World, configure scene.json with worldConfiguration pointing to your NAME or ENS, then run the publish workflow to deploy your World space.

What is worldConfiguration in scene.json used for when publishing to Decentraland Worlds?

worldConfiguration in scene.json defines the target NAME or ENS for your World, performs ownership validation, and sets optional visual environment configurations like skybox or minimap settings.

Can I opt out of Places listing when deploying a scene to my World?

Yes, you can opt out of Places listing during the World deployment workflow. The process provides explicit opt-out options alongside built-in validations to catch common publishing issues.

Do I need a specific NAME or ENS to publish a Decentraland scene to a World?

Yes, deploying to a personal World requires a Decentraland NAME or ENS domain. The deployment process enforces worldConfiguration setup in scene.json to verify ownership of the specified domain.

Why does my Decentraland World deployment fail validation checks?

World deployment fails validation when scene.json lacks proper worldConfiguration setup, has incorrect NAME or ENS ownership, or contains configuration errors that the built-in deployment validations catch before publishing.