Ssh Remote Control

This skill does what it says — it teaches the agent to SSH into remote machines and run commands — but that requires giving the agent access to a private SSH key (SSH_KEY_PATH). Before installing or enabling: 1) Verify the skill source/repository and maintainers (the registry lists an unknown source). 2) Do NOT reuse an existing key: create a dedicated SSH key pair for this skill and grant the remote account minimal permissions (non-admin user, limited sudo if any). 3) Restrict the key in authorized_keys (command=, no-pty, from=) and consider a passphrase + ssh-agent or an SSH certificate with short lifetime. 4) Keep the private key file permission-restricted (600) and ensure the platform will not leak it in logs or to other skills. 5) Resolve the metadata mismatch (the registry claims no required env vars but the skill expects several) — ask the publisher to correct packaging. 6) If you plan to allow autonomous agent actions, limit scope (dedicated account, strict remote-side command restrictions) because the agent can execute arbitrary commands once it has key access. If you cannot enforce these mitigations or verify the publisher, treat the skill as high-risk and do not provide access to sensitive keys or privileged accounts.