GMGN Skill Cooking

⚙️ Configuration

cooking stats: Only GMGN_API_KEY required

cooking create: Both GMGN_API_KEY and GMGN_PRIVATE_KEY must be configured in ~/.config/gmgn/.env. The private key must correspond to the wallet bound to the API Key.

gmgn-cli installed globally — if missing, run: npm install -g gmgn-cli

IMPORTANT — Credential lookup order: gmgn-cli loads ~/.config/gmgn/.env first, then overlays any .env found in the current working directory (project-level overrides global). If credentials appear missing or wrong, check whether a .env in the workspace directory is shadowing the global config:

ls -la .env 2>/dev/null && echo "WARNING: local .env is overriding ~/.config/gmgn/.env"

If a local .env exists but lacks GMGN_API_KEY / GMGN_PRIVATE_KEY, either add them to that file or remove it so the global config is used.

📋 Tips & Best Practices

cooking create uses critical auth (API Key + signature) — CLI handles signing automatically.

cooking stats uses normal auth (API Key only — no private key needed).

The new token's mint address is in output_token from gmgn-cli order get, not in the initial cooking create response.

Use --raw on any command to get single-line JSON for further processing.