V2rayn

Manage V2RayN on macOS to list nodes, test proxy connections, check current node status, view logs, and support auto-failover via scripted health checks.

This skill appears coherent for managing a local macOS V2RayN client, but take these precautions before installing/running the suggested script: 1) Inspect the check_v2rayn.sh contents yourself — it reads your V2RayN config file (which may contain server addresses and credentials) and writes a log under $HOME/.openclaw/logs. 2) If you enable the cron job, create the log directory with restrictive permissions (chmod 700) to avoid exposing logs to other local users. 3) Prefer using macOS-native scheduling (launchd) if you want better control and visibility than cron. 4) Do not run the script as root; run it as your user. 5) If you are uncomfortable with automatic reads of your config file, perform the checks manually instead. Overall, the skill is consistent with its stated purpose, but the user is responsible for safely creating the script and the scheduled job.

Type: OpenClaw Skill Name: v2rayn Version: 1.0.0 The skill is designed to manage the V2RayN proxy client on macOS, including status checks, node listing, connection testing, and application restart. All code snippets access local V2RayN configuration files, test connectivity to `google.com` (either direct or via proxy), and manage the V2RayN application process. While it instructs the agent to set up a cron job for periodic health checks, the associated script (`check_v2rayn.sh`) is benign, only performing local checks and logging. There is no evidence of data exfiltration, malicious execution, obfuscation, or prompt injection attempts to subvert the agent's purpose.