setup-prospectorlisted

# Setup claude-prospector This skill materialises the plugin-owned Python venv that the plugin's hooks need to run `claude-prospector` as a subprocess. Run it once after first install and after any plugin version update. ## Step 1: Resolve `${CLAUDE_PLUGIN_DATA}` Read the `CLAUDE_PLUGIN_DATA` environment variable. If unset, compute the default: ``` ~/.claude/plugins/data/claude-prospector-claude-prospector/ ``` The slug is the plugin ID `claude-prospector@claude-prospector` with every character outside `[a-zA-Z0-9_-]` replaced by a hyphen. Create the directory if it does not exist. ## Step 2: Discover Python Find a Python ≥ 3.10 interpreter using this probe chain (stop at first success): 1. `flag.interpreter` from the prior `setup-state.json` (if a flag exists from a previous run, try that interpreter first). 2. `$CLAUDE_PROSPECTOR_BOOTSTRAP_PYTHON` environment variable (absolute path). 3. `py -3` (Windows only). 4. `python3` 5. `python` Probe each candidate with: ``` <candidate> -c "import sys; sys.exit(0 if sys.version_info >= (3, 10) else 1)" ``` If all candidates fail, ask the user: > "No Python ≥ 3.10 interpreter found. Please provide an absolute path to > a Python 3.10+ executable, or set CLAUDE_PROSPECTOR_BOOTSTRAP_PYTHON." ## Step 3: Wipe the existing venv If `${CLAUDE_PLUGIN_DATA}/venv/` exists, remove it entirely: ``` shutil.rmtree(<plugin_data>/venv) ``` This is always-wipe-first (spec D4). A partial venv from a failed previous run is handled correc