此技能用于扫描本地目录。

This skill's purpose (listing files and sizes) lines up with its code, but there are red flags you should address before using it: - index.js uses a hardcoded python path and an absolute script location in /home/jiajiexu/... instead of the bundled scripts/file_scanner.py. That will likely break or point to an unexpected file. Require the author to change scriptPath to use a path relative to the skill (e.g., __dirname + '/scripts/file_scanner.py') and avoid hardcoding /usr/bin/python3 (or at least fall back to 'python3' on PATH). - The Python script logs every invocation and the provided path to /tmp/openclaw_python_debug.log. This file can leak filesystem paths or be read by others on a multi-user system. If you care about privacy, ask to remove or disable logging or write to a controlled location. - index.js builds a table expecting a 'type' field that the Python script does not return; this mismatch may cause incorrect output. Ask the author to align returned JSON with the consumer code. - Because the package source is 'unknown' and the code references another user's home path, treat this as untrusted until corrected. Prefer running it in a sandbox or requesting a corrected release that uses relative paths and documents its logging behavior. If you don't trust the author or cannot get a corrected package, do not install it system-wide. If you proceed, inspect and modify index.js to use the included scripts/ path and remove or secure the debug logging.

Type: OpenClaw Skill Name: folder-inspector Version: 1.0.0 The `index.js` file contains a critical shell injection vulnerability. The `execSync` call directly interpolates the user-provided `args.path` into a shell command without proper sanitization, allowing arbitrary command execution on the host system. While the skill's stated purpose is benign (folder inspection), this severe lack of input validation makes the skill highly exploitable, classifying it as suspicious rather than benign. The `file_scanner.py` script also includes a debug log that writes to `/tmp/openclaw_python_debug.log`, which is a minor information leakage risk but not the primary concern.