openclaw-server-secure-skill
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only server-hardening guide, but it includes powerful admin commands and external software installs that should be reviewed before running.
Install only if you intentionally want this agent to help harden a server. Before running the commands, verify SSH key access, keep a recovery console available, confirm the Tailscale and Telegram identities, and validate the external install sources.
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.
If these commands are run on the wrong server or before confirming SSH/Tailscale access, the user could lose remote access or disrupt services.
The guide instructs the agent/user to run privileged commands that alter SSH login behavior and firewall policy. This is expected for server hardening, but a mistake can lock out remote access.
sudo sed -i 's/^#*PasswordAuthentication .*/PasswordAuthentication no/' /etc/ssh/sshd_config ... sudo ufw default deny incoming ... sudo ufw enable
Review each command before running it, confirm key-based SSH works, and keep console or provider recovery access available before enabling restrictive firewall rules.
The server will run installer code obtained from external package sources, so a compromised or unexpected package source could affect the host.
The instructions rely on executing a remote install script and installing an unpinned global npm package. These are purpose-aligned installation steps, but they require trusting external sources.
curl -fsSL https://tailscale.com/install.sh | sh ... npm install -g openclaw && openclaw doctor
Verify the official Tailscale install instructions and OpenClaw npm package before running, and pin versions or use trusted package repositories where practical.
Using the wrong Tailscale account or Telegram ID could expose access to the wrong person or prevent the real owner from managing the agent.
The setup links the server to a Tailscale identity and configures Telegram owner access. This is expected for the stated purpose, but the identity values determine who can reach or control the installation.
sudo tailscale up ... Wait for user to authenticate the Tailscale link ... Ask the user for their Telegram ID ... "allowFrom": ["YOUR_TELEGRAM_ID"]
Authenticate only to the intended Tailscale tailnet and independently verify the Telegram ID before applying the allowlist configuration.