From windows-dev-agent
Route code execution or tool testing into an isolated environment. Use when running untrusted code, testing installers, or needing reproducible execution. Chooses between Windows Sandbox, WSL, Dev Container, or Hyper-V based on what's available and what's needed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/windows-dev-agent:sandbox-runThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When isolated execution is needed, choose the right environment:
When isolated execution is needed, choose the right environment:
| Scenario | Environment | Why |
|---|---|---|
| Run untrusted installer/script | Windows Sandbox | Disposable, no host impact |
| Linux-native tool | WSL | Native Linux layer |
| Reproducible project build | Dev Container | Locked deps, portable |
| Persistent high-isolation work | Hyper-V VM | Full OS isolation |
| Fast scripting test | WSL | Lightweight |
env_inspect (virtualization section)Enable-WindowsOptionalFeature -Online -FeatureName "Containers-DisposableClientVM"wsl --installEnable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Allwsl -d Ubuntu -- bash -c "<command>"
Create a .wsb config file and launch:
$config = @"
<Configuration>
<MappedFolders>
<MappedFolder>
<HostFolder>$env:USERPROFILE\sandbox-work</HostFolder>
<SandboxFolder>C:\Users\WDAGUtilityAccount\Desktop\work</SandboxFolder>
<ReadOnly>false</ReadOnly>
</MappedFolder>
</MappedFolders>
<LogonCommand>
<Command>powershell -Command "cd C:\Users\WDAGUtilityAccount\Desktop\work; <your-command>"</Command>
</LogonCommand>
</Configuration>
"@
$config | Out-File "$env:TEMP\sandbox.wsb"
Start-Process "$env:TEMP\sandbox.wsb"
All sandbox runs are approval-required. Show the config before launching.
npx claudepluginhub the-biomechanist/windows-dev-agentCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.