ls-skill-sandbox-tester

To run a smoke test without modifying the repository, the sandbox tester creates a unique temporary sandbox, copies the skill into it, and executes the smoke command in isolation. Changes are only written back after you explicitly approve promotion to the real skill location.

Sandbox isolation for skill vetting is the process of testing skill behavior in a temporary environment to prevent repo contamination. You need it during end-to-end vetting after normalization to ensure safe testing across platforms before production deployment.

To debug a failing smoke test inside a sandbox, the tester engages the ls-debug-pro protocol within the isolated environment. This allows you to reproduce, instrument, and fix issues directly in the sandbox without touching the real skill.

Yes, you can validate skills across supported platforms using sandbox isolation. The tester is designed for post-vet normalization testing, enforcing unique temporary sandbox creation to ensure safe testing of skill behavior across platforms.

The best way to prevent repo contamination during skill testing is to isolate the skill in a unique temporary sandbox. The sandbox tester enforces isolation by running smoke tests and debug loops separately, writing changes back only after user approval.

You should not write changes back to the real skill location until the user approves promotion from the sandbox. If a smoke test fails, all debugging and fixes must remain inside the sandbox to prevent touching the real skill.