install-skills

# Install Skills Configuration Tool

Configure skills by asking the user for their preferences and updating the skill files accordingly.

## Arguments

- `$0` (optional): Skill name to configure. If not provided, configure all available skills that need setup.

## Supported Skills

### Build Skill

The `build` skill can be configured with:

1. **Build directory pattern**: Where builds are stored relative to workspace
   - **Always prompt with at least these options:**
     - `build/${buildType}` (e.g., `build/Debug`, `build/Release`) - Recommended
     - `build` (single build directory)
   - Additional optional patterns:
     - `cmake-build-${buildType}` (CLion style)
     - Custom pattern

2. **Default build type**: What build type to use when not specified
   - Options: `Release`, `Debug`, `RelWithDebInfo`, `ASAN`, `TSAN`, `MSAN`, `UBSAN`

3. **Default target**: What to build by default
   - Common targets: `clickhouse`, `clickhouse-server`, `clickhouse-client`, or build all

### Test Skill

The `test` skill can be configured with:

1. **Build directory pattern**: Where to find the clickhouse binary for testing
   - Should match the build skill configuration
   - Used to set PATH for test runner
   - **Always prompt with at least:** `build/${buildType}` and `build`

2. **Default build type for testing**: Which build to use when running tests
   - Options: `Release`, `Debug`, `RelWithDebInfo`, `ASAN`, `TSAN`, etc.
   - Typically the same as the build skill default

## Configuration Process

1. **Identify the skill to configure:**
   - If `$ARGUMENTS` is provided, configure that specific skill
   - Otherwise, configure all available skills that need setup (build and test together)

2. **When configuring both build and test skills together:**
   - Ask all questions upfront (build directory, default build type, default target)
   - Use the same answers to configure both skills
   - The test skill will use the same build directory and default build type as the build sk