Analyze Hyperliquid market data and provide trading insights. Real-time price monitoring, trend analysis, and risk assessment.

This skill appears to do what it says (calls Hyperliquid API and parses results), but there are several things to check before installing: - Source and provenance: There is no homepage or source. Ask the publisher for a repository or documentation so you can inspect what will be called and how data is handled. - Wallet privacy: The skill asks for a wallet address (declared as primaryEnv). A wallet address is not a secret key but can be used to fetch on-chain holdings and link activity to you. Only provide it if you trust api.hyperliquid.xyz and the skill owner. - Missing API key declaration: SKILL.md mentions HYPERLIQUID_API_KEY as optional but it is not declared in the registry metadata. If you plan to use an API key, insist it be declared and scoped with least privilege. - Network behavior & polling: The notes on 5-second refreshes imply frequent outbound requests. If you allow autonomous invocation, consider the privacy and rate-limit implications; consider limiting autonomous runs or disabling autonomous invocation until you verify behavior. - Verify endpoints manually: Run the provided curl commands yourself to inspect responses and ensure no unexpected data exchange happens before granting any env vars. Given these inconsistencies and privacy implications, proceed cautiously: request source code or a homepage, confirm how the wallet address is used/stored/transmitted, and avoid putting sensitive credentials into the environment until you can verify the implementation.

Type: OpenClaw Skill Name: hyperliquid-analyzer Version: 1.0.0 The skill bundle appears benign. It uses `curl` and `jq` to fetch market data from `https://api.hyperliquid.xyz`, which aligns with its stated purpose of analyzing Hyperliquid market conditions. The `SKILL.md` file describes the skill's features and provides example commands that are consistent with data retrieval, without any evidence of prompt injection, data exfiltration, or other malicious activities. The mention of an optional `HYPERLIQUID_API_KEY` is for 'authenticated requests', a plausible feature for a market analysis tool, and is not misused in the provided examples.