V2ray Proxy
Analysis
The proxy-management behavior mostly matches the stated purpose, but the skill should be reviewed because its command wrapper can execute arbitrary shell syntax and it makes broad local process and shell-startup changes.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
wrap() {
local cmd="$*"
...
eval "$cmd"
...
eval "$cmd" || result=$?
}The wrapper builds a single shell string from all supplied arguments and executes it with `eval`; this is an unbounded command-execution path inside a proxy-management skill.
pkill -f "xray.*config" || true pkill -f "v2rayN" || true
Stopping the proxy is expected, but these broad process-name matches can terminate any matching Xray/V2Ray/v2rayN process rather than only a process started by this script.
echo "# V2Ray Proxy (managed by OpenClaw)" >> ~/.bashrc echo "export V2RAY_PROXY=1" >> ~/.bashrc
The script automatically appends a persistent environment marker to the user's shell startup file when enabling the proxy.
V2RAY_DIR="/media/felix/d/v2rayN-linux-64" ... cd "$V2RAY_DIR" nohup ./v2rayN > /dev/null 2>&1 &
The skill runs an external local executable from a hard-coded, user-specific path that is not included in the skill package.
