Skill Safe Install

Skills 安全安装工具 - 整合 Vetter 代码审查 + ClawHub 评分 + ThreatBook 沙箱扫描三层验证

This skill appears to do what it says (local vetting + ClawHub rating + ThreatBook sandbox), but it will package and upload entire skill code to a third‑party service. Before installing, consider: 1) Do not alias/overwrite your `clawhub` command system-wide until you’ve tested the script — that alias would make every install automatically upload code to ThreatBook. 2) Review scripts/safe-install.mjs yourself to confirm exactly what is uploaded and whether temporary directories are cleaned. 3) Be careful about placing sensitive or proprietary skills behind this flow; the tool warns not to upload secrets, but it is your responsibility to prevent that. 4) The README suggests echoing the API key into ~/.openclaw/.env — ensure your runtime actually loads that file or export the env var in your shell/CI so the script can authenticate. 5) Use --dry-run first and run the tool in a controlled environment (non-prod user) to observe behavior. If you must use it in CI, restrict the scanned artifacts to non-sensitive samples or ensure ThreatBook usage complies with your privacy policies.

Type: OpenClaw Skill Name: skill-safe-install Version: 2.0.1 The skill's stated purpose is to enhance security by vetting other skills, which is benign. However, the `scripts/safe-install.mjs` script uses `child_process.execSync` to execute `clawhub` commands with user-provided `skillName` input. Although the `skillName` is double-quoted, this is insufficient to prevent shell injection if a malicious `skillName` contains crafted characters (e.g., `"; evil_command; echo "`). This constitutes a critical shell injection vulnerability (RCE risk) that could allow an attacker to execute arbitrary commands on the system, classifying the skill as suspicious despite its benevolent intent.