Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Forecast Valuation

v1.0.0

专业财务预测与估值模型生成器。结合高盛 DCF 标准与 Wind Evaluator 框架,自动生成完整三表预测、DCF 估值、相对估值、敏感性分析和 Football Field 估值区间。

0· 50·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description (financial forecasting & valuation) align with the included scripts: build_forecast.py and configure.py implement Excel model generation and a configuration prompt for data-source API keys (Gangtise/Tushare). Dependencies listed (pandas, openpyxl, requests, numpy) are appropriate for the task. Minor mismatch: SKILL.md lists extra functionality (build_dcf.py, build_comps.py, test_connection.py, upload-to-Baidu) that are referenced but not present in the file manifest.
!
Instruction Scope
SKILL.md instructs running multiple helper scripts (build_dcf.py, build_comps.py, test_connection.py) and an upload option, but only build_forecast.py and configure.py are bundled. configure.py prompts for and writes API keys into a config.json in the repo root — this is within the skill's operational scope but is a credential-handling decision that broadens the runtime data surface. The instructions assume network access to fetch market data (e.g., risk-free rate) but the provided code is truncated, so exact network calls are not fully visible.
Install Mechanism
No install spec is provided (instruction-only plus a couple of scripts). This is low-risk in terms of automatic downloads or arbitrary code fetch during install. The runtime will execute bundled Python scripts, which will write files locally; there is no external installer URL or archive to review.
!
Credentials
The skill declares no required environment variables, yet its configuration and code expect API credentials (GANGTISE_ACCESS_KEY, GANGTISE_SECRET_KEY, TUSHARE_TOKEN) to be stored in config.json. Storing secrets in a local JSON file (by default saved in the skill tree) is a security consideration and is inconsistent with the declared empty requires.env. The number and kind of credentials requested are proportionate to the described data sources, but the storage method and missing explicit declare of required secrets are concerning.
Persistence & Privilege
The skill does not request elevated platform privileges and always:false. It writes a config.json into the skill directory and writes output to a hard-coded OUTPUT_DIR (/root/.openclaw/workspace) by default — that may be surprising for some environments and could create files under /root. It does not request to modify other skills or system-wide settings.
What to consider before installing
Things to consider before installing or running this skill: - The main functionality (creating Excel valuation models) is implemented in the included build_forecast.py; that matches the description. However the README/SKILL.md references other helper scripts (build_dcf.py, build_comps.py, test_connection.py) that are not present. Ask the author for the missing scripts or avoid commands that call them. - The configure.py will prompt you to enter API keys and will save them into a local config.json file inside the skill directory. If you provide real API keys, they will be stored on disk in plaintext — consider using temporary/test keys, storing secrets in a secure location, or editing the script to read from protected environment variables instead. - The script defaults OUTPUT_DIR to /root/.openclaw/workspace. Running as a non-root user may fail or will create files under /root; check and change OUTPUT_DIR before running if needed. - The code uses network-capable libraries (requests) and SKILL.md says it will fetch market data (10-year yield) and pull from Gangtise/Tushare. Review the remaining (truncated) portions of build_forecast.py to confirm which external endpoints it contacts, and whether any endpoints are unexpected. Run the code in a sandboxed environment (isolated VM or container) if you cannot verify those calls first. - No automated installer downloads code from arbitrary URLs (good), but because this skill comes from an unknown source (no homepage) you should inspect the complete scripts locally before executing them. If you decide to use the skill, prefer manual credential handling (do not reuse high-value production keys) and limit file permissions on config.json (chmod 600) or move secrets into environment variables/secret manager.

Like a lobster shell, security has layers — review code before you run it.

latestvk970ynn0h7gzhx8q9bq91g9awx84b2kz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📊 Clawdis

Comments