skill-isolation-tester

# Skill Isolation Tester

Tests Claude Code skills in isolated environments to ensure they work correctly without dependencies on your local setup.

## When to Use

**Trigger Phrases**:
- "test skill [name] in isolation"
- "validate skill [name] in clean environment"
- "test my new skill in worktree/docker/vm"
- "check if skill [name] has hidden dependencies"

**Use Cases**:
- Test before committing or sharing publicly
- Validate no hidden dependencies on local environment
- Verify cleanup behavior (no leftover files/processes)
- Catch environment-specific bugs

## Quick Decision Matrix

| Request | Mode | Isolation Level |
|---------|------|-----------------|
| "test in worktree" | Git Worktree | Fast, lightweight |
| "test in docker" | Docker | Full OS isolation |
| "test in vm" | VM | Complete isolation |
| "test skill X" (unspecified) | Auto-detect | Based on skill risk |

## Risk-Based Auto-Detection

| Risk Level | Criteria | Recommended Mode |
|------------|----------|------------------|
| Low | Read-only, no system commands | Git Worktree |
| Medium | File creation, bash commands | Docker |
| High | System config changes, VM ops | VM |

## Mode 1: Git Worktree (Fast)

**Best for**: Low-risk skills, quick iteration

**Process**:
1. Create isolated git worktree
2. Install Claude Code
3. Copy skill and run tests
4. Cleanup

**Workflow**: `modes/mode1-git-worktree.md`

## Mode 2: Docker Container (Balanced)

**Best for**: Medium-risk skills, full OS isolation

**Process**:
1. Build/pull Docker image
2. Create container with Claude Code
3. Run skill tests with monitoring
4. Cleanup container and images

**Workflow**: `modes/mode2-docker.md`

## Mode 3: VM (Safest)

**Best for**: High-risk skills, untrusted code

**Process**:
1. Provision VM, take snapshot
2. Install Claude Code
3. Run tests with full monitoring
4. Rollback or cleanup

**Workflow**: `modes/mode3-vm.md`

## Test Templates

Production-ready templates in `test-templates/`:

| Template | Use For |
|--