migratelisted

# migrate — AI settings migration (plugin distribution) Migrate another tool's settings into **whichever tool this skill is currently running in**. This distribution is installed through a plugin marketplace, and both Claude Code and Codex CLI install the same package without conversion. That is why the destination is not fixed here — step 0 determines it. (Cursor and Grok install via the repository's `./install.sh <dest>`, which uses destination-specific entry points instead.) ## 0. Resolve inputs ### 0-1. Determine the destination (do this first) The destination is **the tool you are running inside** — not the tool whose directory this file happens to sit in. Getting this wrong writes settings into the wrong home, so treat it as the highest-risk decision in the whole run. **The skill directory path is a hint, not proof.** Several tools load other tools' skill directories for compatibility — Grok Build reads `~/.claude/skills/` and `~/.codex/skills/`, and Cursor reads `.claude/skills/` and `.codex/skills/`. So a path containing `.claude` can perfectly well be running inside Grok or Cursor. Determine it this way: 1. Form a hypothesis from the skill directory path (`.claude` → claude, `.codex` → codex). 2. **Verify the hypothesis against the session you are actually in.** Ask yourself which tool's runtime you are executing under — the name of the product in your own system context, the tool set you were given, the slash-command namespace you were invoked through (a com