How do I install the Ssh Manager skill?

Run npx skillmds@latest add modbender/ssh-manager in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ssh Manager skill do?

Manage SSH connections, generate keys, organize config, and test remote server access. It is listed under Coding & Dev Tools on SkillMD.

Is Ssh Manager safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: WARNING, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ssh Manager?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ssh Manager free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ssh Manager?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ssh Manager by modbender — Agent Skill

Name: Ssh Manager
Rating: 4.2 (5 reviews)
Author: modbender

File contents

SSH Manager

Manage SSH connections, config, keys, and remote server access.

Requirements

ssh, ssh-keygen (pre-installed on Linux/macOS)
No API keys needed

Instructions

List connections — Parse and display ~/.ssh/config:
```
grep -E '^Host |HostName |User |Port |IdentityFile ' ~/.ssh/config 2>/dev/null
```
Format as a table: Alias | Hostname | User | Port | Key File

Add new host — Gather details and append to config:

Host myserver
    HostName 192.168.1.100
    User deploy
    Port 22
    IdentityFile ~/.ssh/id_ed25519

Always show the block and confirm before writing.

Edit host — Find the block, show current values, apply changes.
Remove host — Remove the Host block. Always confirm before deleting. Back up config first.
Generate SSH key:
```
ssh-keygen -t ed25519 -C "user@hostname" -f ~/.ssh/id_ed25519_myserver
```
Recommend Ed25519 over RSA. Suggest a passphrase for security.

Key audit — List keys and check permissions:

ls -la ~/.ssh/id_* 2>/dev/null
# Private keys must be 600, public keys 644
# ~/.ssh/ directory must be 700

Test connection:

ssh -o ConnectTimeout=5 -o BatchMode=yes myserver exit 2>&1 && echo "✅ OK" || echo "❌ Failed"

Input Validation

Before writing to SSH config, validate all values:

Hostname: ^[a-zA-Z0-9._-]+$ only
Username: ^[a-zA-Z0-9_-]+$ only
Port: numeric, 1–65535
Reject any input containing shell metacharacters (;, |, &, $, `)

Edge Cases

Config doesn't exist: Create ~/.ssh/config with chmod 644 and ~/.ssh/ with chmod 700.
Duplicate host alias: Warn user — SSH uses first match. Suggest renaming.
ProxyJump/bastion: Support ProxyJump directive for jump hosts.
Wildcard hosts: Be careful with Host * blocks — explain they apply globally.

Security

Never display private key contents — only reference file paths.
Back up ~/.ssh/config to ~/.ssh/config.bak before any modification.
Verify permissions after changes: chmod 700 ~/.ssh && chmod 644 ~/.ssh/config.
Recommend disabling password auth on servers (PasswordAuthentication no).
Suggest AddKeysToAgent yes for convenience with passphrase-protected keys.

---name: ssh-managerdescription: Manage SSH connections, generate keys, organize config, and test remote server access.--- # SSH Manager Manage SSH connections, config, keys, and remote server access. ## Requirements - `ssh`, `ssh-keygen` (pre-installed on Linux/macOS) - No API keys needed ## Instructions 1. **List connections** — Parse and display `~/.ssh/config`: ```bash grep -E '^Host |HostName |User |Port |IdentityFile ' ~/.ssh/config 2>/dev/null ``` Format as a table: Alias | Hostname | User | Port | Key File 2. **Add new host** — Gather details and append to config: ``` Host myserver HostName 192.168.1.100 User deploy Port 22 IdentityFile ~/.ssh/id_ed25519 ``` **Always show the block and confirm before writing.** 3. **Edit host** — Find the block, show current values, apply changes. 4. **Remove host** — Remove the `Host` block. **Always confirm before deleting.** Back up config first. 5. **Generate SSH key**: ```bash ssh-keygen -t ed25519 -C "user@hostname" -f ~/.ssh/id_ed25519_myserver ``` Recommend Ed25519 over RSA. Suggest a passphrase for security. 6. **Key audit** — List keys and check permissions: ```bash ls -la ~/.ssh/id_* 2>/dev/null # Private keys must be 600, public keys 644 # ~/.ssh/ directory must be 700 ``` 7. **Test connection**: ```bash ssh -o ConnectTimeout=5 -o BatchMode=yes myserver exit 2>&1 && echo "✅ OK" || echo "❌ Failed" ``` ## Input Validation Before writing to SSH config, validate all values: - **Hostname**: `^[a-zA-Z0-9._-]+$` only - **Username**: `^[a-zA-Z0-9_-]+$` only - **Port**: numeric, 1–65535 - **Reject** any input containing shell metacharacters (`;`, `|`, `&`, `$`, `` ` ``) ## Edge Cases - **Config doesn't exist**: Create `~/.ssh/config` with `chmod 644` and `~/.ssh/` with `chmod 700`. - **Duplicate host alias**: Warn user — SSH uses first match. Suggest renaming. - **ProxyJump/bastion**: Support `ProxyJump` directive for jump hosts. - **Wildcard hosts**: Be careful with `Host *` blocks — explain they apply globally. ## Security - **Never display private key contents** — only reference file paths. - Back up `~/.ssh/config` to `~/.ssh/config.bak` before any modification. - Verify permissions after changes: `chmod 700 ~/.ssh && chmod 644 ~/.ssh/config`. - Recommend disabling password auth on servers (`PasswordAuthentication no`). - Suggest `AddKeysToAgent yes` for convenience with passphrase-protected keys.

Frequently asked questions

Ssh Manager