Moltbot Security

Name and description claim security hardening for Moltbot/OpenClaw and the SKILL.md content indeed provides firewall, auth, permissions, Node.js updates, and Tailscale guidance — that aligns with the stated purpose. However, the package metadata claims no required config paths or env vars while the instructions explicitly reference ~/.openclaw/openclaw.json and several CLAWDBOT_* environment variables. This metadata/instruction mismatch is unexpected and deserves attention.

Instructions tell the operator to read and edit sensitive config files (~/.openclaw/openclaw.json), change file permissions, export secrets (CLAWDBOT_GATEWAY_TOKEN / CLAWDBOT_GATEWAY_PASSWORD), run firewall and sshd config changes, and run 'openclaw security audit --deep --fix'. Those actions are within a hardening guide's scope, but they are high-impact (modify system files, apply fixes automatically). The guide also recommends piping remote install scripts (Tailscale, NodeSource). Ensure you trust the sources before running them and verify the CLI tooling (openclaw) exists and is from a trusted origin.

The skill is instruction-only (no install spec), which is lower risk as nothing is written by the package manager. However, the instructions recommend running third-party install scripts (curl | sh for Tailscale and NodeSource), and a homebrew command for macOS; those are external downloads executed on the host and carry the usual supply-chain risk. The package.json references a GitHub repo, but registry metadata lists source/homepage as unknown/none — inconsistent provenance information.

The SKILL.md instructs you to set environment variables (CLAWDBOT_GATEWAY_TOKEN, CLAWDBOT_GATEWAY_PASSWORD, CLAWDBOT_DISABLE_BONJOUR) and to edit local config paths, which are reasonable for a gateway hardening guide. But the registry metadata declares no required env vars and no required config paths; this mismatch makes it unclear what secrets/config the skill expects or will operate on. No unrelated credentials are requested, but the lack of declared requirements reduces transparency.

The skill does not request persistent or privileged platform-level presence (always:false, no special flags). It instructs manual edits to user and system files (home config, /etc/ssh, ufw) which are expected for system hardening. It does not attempt to modify other skills or system agent configs automatically in the provided instructions.