Hyperliquid CLI (with HIP3 Support)

What to consider before installing: - The SKILL.md requires installing 'hyperliquid-cli' globally and setting HYPERLIQUID_PRIVATE_KEY (a raw private key). The registry metadata you saw earlier did not list these — treat that mismatch as a red flag and verify the skill metadata/source. - Before running 'npm install -g hyperliquid-cli', check the npm package page and GitHub repo (https://github.com/chrisling-dev/hyperliquid-cli) for: author identity, recent commits, issues, and whether the published package matches source code. Prefer packages with many users and clear provenance. - Never paste your main trading private key into prompts or export it permanently until you trust the package. Prefer using a scoped/trading-only API key or a testnet key for initial testing. Consider using an address with limited funds or a hardware wallet/isolated VM. - Inspect ~/.hyperliquid after use to see what data is stored; remove keys when not needed. Avoid persisting secrets as environment variables in long-lived shells if you can. - Because the package runs code on install and offers a background server that keeps keys in memory/disk, run it in an isolated environment (container or VM) until you audit it. - If you want to proceed: test with --testnet and a limited key, review the package contents locally (npm pack / inspect), and confirm the published package source matches the GitHub repo and expected maintainer.