setup-envlisted

# Setup Env **Announce at start:** "I'm using the bridge:setup-env skill to [export/install] this Claude Code environment's plugins." ## Purpose Claude Code plugins/marketplaces are installed per-machine in `~/.claude/plugins/`. There's no built-in way to carry "everything I have installed" from one machine to another. This skill closes that gap in two directions: **export** snapshots the current machine's user-scope plugins and marketplaces (plus the separately-installed `gstack` skill suite) into a manifest file; **install** reads that manifest on a different machine and reproduces the setup by driving the real `claude plugin` CLI. This only covers **user-scope** plugins (`scope: "user"` in `~/.claude/plugins/installed_plugins.json`) — plugins installed per-project (`scope: "project"`/`"local"`) belong to that project's own setup, not the user's personal environment, and are deliberately excluded. ## Step 1 — Determine Mode If the user's request doesn't already make it obvious, ask (via `AskUserQuestion`) whether this is: - **Export** — snapshot this machine's current setup to a manifest file - **Install** — read an existing manifest and set this machine up to match ## Step 2 — Export 1. Read `~/.claude/plugins/installed_plugins.json`. Filter to entries where at least one install record has `"scope": "user"`. 2. Read `~/.claude/plugins/known_marketplaces.json` to resolve each plugin's marketplace alias (the part after `@` in its key, e.g. `context-mode@context-mode`