Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Quant Analyst
v0.1.1Professional quantitative trading system for cryptocurrency - backtesting, paper trading, live trading, and strategy optimization
⭐ 0· 444·9 current·9 all-time
byJustin Liu@zhenstaff
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The primary SKILL.md and SKILL-ZH.md describe a quantitative trading tool and instruct cloning https://github.com/ZhenRobotics/openclaw-quant and installing Python deps—this is coherent with the stated purpose. However, SKILL-EN.md is for a completely different 'video-generator' skill (different repo, different env var: OPENAI_API_KEY) bundled into the same package. That file is unrelated to quant-analyst and suggests a packaging/misconfiguration or intentional bundling of unrelated capabilities.
Instruction Scope
The runtime instructions tell the agent/user to git clone external repositories and run project scripts (pip install -r requirements.txt, run python -m openclaw_quant, and in the English file run ~/openclaw-video/generate-for-openclaw.sh). Those commands will fetch and execute third-party code on the user's machine. The SKILL.md examples reference reading env vars (BINANCE_API_KEY/SECRET and use of os.getenv) even though the declared skill metadata lists no required env vars. The presence of unrelated instructions (video-generator) increases risk that the agent may run commands outside the intended domain.
Install Mechanism
No formal install spec is declared (instruction-only), which is lower baseline risk for the platform, but the instructions require cloning GitHub repos and running pip/npm installs. The repos referenced are hosted on GitHub (reasonable), but cloning and running install scripts pulls arbitrary code from an external source into the user's environment and may execute scripts that are not pre-vetted. The package contains two different repo targets (openclaw-quant and openclaw-video).
Credentials
Declared metadata lists no required env vars, but the instructions and examples explicitly advise setting BINANCE_API_KEY and BINANCE_API_SECRET (for live trading) and SKILL-EN.md requests OPENAI_API_KEY. This mismatch is a red flag: the skill will operate with credentials but does not declare them, so a user or automated installer may not be warned. Live trading also implies use of exchange API keys—users must ensure keys are limited (no withdrawal) and prefer testnet keys for initial use.
Persistence & Privilege
The skill does not request always:true, does not declare special config paths, and is install-free at platform level. It can be invoked autonomously (platform default) and contains AUTO-TRIGGER keywords, which is expected for agent-facing skills. There is no evidence the skill attempts to modify other skills or system-wide settings.
Scan Findings in Context
[no_regex_findings] expected: The static regex scanner had no findings because this skill is instruction-only and contains no executable code files for the scanner to analyze. That absence is not evidence of safety—review of the remote repositories the instructions clone is required.
What to consider before installing
Proceed cautiously. The quant-analyst instructions themselves are consistent with a trading tool, but:
- There is an unrelated SKILL-EN.md (video-generator) bundled in the same package — ask the publisher why unrelated skill docs are included.
- The skill's metadata declares no required env vars but the instructions expect BINANCE_API_KEY/SECRET (and the English file expects OPENAI_API_KEY). Treat this as a mismatch and assume the skill will ask for credentials.
- Before running any git clone / pip install or executing scripts from the repos, manually inspect the GitHub repositories (openclaw-quant and openclaw-video) and review scripts such as generate-for-openclaw.sh and any startup hooks. Check recent commits, contributors, and issues.
- Never supply exchange API keys with withdrawal permissions. Use read-only or testnet API keys and start with paper trading only.
- Run installations and live tests in an isolated environment (VM or container) until you verify the code.
- Prefer skills with a trustworthy homepage or known maintainer. If you can't verify the upstream repositories or get a clear explanation for the bundled video doc, consider not installing.Like a lobster shell, security has layers — review code before you run it.
latestvk970gj7mnba3t7rexfhvvfdhf182bymm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.