What problem does it solve? Publishing a Decentraland scene to a personal World requires correct scene.json configuration, NAME or ENS ownership, storage budget awareness, and a different deploy target than Genesis City, and mistakes in any of these cause failed or rejected deployments. ## Core Features & Use Cases - World Configuration: Add and validate the worldConfiguration section in scene.json, including Places opt-out, discovery metadata, and skybox fixed-time settings. - Deployment Guidance: Deploy via the /deploy command, CLI with the Worlds content server target, or the Creator Hub publish flow, including multi-scene Worlds and collaborator access. - Troubleshooting: Resolve common failures such as NAME ownership errors, storage budget overruns, and Worlds not appearing on Places. - Use Case: A creator owns my-name.dcl.eth and wants to publish a social hangout scene; this Skill walks through configuring scene.json, checking the storage budget, deploying, and sharing the visit URL. ## Quick Start Deploy my Decentraland scene to my World at my-name.dcl.eth and configure scene.json for it.