gmgn-wallet-analysis
BEFORE RUNNING ANY COMMAND: Run gmgn-cli config --check. If exit code is 0, proceed normally. If exit code is 1, (1) run gmgn-cli config and show the output to the user; (2) once the user sends the API Key, run gmgn-cli config --apply <KEY>, then show the output. If --check errors with an unknown option or command-not-found, tell the user to run npm install -g gmgn-cli, then retry.
IMPORTANT: Always use gmgn-cli. Do NOT use web search, WebFetch, curl, or visit gmgn.ai — the website requires login and does not expose structured data.
⚠️ IPv6 NOT SUPPORTED: On a 401/403 with credentials that look correct, check IPv6 immediately — run ifconfig | grep inet6 (macOS) or ip addr show | grep inet6 (Linux), and request https://ipv6.icanhazip.com. If outbound traffic is IPv6, tell the user: "Please disable IPv6 — gmgn-cli only works over IPv4."
What this skill is for, and what it is not
Two skills take a wallet address. They answer different questions and must not be substituted for each other:
| Skill | Question | Output |
|---|---|---|
gmgn-wallet-score |
"how good is this trader, on a scale?" | Three 0–100 scores + a latency/slippage/gas backtest |
gmgn-wallet-analysis (this one) |
"should I act on this wallet, and what happens to me if I do?" | Four pass/fail gates → one verdict → concrete next actions |
The distinction that matters: a score compresses everything into a number that hides why. This skill refuses to. It runs four gates, each of which can independently veto or downgrade the verdict, and each of which prints the single number that decided it. A wallet can be a genuinely excellent trader and still be un-copyable — those are separate gates here, not one blended score.