What problem does it solve? Hand-editing a Decentraland scene's main.composite, main.crdt, or scene.json while the Creator Hub is open silently loses changes, because the editor regenerates those files from its in-memory engine. This Skill routes every scene mutation through the Creator Hub's built-in MCP server so edits apply to the live scene, autosave correctly, and remain undoable. ## Core Features & Use Cases - Live scene editing: Read and mutate entities, components, Smart Items, and scene settings through tools like scene_state, create_entity, set_component, and place_smart_item, with every change visible in the viewport and undoable by the user. - Catalog-first workflow: Search the asset-packs catalog before building objects manually, so lights, furniture, media, and triggers arrive with models, actions, and inspector integration preconfigured. - Preview and verification: Launch the Decentraland Explorer preview, take editor screenshots, check scene metrics against budgets, and inspect logs to validate changes. - Use Case: A user asks to add a spotlight to their open scene. The Skill searches the catalog for the Spotlight Smart Item, places it with place_smart_item, verifies the result with editor_screenshot, and never touches main.composite directly. ## Quick Start Ask the agent to add a point light above the spawn point in the scene currently open in the Creator Hub.