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, but **do not trust it blindly**. When this skill is driven from a main session, `CLAUDE_PLUGIN_DATA` may be set to a *different* plugin's data dir (observed in the wild as `.../data/codex-openai-codex`). Before using it, confirm its basename begins with `claude-prospector-` — i.e. it is *this* plugin's data dir. The marketplace suffix may legitimately differ (`-glitchwerks` for the public install, or another suffix for a local/forked marketplace), so match the `claude-prospector-` prefix, **not** a hardcoded marketplace. If `CLAUDE_PLUGIN_DATA` is unset, empty, or its basename belongs to a *different* plugin, ignore it and compute the default instead (using the canonical `glitchwerks` marketplace slug): ``` ~/.claude/plugins/data/claude-prospector-glitchwerks/ ``` The slug is `<plugin>-<marketplace>` — `claude-prospector` published from the `glitchwerks` marketplace — 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 fr