Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Secure outbound-only relay for remote OpenClaw control — no exposed ports, no SSH, no Telegram.
Secure outbound-only relay for remote OpenClaw control — no exposed ports, no SSH, no Telegram.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Enables secure remote communication between an OpenClaw instance and a relay server without exposing ports, requiring SSH, or relying on Telegram/Discord.
The PrivaClaw skill registers your local OpenClaw instance as a managed remote node on a relay network. Once connected, the node can receive prompts, execute workflows, report health, and be restarted — all through a secure, outbound-only WebSocket channel. This skill replaces external messaging-based control layers such as Telegram or Discord with a native, secure relay channel for OpenClaw interaction.
When the skill is enabled, the OpenClaw instance registers as a remote-capable node with the relay and maintains an active session. The node can be in one of three states: StateDescriptionOnlineAuthenticated and accepting relay commandsReconnectingConnection lost; auto-reconnecting with exponential backoffOfflineSkill disabled or relay unreachable after max retries Relay commands are only accepted while the node is authenticated and online. Commands received during reconnection are discarded by the relay.
CapabilityDescriptionremote_chatReceive and execute prompts remotely, streaming tokens back in real timeremote_statusReport node health: uptime, active tasks, last error, connection stateremote_restartSafely restart the OpenClaw process without manual intervention. Pending executions are cancelled and reported before restart occurs.remote_triggerExecute OpenClaw workflows/tasks triggered remotely Remote commands are limited to declared capabilities and cannot execute arbitrary system-level operations.
KeyRequiredDescriptionrelay_url✅WebSocket URL of the relay servernode_id✅Unique identifier for this OpenClaw nodeauth_token✅Secret token for authenticating with the relay
typeActionpromptExecute via OpenClaw prompt runner, stream response tokens backstatusReturn node health payloadrestartCancel pending tasks, report them, then gracefully restartworkflowExecute a named OpenClaw task/workflow
Heartbeat (every 15s): { "node_id": "...", "uptime": 3600, "active_tasks": 2, "last_error": null, "connection_state": "online" } Response stream: { "type": "token", "request_id": "...", "content": "..." } per token Response complete: { "type": "done", "request_id": "..." } Status: Full heartbeat payload with request_id
EndpointProtocolData SentData Receivedwss://<relay_url>/connectWebSocket (TLS)auth_token, node_id, heartbeat payloads, prompt response tokensRelay commands: prompt, status, restart, workflow No other external endpoints are contacted. All network activity is limited to the configured relay_url.
auth_token — sent once during the WebSocket handshake to authenticate the node node_id — sent with every heartbeat and response to identify the node Heartbeat data — uptime (seconds), active task count, last error string, connection state Prompt response tokens — streamed back to the relay in response to prompt commands Workflow completion status — success/error for triggered workflows
All local AI model execution and inference Local file system contents — never read or transmitted Environment variables (other than the three declared above) System information, IP addresses, or hardware details — never collected
Outbound only — the skill never opens a listening port or accepts inbound connections TLS encrypted — all WebSocket connections use wss:// (TLS 1.2+) No data persistence — the relay server does not store prompt content or response tokens; it forwards in real time
By installing this skill, you are connecting your OpenClaw instance to an external relay server at the configured relay_url. Prompt content and response tokens are transmitted through this relay in real time. Only install this skill if you trust the operator of the relay server. The default relay (wss://relay.privaclaw.com) is operated by the project maintainers.
Local AI execution continues even if the relay disconnects Relay does not expose the node to inbound traffic Remote actions are capability-scoped — only declared capabilities can be invoked Pending tasks are reported before any restart occurs — no silent failures
Easiest way — use the visual setup wizard: 👉 Open your dashboard and go to /skill/privaclaw to configure everything through the UI — generate a node ID, test your connection, and export your config in one place. Or configure manually: Add the skill to your OpenClaw instance Configure relay_url, node_id, and auth_token Start OpenClaw — the relay connection is established automatically
This skill replaces external messaging-based control layers such as Telegram or Discord with a native, secure relay channel for OpenClaw interaction. It is designed for teams and individuals who need reliable remote access to their OpenClaw nodes without exposing infrastructure.
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.