Ssh Exec

Run a single command on a remote Tailscale node via SSH without opening an interactive session.

This skill is coherent for running single SSH commands, but before installing: 1) Confirm you trust the skill owner — the skill will (per its instructions) use your local SSH keys or SSH agent socket if available, which are sensitive. 2) Ask the owner/maintainer to update metadata to declare the env vars/config it uses (SSH_AUTH_SOCK, SSH_HOST/PORT/TARGET) so you can make an informed decision. 3) If you enable the skill, avoid exposing broad credentials: use a dedicated, limited SSH key and targets restricted server-side (authorized_keys forced-commands or limited user accounts). 4) Be cautious about allowing autonomous invocation — an agent could run arbitrary commands on remote hosts accessible via your SSH credentials. 5) If unsure, test in an isolated environment or refuse to provide SSH_AUTH_SOCK or private keys.

Type: OpenClaw Skill Name: ssh-exec Version: 1.0.0 The `ssh-exec` skill is classified as suspicious due to its inherent high-risk capabilities. It explicitly requires access to SSH keys in `~/.ssh/` or `SSH_AUTH_SOCK` and facilitates remote command execution, including piping local scripts for remote execution, as demonstrated in `SKILL.md`. While these capabilities are aligned with the stated purpose of an SSH execution skill, they represent significant security risks if misused, granting broad shell and network access. There is no evidence of intentional malicious behavior such as data exfiltration or persistence mechanisms within the skill definition itself.