VPS Agent Migration
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill matches its VPS migration purpose, but it asks the agent to handle SSH and Discord bot credentials and run privileged remote commands in unsafe ways.
Only use this skill if you understand and control the VPS. Before running it, verify the SSH host key, avoid inline passwords and tokens, back up local and remote OpenClaw configs, and be prepared to rotate the Discord bot token if it appears in shell history or logs.
Findings (3)
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.
The Discord bot token gives control over the bot account. If copied to the wrong server, exposed in shell history, or mishandled, the user may lose control of that bot identity.
The skill instructs the agent to read a local OpenClaw configuration file to obtain a Discord bot token and then place that token into the VPS configuration.
cat ~/.openclaw/openclaw.json | grep -A5 '"[Discord_ID]":' ... "token": "[Token]"
Treat the Discord token and SSH credentials as secrets. Prefer environment variables or a secrets manager, avoid pasting tokens directly into shell commands, verify the VPS owner and host key, and rotate the token if it may have been exposed.
A mistyped or spoofed VPS endpoint could receive credentials or sensitive configuration, and root-level commands could make broad changes on the remote system.
The documented SSH command uses an inline password, root login, and disables host-key verification, which weakens authentication and increases the chance of connecting to the wrong or intercepted host.
sshpass -p 'VPS密码' ssh -o StrictHostKeyChecking=no root@VPS_IP
Use SSH keys, keep host-key checking enabled, avoid root login where possible, and require explicit user confirmation before running remote configuration or restart commands.
If the Discord ID, agent ID, token, or VPS target is wrong, the bot may stop responding locally or route messages to the wrong remote agent.
The skill changes routing bindings, restarts the VPS gateway, and disables the local Discord account, which can affect where messages are handled.
openclaw config set bindings ... openclaw gateway restart ... openclaw config patch --json '{"channels": {"discord": {"accounts": {"[Discord_ID]": {"enabled": false}}}}}'Back up both local and VPS OpenClaw configs, verify IDs before applying changes, test with a noncritical agent first, and keep a rollback command ready.