// Asset search (local and external), asset metadata lookup, model import, and 3D model generation for Studio 3D. Use for finding, inspecting, downloading, and placing 3D models in the scene.
Scene lighting, light object properties, fog, background, tone mapping, and post-processing for Studio 3D. Use for mood, atmosphere, shadows, and visual environment setup.
Add sound effects and audio to 3D scenes in Studio 3D game engine. Use when the user asks to add sounds, music, audio feedback, or sound effects to objects or events. Covers the genericSound behavior for event-triggered audio, audio resource management, and common patterns like ambient sound, collision SFX, UI click sounds, and background music. Examples include "add a sound when the coin is collected", "play background music", "add footstep sounds to the character", or "make the button click sound".
Behavior discovery, creation, update, attach/detach, and configuration in Studio 3D. Use for built-in behavior reuse first, then custom behavior authoring only when needed.
Camera type, perspective, and configuration for Studio 3D. Use for camera type selection, FOV, clipping planes, and genre-appropriate camera setup.
Master routing skill for StemStudio ACP work. Use for broad or ambiguous requests such as "make a game", "build a scene", "improve this", or any task that needs skill selection, scene inspection, staged execution, and clean scene hierarchy.
EventBus guidance for behavior-to-behavior messaging in Studio 3D. Use when behaviors need decoupled communication, topic design, or event lifecycle cleanup.
| name | stemstudio-assets |
| description | Asset search (local and external), asset metadata lookup, model import, and 3D model generation for Studio 3D. Use for finding, inspecting, downloading, and placing 3D models in the scene. |
Use this skill for asset discovery, model import, and generation.
Search local assets first, then external, then generate as a last resort:
python scripts/search_local_assets.py --phrases castle medieval fortress stone tower
Choose one approach per object and stick to it:
stemstudio-objectsstemstudio-prefabsBreak the user's description into individual keywords including synonyms (OR logic — more keywords = better recall):
# WRONG: --phrases "medieval castle with drawbridge"
# RIGHT: decompose into individual keywords
python scripts/search_local_assets.py --phrases castle medieval fortress stone tower drawbridge bridge gate
python scripts/search_local_assets.py --phrases sword weapon blade iron --type model
Before placing an uncertain local result, fetch details by asset ID:
python scripts/get_library_asset.py --assetId "asset-123"
Pass the natural language prompt as-is (external providers handle NLP):
python scripts/search_external_assets.py --prompt "oak tree"
python scripts/search_external_assets.py --prompt "medieval sword" --provider sketchfab --limit 5
Providers: sketchfab, polyhaven, meshy.
python scripts/add_model_to_scene.py "ext-123" "Medieval Sword" sketchfab "https://example.com/sword.glb" --position 0 1 0
python scripts/add_model_to_scene.py "local-456" "Oak Tree" local "/assets/tree.glb" --position 5 0 3
python scripts/generate_3d_model.py "a medieval sword" --name "Sword" --position 0 1 0
generate_3d_model.py is slow and should be the fallback path, not the first path.
Use this skill for:
Do not use this skill for:
stemstudio-objects)stemstudio-prefabs)stemstudio-materials)stemstudio-scene)After adding a model, verify it appeared:
python ~/.claude/skills/stemstudio-scene/scripts/get_scene_objects.py --filter "Sword"
~/.claude/stemstudio-docs/architecture.md~/.claude/stemstudio-docs/prefab-system.mdstemstudio-objects for primitives when asset search isn't neededstemstudio-prefabs for reusable templatesstemstudio-materials for texturing imported modelsstemstudio-threejs-loaders for custom loader configurations