ls-skill-sandbox-tester

Execute smoke tests on skill copies in isolated temporary sandboxes.

3|2|Updated Dec 25, 2025

Search Tags:#automation #testing #debugging #sandbox #smoke-test #skill-vetting

Ready to run

npx skills add https://github.com/CruxExperts/localsetup --skill ls-skill-sandbox-tester

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ls-skill-sandbox-tester
Source: https://github.com/CruxExperts/localsetup/tree/main/_localsetup/skills/ls-skill-sandbox-tester
Command: npx skills add https://github.com/CruxExperts/localsetup --skill ls-skill-sandbox-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Allows teams to validate and smoke-test skills in an isolated sandbox, preventing any writes to the repo during validation.

Core Features & Use Cases

Create a unique temporary sandbox and copy the skill into it for isolated testing.
Run a smoke command inside the sandbox and treat exit code 0 as success.
When smoke fails, engage the ls-debug-pro protocol inside the sandbox to reproduce, instrument, and fix without touching the real skill.
Do not write changes back to the repository until the user approves promotion from sandbox to the real skill location.
Designed for post-vet/normalization testing before production deployment across supported platforms.

Quick Start

Use the sandbox tester to create a sandbox copy of the skill and run a smoke test against its main entry point.

Frequently Asked Questions about ls-skill-sandbox-tester

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

FAQPage Schema

How do I run a smoke test on a skill without modifying the repository?▼

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.

What is sandbox isolation for skill vetting and when do I need it?▼

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.

How do I debug a failing smoke test inside a sandbox?▼

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.

Can I validate skills across different platforms using sandbox isolation?▼

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.

What is the best way to prevent repo contamination during skill testing?▼

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.

When should I not write changes back to the real skill location?▼

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.