WQBuddy

WorldQuant BRAIN Alpha挖掘协作专家。引导用户从模糊想法到可提交Alpha的全流程：字段勘探、表达式构建、回测分析、优化迭代和提交管理。使用当用户需要回测Alpha、搜索BRAIN平台字段、批量测试表达式时。

This skill appears to implement a real BRAIN alpha workbench, but it asks to store your BRAIN username/password in a local JSON file and to modify OpenClaw's configuration (~/.openclaw/openclaw.json). Before installing: - Verify the npm package and GitHub repo contents yourself (review the code) and confirm the package author and integrity. Do not rely only on the SKILL.md claims. Check the npm package tarball and repository for unexpected network calls or code that reads other files. - Prefer using a dedicated/test BRAIN account (as the skill itself recommends). Treat the credentials as sensitive — consider using an OS credential store/secret manager rather than plaintext config.json. - Ask the publisher to explain why write access to ~/.openclaw/openclaw.json is required and whether the modification is minimal and reversible. If possible perform the plugin registration step manually rather than granting automatic write+restart. - Confirm the token cache implementation (.wq_token.json) and that tokens are not uploaded anywhere. The SKILL.md claims no external upload, but you should verify in the package code. - Request the registry owner to add an explicit install spec (npm/clawhub) in registry metadata to remove the inconsistency. If you cannot inspect the package or are uncomfortable granting platform-config write access, do not install or run with real production credentials.

Type: OpenClaw Skill Name: wqbuddy Version: 1.0.6 The wq-buddy skill bundle is designed to interact with the WorldQuant BRAIN platform, but it requires storing raw usernames and passwords in a local configuration file (~/.wq-buddy/config.json) because the platform lacks OAuth/API key support. While this behavior is documented and justified by the tool's purpose, the storage of plaintext credentials and the requirement to modify the global OpenClaw configuration (~/.openclaw/openclaw.json) represent significant security vulnerabilities. No evidence of intentional data exfiltration or malicious intent was found, but the high-risk credential handling and filesystem permissions align with the 'suspicious' classification.