Weex

This skill appears to be a real WEEX trading client (spot + futures) implemented as local Python scripts. Before installing or providing real API credentials: - Treat the registry metadata mismatch as a red flag: SKILL.md and the scripts require WEEX_API_KEY / WEEX_API_SECRET / WEEX_API_PASSPHRASE even though the registry lists none. Don’t rely solely on the registry declarations. - Do not provide your main account keys. Create a least-privilege API key for testing (disable withdrawals; limit permissions to read and trading only if needed). - Inspect the scripts yourself (they are included) to confirm there are no hardcoded exfil endpoints or logging of secrets. The provided files appear to call the weex.com API and fetch docs from weex.com — expected for this skill. - Test in dry-run / sandbox first: manually run the scripts locally with test keys or in a sandbox account to verify behavior. The SKILL.md expects the agent to include --confirm-live for mutating actions; be explicit in prompts and review generated CLI before execution. - Because the agent is responsible for mapping natural language to CLI flags, prefer explicit structured prompts (e.g., specify exact --confirm-live or --no-execute) and review any generated command before it runs. - If you plan to use this in an automated/agent setting, require an explicit confirmation step for any live trade, rotate keys if exposed, and consider running the skill in an isolated environment. If you want a cleaner integration: ask the skill author to update the registry metadata to declare the required env vars and set a primary credential, and to clarify the default/dry-run behavior to avoid ambiguity around live execution.