remote-ssh-bridge
v0.1.3Standard SSH command templates for a remote operator machine (bird reads, Puppeteer runs, inbox-style messaging).
⭐ 0· 467·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The name/description (SSH templates for remote ops) matches the included scripts and instructions: both scripts use ssh to run placeholder remote commands. However the skill does not declare the REMOTE_TARGET environment variable it requires (SKILL.md and scripts both expect REMOTE_TARGET), which is an inconsistency between claimed requirements and actual runtime needs.
Instruction Scope
SKILL.md limits activity to SSH to a REMOTE host and the scripts follow that. However scripts interpolate user-provided MESSAGE directly into a remote shell command without sanitization, which can allow arbitrary remote command injection if messages contain special characters. The instructions also give the agent broad discretion to 'fill placeholders' — that could lead to unintended remote commands if not reviewed.
Install Mechanism
No install spec and only two small shell scripts are included; nothing is downloaded or written to disk by an installer. This is low-risk from an install perspective.
Credentials
The skill declares no required environment variables, but both SKILL.md and the scripts rely on REMOTE_TARGET (and recommend keeping credentials in env variables). The missing declaration is a mismatch that reduces transparency. No other credentials are requested, which is proportionate, but the omission should be fixed.
Persistence & Privilege
always is false, the skill is user-invocable, and it doesn't modify other skills or system-wide config. It does enable remote execution via SSH (its stated purpose) but asks for no persistent elevated privileges on the local agent.
What to consider before installing
This skill is a small collection of SSH command templates and appears to do what it says, but there are practical problems you should fix before using it: (1) The scripts expect REMOTE_TARGET but the skill metadata doesn't declare it — set REMOTE_TARGET explicitly (e.g., export REMOTE_TARGET="user@host") and verify it points to the correct host. (2) The message script interpolates MESSAGE into a remote shell command without escaping; if the agent or other automation supplies message text, a crafted message could execute arbitrary commands on the remote host. Mitigations: sanitize/escape message input or pass the message via stdin (e.g., echo "$MESSAGE" | ssh "$REMOTE_TARGET" 'some-safe-handler'), or use printf '%s' with proper quoting on the remote side. (3) Replace the placeholder defaults (neill@<YOUR_REMOTE_HOST>) with no default or a clearly documented required variable to avoid accidental connections. (4) Only run this skill when you have reviewed the exact remote command placeholders and you trust the source of any messages passed to it. If you plan to allow autonomous agent invocation, restrict or validate message inputs to avoid accidental remote command execution.Like a lobster shell, security has layers — review code before you run it.
latestvk97dwy2vss836d5n1yfqk0faex81yjx8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.