reset-preview-environment

Reset the Lens Studio preview to a clean state before scene generation.

16|2|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/lens-studio-devs/ls-extensions --skill reset-preview-environment-lens-studio-devs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reset-preview-environment
Source: https://github.com/lens-studio-devs/ls-extensions/tree/main/plugins/ls-clad/skills/reset-preview-environment
Command: npx skills add https://github.com/lens-studio-devs/ls-extensions --skill reset-preview-environment-lens-studio-devs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before generating a new scene in Lens Studio, leftover objects, misplaced cameras, and stale log output can corrupt results and make debugging difficult. This Skill restores the preview to a verified clean baseline so every scene generation starts from a known state. ## Core Features & Use Cases - Camera Reset: Locates the Camera or Main Camera object via ExecuteEditorCode and resets its position and rotation to the origin. - Visual Verification Loop: Captures Preview panel screenshots and iteratively disables stray scene objects until only the default virtual environment remains, up to 5 passes. - Log Baselining: Records the current log file length so only new entries generated during the subsequent build are analyzed. - Use Case: Before running an automated scene generation task, invoke this Skill to reset the camera, clear residual meshes and UI from the preview, and capture a log baseline for clean diagnostics. ## Quick Start Ask the agent to reset the Lens Studio preview environment and confirm it is clean before starting scene generation.

Frequently Asked Questions about reset-preview-environment

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

FAQPage Schema
How do I reset the Lens Studio preview before generating a scene?

Run this Skill to reset the camera transform to the origin, disable leftover scene objects, and verify via screenshots that only the default virtual environment remains. It also captures a log baseline for the upcoming build.

How does the preview cleanup verification loop work?

The Skill captures a Preview panel screenshot, checks for unexpected 3D meshes, UI, or text, and disables responsible objects via ExecuteEditorCode. It repeats up to 5 iterations, then warns the user if content remains.

Will resetting the preview disable lighting or the skybox?

No. The Skill explicitly avoids disabling permanent environment elements such as lighting rigs, skyboxes, device camera feeds, and tracking nodes. It prefers disabling top-level parent objects to clean subtrees efficiently.

What happens if no camera exists in the Lens Studio scene?

The Skill warns the user but continues with cleanup and log baselining. Some scenes legitimately lack an explicit Camera or Main Camera object, so this is treated as a non-blocking condition.

Is it safe to run the preview reset multiple times?

Yes, the Skill is idempotent. Re-running it simply re-resets the camera, re-verifies the preview is clean, and captures a fresh log baseline without compounding side effects.