Skills ssh
📦
ssh
Content revision r1 Critical ⚙️ External commands🌐 Network access📁 Filesystem access
Manage SSH Workflows Safely
Remote server access often requires exact SSH syntax and careful key handling. This skill provides practical SSH patterns for connections, transfers, tunnels, jump hosts, and troubleshooting.
Supports: Claude Codex Code(CC)
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "ssh" from https://skillstore.io/skills/dicklesworthstone-ssh.md and its manifest at https://skillstore.io/api/skills/dicklesworthstone-ssh/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "ssh". I need to copy a file to a server.
Expected outcome:
The skill recommends an SCP upload pattern with placeholders for the local file, remote user, host, and destination path.
Using "ssh". I need to access a remote database locally.
Expected outcome:
The skill explains a local SSH tunnel and identifies which local port maps to the remote database endpoint.
Using "ssh". My SSH host key changed.
Expected outcome:
The skill shows how to remove a stale known_hosts entry and reminds the user to verify the new host fingerprint.
Security Audit
Criticalv10 • 7/9/2026 Open versioned report
Most static hits are Markdown examples for standard SSH administration, not executable code or hidden malware. The remaining confirmed risks involve sensitive SSH key paths, ssh-agent usage, host trust file changes, tunneling, and agent forwarding that require explicit user authorization and safer guidance.
1
Files scanned
247
Lines analyzed
11
Review items
0
False positives ignored
Confirmed security concerns (11)
Critical
SSH directory access
ssh -i ~/.ssh/my_key user@hostname
The example uses a private SSH key path under ~/.ssh for authentication. This is expected SSH usage but involves sensitive credential material.
Critical
SSH directory access
IdentityFile ~/.ssh/myserver_key
The config example points IdentityFile at ~/.ssh, which identifies private credential material. This is expected SSH usage but security-sensitive.
Critical
SSH directory access
ssh-add ~/.ssh/id_ed25519
The command loads ~/.ssh/id_ed25519 into ssh-agent. This directly operates on a private key file and is security-sensitive.
Critical
SSH directory access
ssh-add --apple-use-keychain ~/.ssh/id_ed25519
The command loads ~/.ssh/id_ed25519 into ssh-agent and the macOS keychain. This directly operates on a private key file and is security-sensitive.
Critical
SSH directory access
ssh-keyscan hostname >> ~/.ssh/known_hosts
The command writes scanned host keys into ~/.ssh/known_hosts. This changes SSH trust decisions and can be dangerous without fingerprint verification.
Critical
SSH private key file
ssh-add ~/.ssh/id_ed25519
The example directly references ~/.ssh/id_ed25519, a common SSH private key file. Any automated handling of this path requires explicit user authorization.
Critical
SSH private key file
ssh-add --apple-use-keychain ~/.ssh/id_ed25519
The example directly references ~/.ssh/id_ed25519, a common SSH private key file. Adding it to an agent or keychain is credential-sensitive.
High
SSH host/auth files
ssh-keyscan hostname >> ~/.ssh/known_hosts
The example appends to known_hosts, an SSH host authentication file. Trust file changes should verify the host fingerprint first.
Show all 11 confirmed findings
High
Agent Forwarding Enabled in Example Configuration
The SSH config example sets ForwardAgent yes. Agent forwarding can expose the local SSH agent to a compromised remote host and should be disabled unless explicitly needed.
The exact configuration directive is present and is a known SSH security risk when used broadly.
High
Host Key Trust Added Without Verification
The known_hosts example pipes ssh-keyscan output directly into the trust file. This can trust an attacker-controlled key during a man-in-the-middle attack if fingerprints are not verified out of band.
The command directly appends scanned host keys to known_hosts and the surrounding text does not instruct fingerprint verification.
Medium
Remote Port Forwarding Can Expose Local Services
The remote forwarding example maps a local service to a remote port. This is legitimate SSH behavior but can unintentionally expose local development services to users on the remote host.
The example clearly documents ssh -R remote forwarding; exposure depends on server policy and bind settings.
Capability review items (11)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
SOCKS proxy
# Use localhost:1080 as SOCKS5 proxy
The skill intentionally documents dynamic SOCKS tunneling, which can route browser or application traffic through a remote host. This is legitimate SSH usage but can bypass network controls if used without authorization.
High
Hidden file in home directory
ssh -i ~/.ssh/my_key user@hostname
The command references an SSH identity file under ~/.ssh, which is sensitive local credential material. The example is legitimate SSH usage, but it can cause an agent to operate on private key paths.
High
Hidden file in home directory
IdentityFile ~/.ssh/myserver_key
The config example references an IdentityFile under ~/.ssh, which is sensitive credential material. The usage is expected for SSH, but it still directs access to private key paths.
High
Hidden file in home directory
ssh-add ~/.ssh/id_ed25519
The ssh-add example loads a private key from ~/.ssh into the agent. This is a sensitive credential operation even though it is normal SSH practice.
High
Hidden file in home directory
ssh-add --apple-use-keychain ~/.ssh/id_ed25519
The macOS keychain example loads a private key from ~/.ssh into ssh-agent. This is a sensitive credential operation involving private key material.
High
Hidden file in home directory
ssh-keyscan hostname >> ~/.ssh/known_hosts
The command appends host key material into ~/.ssh/known_hosts. Modifying SSH trust files is security-sensitive and should include fingerprint verification.
Medium
Hidden file access
ssh -i ~/.ssh/my_key user@hostname
The command accesses an SSH identity path in a hidden home directory. This is legitimate but security-sensitive because it uses private key material.
Medium
Hidden file access
IdentityFile ~/.ssh/myserver_key
The config entry accesses an SSH identity path in a hidden home directory. This is legitimate but security-sensitive because it points to private key material.
Medium
Hidden file access
ssh-add ~/.ssh/id_ed25519
The ssh-add command accesses a private key path in ~/.ssh. Loading keys into an agent is security-sensitive even when user authorized.
Medium
Hidden file access
ssh-add --apple-use-keychain ~/.ssh/id_ed25519
The ssh-add keychain command accesses a private key path in ~/.ssh. Loading keys into an agent is security-sensitive even when user authorized.
Medium
Hidden file access
ssh-keyscan hostname >> ~/.ssh/known_hosts
The command writes to ~/.ssh/known_hosts, changing local SSH host trust state. This is legitimate but should not be automated without validation.
Risk Factors
⚙️ External commands (50)
SKILL.md:13-15 SKILL.md:15-18 SKILL.md:18-20 SKILL.md:20-23 SKILL.md:23-25 SKILL.md:25-30 SKILL.md:30-32 SKILL.md:32-35 SKILL.md:35-42 SKILL.md:42-45 SKILL.md:45-47 SKILL.md:47-52 SKILL.md:52-54 SKILL.md:54-57 SKILL.md:57-59 SKILL.md:59-62 SKILL.md:62-64 SKILL.md:64-69 SKILL.md:69-71 SKILL.md:71-74 SKILL.md:74-76 SKILL.md:76-79 SKILL.md:79-81 SKILL.md:81-86 SKILL.md:86-88 SKILL.md:88-91 SKILL.md:91-93 SKILL.md:93-96 SKILL.md:96-98 SKILL.md:98-101 SKILL.md:101-103 SKILL.md:103-108 SKILL.md:108-111 SKILL.md:111-114 SKILL.md:114-117 SKILL.md:117-120 SKILL.md:120-123 SKILL.md:123-126 SKILL.md:126-129 SKILL.md:129-134 SKILL.md:134-136 SKILL.md:136-139 SKILL.md:139-141 SKILL.md:141-144 SKILL.md:144-149 SKILL.md:149-154 SKILL.md:154-156 SKILL.md:156-159 SKILL.md:159-161 SKILL.md:161-164
🌐 Network access (3)
Detected Patterns
SSH directory access×5SSH private key file×2
Audited by: claude View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dicklesworthstone-ssh/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dicklesworthstone-ssh?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dicklesworthstone-ssh?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dicklesworthstone-ssh/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dicklesworthstone-ssh.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Dicklesworthstone. (2026). ssh security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dicklesworthstone-ssh/audits/10BibTeX citation
@techreport{dicklesworthstone-dicklesworthstone-ssh-2026,
author = {Dicklesworthstone},
title = {ssh security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/dicklesworthstone-ssh/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ssh security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "Dicklesworthstone"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/dicklesworthstone-ssh/audits/10"
identifiers:
- type: other
value: "skillstore:dicklesworthstone-ssh:audit:10"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 55
Architecture
85
Maintainability
87
Content
70
Community
83
Spec Compliance
What You Can Build
Connect to production hosts
Use host aliases, custom ports, and identity files to connect to approved servers with repeatable commands.
Transfer release artifacts
Copy files or synchronize directories with SCP and rsync while preserving a clear command history.
Debug private services through tunnels
Create local or jump-host tunnels to inspect databases, web services, or admin tools behind private networks.
Try These Prompts
Connect to a server
Show me the SSH command to connect to user@hostname on the default port. Explain each part briefly.
Copy a directory safely
Give me an rsync command to copy ./local/ to user@host:/remote/path/. Include a dry-run command first.
Create a jump-host tunnel
Help me connect to an internal server through a bastion host using SSH ProxyJump. Use placeholders for all hostnames.
Review my SSH configuration
Review this SSH config for security risks, especially agent forwarding, key paths, multiplexing, and host key handling.
Best Practices
- Confirm authorization before connecting to any host or creating any tunnel.
- Verify host fingerprints before adding keys to known_hosts.
- Use passphrase-protected Ed25519 keys and avoid broad agent forwarding.
Avoid
- Do not run private-key commands without explicit user confirmation.
- Do not add ssh-keyscan output to known_hosts without verification.
- Do not use tunnels to bypass organizational network policy.
Frequently Asked Questions
Does this skill connect to servers automatically?
No. It provides command patterns. Users must authorize and run commands in their own environment.
Can it help with SSH keys?
Yes. It shows key generation, ssh-copy-id, and ssh-agent patterns, but private key handling needs explicit care.
Does it support file transfer?
Yes. It includes SCP and rsync examples for uploads, downloads, recursive copies, and dry runs.
Can it create SSH tunnels?
Yes. It covers local, remote, dynamic SOCKS, and jump-host forwarding patterns.
Is agent forwarding safe?
Agent forwarding can be risky on untrusted hosts. Enable it only for specific trusted systems when required.
Should I verify known_hosts entries?
Yes. Verify host key fingerprints through a trusted channel before adding or replacing known_hosts entries.
Developer Details
Author
DicklesworthstoneLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
1ffa7643651792ccb4bd3b15d924d2c97edff755
Maintenance freshness
7/18/2026
Usage
17 downloads · 210 views
File structure
📄 SKILL.md