What problem does it solve? Verifying that a Lens actually behaves correctly at runtime is hard: editor-side configuration tells you nothing about resolved object references, runtime-spawned components, or post-interaction state. This Skill lets you query the live Lens Studio preview scene and capture renders of it, so you can confirm what the Lens really does when it runs. ## Core Features & Use Cases - Runtime scene querying: Use QueryRuntimeSceneTool with GraphQL to walk the scene hierarchy, filter objects by component, name, property value, or spatial proximity, and read transforms, bounds, and component properties. - Orthographic scene capture: Use CaptureRuntimeViewTool to render the runtime scene from any angle, auto-frame specific objects by uniqueId, and isolate targets from occluders. - Multi-preview routing: Route queries and captures to specific preview panels by name for multiplayer or side-by-side Lens testing. - Use Case: After wiring a PinchButton in a Specs Lens, run the preview and query { sceneObjects(filter: {hasComponents: ["Interactable"]}) { matches { summary } } } to confirm the Interactable spawned at runtime, then capture an isolated front view of the button to verify its visual state. ## Quick Start Ask the agent to list the top-level objects in the running Lens Studio preview and show a render of the current scene.
