remote-server
Skill4 starsChanged 6 months agoMITView on GitHub
Manage remote Linux servers via SSH. Use when the user wants to: connect to a remote server via SSH, configure SSH keys and ~/.ssh/config, transfer files with scp/rsync, run long-running background jobs with screen/tmux/nohup, monitor progress of remote tasks, or retrieve results from a remote server. Triggers on mentions of remote server, SSH, scp, rsync, screen, tmux, nohup, background jobs on a server, or connecting to GPU/compute servers.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- illsdsd/claude-skillstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- illsdsd/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- af3cliSkill
- alphafold3Skill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 103
Connection: Always test SSH connectivity first before attempting file transfer or execution
- Very specific: line 104
File transfer: Ask the user for the remote path.
- Very specific: line 105
Background jobs: Always use screen/tmux/nohup — never run long tasks in foreground over SSH
- Distinctive: line 107
Progress check: Use minimal SSH commands (check for output files, tail logs) rather than attaching to sessions
- Distinctive: line 108
Error handling: If SSH fails, suggest checking connectivity, key permissions, and firewall rules before retrying
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Remote Server
Connect to remote Linux servers, transfer files, and manage long-running background jobs for scientific computing and machine learning workloads.
Prerequisites
- SSH client (
ssh,scp) — pre-installed on macOS/Linux - rsync — recommended for efficient file transfer
- screen or tmux — for persistent background sessions
- SSH access to the remote server (hostname/IP, username, authentication)
Core Workflow
Local Machine Remote Server
│ │
① SSH 连接 ────────────────────────────────▶
② 上传文件 (scp/rsync) ─────────────────────▶
③ 启动后台任务 (screen/tmux/nohup) ─────────▶
④ 告知用户预计完成时间,断开连接
│ │ ... 任务运行中 ...
⑤ 用户稍后要求检查进度
│ ssh <host> "ls /path/output/" ──────▶ 检查输出文件
│ 结果已出 / 仍在运行 │
⑥ scp <host>:/path/output/* ./ ────────────▶ 下载结果Quick Reference
SSH Connection
ssh user@host # Direct
ssh -i ~/.ssh/id_rsa user@host # With key
ssh -o ConnectTimeout=5 user@host "uptime" # Test connectionSee references/ssh-connection.md for config, key setup, and jump hosts.
File Transfer
# Upload single file
scp input.json user@host:/path/to/dir/
# Upload directory (recursive)
scp -r data/ user@host:/path/to/dir/
# Efficient sync (skip unchanged files, resume partial transfers)
rsync -avzP input.json user@host:/path/to/dir/
# Write file content directly via SSH
ssh user@host "cat > /path/to/input.json" < input.json
# Download results
scp user@host:/path/to/output/*.cif ./
rsync -avzP user@host:/path/to/output/ ./output/See references/file-transfer.md for details.
Background Jobs
# screen — start detached session
ssh user@host "screen -dmS af3 bash -c 'docker run ... 2>&1 | tee /tmp/af3.log'"
# tmux — start detached session
ssh user@host "tmux new-session -d -s af3 'docker run ... 2>&1 | tee /tmp/af3.log'"
# nohup — simplest, no session management needed
ssh user@host "nohup docker run ... > /tmp/af3.log 2>&1 &"See references/background-jobs.md for session management and reattachment.
Progress Monitoring
# Check if job is still running
ssh user@host "pgrep -a docker"
# View recent log output
ssh user@host "tail -50 /tmp/af3.log"
# Check for output files (indicates completion)
ssh user@host "ls -la /path/to/output/*.cif 2>/dev/null && echo DONE || echo RUNNING"
# Check tmux/screen session status
ssh user@host "screen -ls"
ssh user@host "tmux ls"See references/progress-monitoring.md for polling strategies and notifications.
Agent Behavior Guidelines
- Connection: Always test SSH connectivity first before attempting file transfer or execution
- File transfer: Ask the user for the remote path; default suggestions for AF3:
~/.af_input/for input,~/.af_output/for output - Background jobs: Always use screen/tmux/nohup — never run long tasks in foreground over SSH
- After launching: Tell the user the estimated completion time and that they can ask to check progress later
- Progress check: Use minimal SSH commands (check for output files, tail logs) rather than attaching to sessions
- Error handling: If SSH fails, suggest checking connectivity, key permissions, and firewall rules before retrying
References in This Skill
references/ssh-connection.md— SSH config, key authentication, jump hosts, connection testingreferences/file-transfer.md— scp, rsync, sftp, direct file writing, downloading resultsreferences/background-jobs.md— screen, tmux, nohup, session management, log managementreferences/progress-monitoring.md— Polling strategies, log inspection, completion detection, notifications
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

