by 安全扫描
OpenClaw
安全
high confidenceThe skill's instructions, required tools, and scope match its stated purpose (remote exec and file transfer via node protocol or SSH) and do not ask for unrelated credentials or installs.
评估建议
This skill is coherent with its stated purpose, but before installing: ensure your node is actually paired and you have appropriate SSH access (keys/config); be aware restarting the remote OpenClaw service requires admin rights on the node; verify the openclaw CLI you run is from a trusted source; test commands on a non-production node first to avoid accidental service disruption.详细分析 ▾
✓ 用途与能力
Name/description (remote exec + file transfer) aligns with the SKILL.md: it documents node protocol for exec and SSH (ssh/scp/rsync) for fallback and transfer. The declared required tools (ssh, scp, rsync, openclaw CLI) are appropriate for this purpose.
✓ 指令范围
Instructions are narrowly focused on running commands and transferring files between gateway and paired node. They do not request unrelated system files, global environment variables, or external endpoints. Note: the doc assumes the operator has SSH access and may need administrative rights on the remote node to restart the OpenClaw node service.
✓ 安装机制
No install spec or code files — instruction-only. This is low-risk since nothing is fetched or written by an install step.
✓ 凭证需求
No environment variables, credentials, or config paths are requested. Use of SSH keys and the openclaw CLI is expected and proportional to the functionality.
✓ 持久化与权限
Skill is not forced always-on. It allows autonomous invocation (platform default) but that is not combined with broad credentials or system-wide modifications, so no elevated persistence concerns.
安全有层次，运行前请审查代码。
运行时依赖
无特殊依赖
版本
latestv1.0.12026/4/3
Added required tools, homepage, license. Removed privileged command references.
● 可疑
安装命令 点击复制
官方npx clawhub@latest install remote-node-ssh
镜像加速npx clawhub@latest install remote-node-ssh --registry https://cn.clawhub-mirror.com
技能文档
Run commands on a paired OpenClaw node from your gateway. Node protocol when connected, SSH when not.
Setup: Node must be paired first. See hybrid-gateway.Required Tools
This skill expects the following on your gateway machine:
ssh,scp,rsync— standard SSH tooling for fallback transport and file transferopenclawCLI — for node protocol commands and node status checks
Your remote node needs an SSH server running and an OpenClaw node agent paired to your gateway.
When to Use What
| Need | Transport |
|---|---|
| Run a command | exec host=node (node protocol) |
| Full shell env (brew, nvm, pyenv) | SSH with shell rc sourcing |
| Transfer files | SSH (scp / rsync) |
| Node disconnected | SSH |
| Long-running task | SSH + nohup or tmux |
Node Protocol
Fastest path. Routes through the gateway — no SSH keys needed.
exec host=node command="uname -a"
Caveat: Minimal PATH. Use full binary paths for package-manager-installed tools:
exec host=node command="/opt/homebrew/bin/python3 --version"
SSH Fallback
Use your SSH config alias (the hostname or alias you configured in your SSH config for the node).
ssh "whoami"
With full shell environment:
ssh "source ~/.profile 2>/dev/null; node --version"
File Transfer (SSH only)
# To node
scp file.txt :/tmp/# From node
scp :/tmp/result.txt ./
# Sync a directory
rsync -avz ./data/ :~/data/
Check Node Status
openclaw nodes status
Disconnect Recovery
- Check:
openclaw nodes status - If disconnected, verify the node is reachable via SSH:
ssh"echo ok" - If reachable, restart the OpenClaw node service on the remote machine using its service manager
- Verify:
openclaw nodes status
Constraints
- Node protocol: no file transfer, no TTY/interactive sessions, minimal PATH
- SSH: requires network reachability (LAN, Tailscale, or VPN)
- Long tasks: use SSH +
nohup/tmuxto avoid timeouts
数据来源：ClawHub ↗ · 中文优化：龙虾技能库
OpenClaw 技能定制 / 插件定制 / 私有工作流定制
免费技能或插件可能存在安全风险，如需更匹配、更安全的方案，建议联系付费定制