sdk-scenes

Build and extend Decentraland SDK7 scenes with composite-first authoring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers lack clear, safety‑first guidance for building Decentraland SDK7 scenes, especially regarding composite‑first authoring, asset handling, and deployment constraints within the QuickJS sandbox.

Core Features & Use Cases

  • Composite‑first rule: Enforces that all static entities are defined in composites, keeping TypeScript code focused on dynamic behavior.
  • Behavioral guidelines: Provides a structured approach to confirm parcel changes, asset fetching, and authoritative server additions with the user.
  • Index of topic skills: Links to specialized skills such as create-scene, add-3d-models, multiplayer-sync, and more, enabling modular scene development.
  • Shared references: Includes component APIs, asset catalogs, and validation rules for consistent implementation.
  • Use case: A developer can quickly scaffold a new scene, add 3D models from the catalog, configure interactivity, and deploy it while adhering to best‑practice safety checks.

Quick Start

Create a new Decentraland SDK7 scene scaffold with default configuration.

Frequently Asked Questions about sdk-scenes

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

FAQPage Schema
How do I create a Decentraland SDK7 scene using composite-first authoring?

To create a Decentraland SDK7 scene, define all static entities in composites first, keeping TypeScript code focused on dynamic behavior. This approach enforces safety-first guidance and maintains clear separation between static layout and interactivity.

What are the QuickJS sandbox constraints for Decentraland scene deployment?

Decentraland scene deployment requires operating within sandboxed QuickJS runtime constraints. This affects asset fetching confirmations and how you handle interactivity setup, ensuring your scene logic runs safely inside the limited runtime environment.

Can I add 3D models and configure multiplayer sync in a Decentraland SDK7 scene?

Yes, you can add 3D models from the asset catalog and configure multiplayer sync. The scene creation workflow links to specialized skills like add-3d-models and multiplayer-sync, enabling modular development with consistent component APIs.

Do I need an authoritative server for interactivity setup in Decentraland scenes?

An authoritative server is optional for Decentraland scene interactivity setup. The workflow provides behavioral guidelines to confirm parcel changes, asset fetching, and authoritative server additions with the user before deployment.

What is the best way to scaffold a new Decentraland SDK7 scene for deployment?

The best way to scaffold a Decentraland SDK7 scene is using the default configuration quick start. This applies composite-first rules, asset integration, and deployment guidance while satisfying sandboxed QuickJS runtime constraints.

Why does my Decentraland SDK7 scene fail validation during asset integration?

Decentraland SDK7 scene validation failures often occur when composite-first rules are ignored or asset fetching confirmations are bypassed. Ensure static entities are defined in composites and component APIs follow shared reference validation rules.