composites

Author and validate Decentraland main.composite JSON files defining initial scene entities.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/stom66/dcl-bowling --skill composites-stom66
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: composites
Source: https://github.com/stom66/dcl-bowling/tree/main/agent/skills/composites
Command: npx skills add https://github.com/stom66/dcl-bowling --skill composites-stom66

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Hand-editing a Decentraland scene's main.composite file is error-prone: entities can fall outside parcel bounds and never render, missing inspector::Nodes entries make entities invisible in the Creator Hub entity tree, and incorrect jsonSchema usage causes SDK build failures. This Skill provides the format reference and mandatory validation workflow to author or edit composites correctly. ## Core Features & Use Cases - Composite Format Reference: Full specification of the main.composite JSON structure, entity ID allocation, and per-component catalogs (core::Transform, core::GltfContainer, core::MeshCollider, core::Animator, and more). - Bounds and Bounding-Box Validation: Mandatory Step 0 computes scene bounds from scene.json parcels and measures GLB bounding boxes so models are never placed outside the renderable area. - Edit-Mode vs Authoring-Mode Rules: Distinct checklists for fresh composites versus scenes already saved by the Creator Hub, including inspector::Nodes synchronization and the Creator Hub MCP gate. - Use Case: When adding a new 3D model entity to an existing Decentraland scene without the Creator Hub MCP, follow the edit-mode checklist to register the entity in inspector::Nodes, add core-schema::Name, and verify with an SDK build. ## Quick Start Ask the AI to add a new GLB model entity to the scene's main.composite file while keeping it inside the parcel bounds and visible in the Creator Hub entity tree.

Frequently Asked Questions about composites

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

FAQPage Schema
How do I add an entity to a Decentraland main.composite file?▼

Add the entity under core::Transform with a unique ID starting at 512, give it a core-schema::Name, and attach feature components like core::GltfContainer. If the composite already contains inspector::Nodes, also register the new ID there or it will be invisible in the Creator Hub entity tree.

Why is my composite entity invisible in the Creator Hub entity tree?▼

The entity was added to core::Transform but not registered in inspector::Nodes. Append its ID to the parent entry's children array and add a matching top-level entry in the Nodes value array so the editor tree recognizes it.

Should I edit main.composite by hand or use the Creator Hub MCP?▼

Prefer the Creator Hub MCP whenever its tools are available, because the editor autosaves and regenerates main.composite wholesale, silently discarding external file edits. Hand-edit only when the MCP is unavailable and the scene is closed in the Creator Hub.

Why does my SDK build fail with an undefined component error?▼

The build fails when a non-core component like asset-packs::Actions lacks its jsonSchema, or when inspector:: components are included in a freshly authored composite. Copy jsonSchema from the asset catalog for non-core components and omit inspector components when authoring from scratch.

How do I keep GLB models inside Decentraland scene bounds?▼

Compute valid X and Z ranges from scene.json parcels (16 meters per parcel), then parse the GLB binary to measure its real bounding box including node transforms. Place the model origin so the full bounding box stays inside the computed bounds with at least a 1 meter margin.