Agent skill · security · aiskillstore
openclaw-secure-linux-cloud
Use when self-hosting OpenClaw on a cloud server, hardening a remote OpenClaw gateway, choosing between SSH tunneling, Tailscale, or reverse-proxy exposure, or reviewing Podman, pairing, sandboxing, token auth, and tool-permission defaults for a secure personal deployment.
Why this skill is useful
Provides specific hardening procedures and configurations for securely deploying OpenClaw on Linux cloud servers that the AI wouldn't reliably generate on its own.
What it needs
Requires podman installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
OpenClaw Secure Linux Cloud Overview Use this skill for the conservative "deploy first, expose later" pattern for OpenClaw on a cloud server. Default to a private control plane: Harden the Linux host before exposing anything. Keep the gateway bound to 127.0.0.1. Reach the Control UI through an SSH tunnel first. Keep token authentication, pairing, and sandboxing enabled. Start with a narrow tool profile and loosen only with an explicit need. This skill is for secure Linux cloud hosting. If the user only wants the fastest generic OpenClaw install on a local machine, prefer the official OpenClaw onboarding docs instead of forcing this flow. Open references/REFERENCE.md when you need the command matrix, baseline config shape, checklist, or access-path comparison. When To Use Use this skill when the user mentions any of the following: OpenClaw on a cloud server, VM, or other Linux host Secure self-hosting, hardening, or "run it privately" Podman, loopback binding, SSH tunneling, or remote Control UI access Tailscale vs reverse proxy for OpenClaw Pairing, sandboxing, token auth, or locked-down tool permissions Reviewing whether an existing OpenClaw host is too exposed Do not use this skill for: General Linux hardening with no OpenClaw component Local single-machine onboarding where remote access is irrelevant Pure local onboarding with no remote-host hardening questions Non-Linux hosting unless the user explicitly wants this Linux-first pattern adapted Workflow 1. Classify the request Put the task in one of these buckets before giving detailed guidance: 1. Fresh deploy: the user wants to stand up OpenClaw securely on a Linux cloud host from scratch. 2. Hardening review: the user already has OpenClaw running and wants to reduce exposure or audit risky defaults. 3. Access-model decision: the user is choosing between SSH tunneling, Tailscale, or a reverse proxy. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/openclaw-secure-linux-cloud