# Remote Compute

Use when the user asks to run, submit, monitor, or cancel a job on a remote machine...

- Repository: https://github.com/ai4s-research/open-science (2069 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add ai4s-research/open-science --skill remote-compute -g -a claude-code -y`
Codex: `npx skills add ai4s-research/open-science --skill remote-compute -g -a codex -y`
Cursor: `npx skills add ai4s-research/open-science --skill remote-compute -g -a cursor -y`
Gemini CLI: `npx skills add ai4s-research/open-science --skill remote-compute -g -a gemini-cli -y`

## Description

Use when the user asks to run, submit, monitor, or cancel a job on a remote machine over SSH, their own GPU/CPU server, a workstation, or a Slurm cluster ("the cluster", a login node, "my 3090 box", "the compute server"). Picks a saved machine, runs the work directly over SSH (or via Slurm when present), tracks it, and fetches results back into the workspace.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Remote compute over SSH

Run heavy work on the user's own machines over SSH with their own keys or their
own interactive sign-in, you never install anything remote and never handle
credentials yourself. A machine may be a plain server (CPU or GPU, no scheduler)
or a Slurm cluster.

## 0 · Always run ssh through the app's config

Every `ssh`, `scp` and `rsync` below passes `-F "$OPENSCIENCE_SSH_CONFIG"`. Write
it as `$SSHCFG` after defining it once per command you send:

```bash
SSHCFG="${OPENSCIENCE_SSH_CONFIG:+-F $OPENSCIENCE_SSH_CONFIG}"
```

That config makes your connection reuse the one the app already authenticated,
which is what lets clusters with two-factor authentication work at all: the user
signs in once, and every command after that needs no password or code. Without
it, such a host refuses every command you send.

### When a host asks for credentials

Many institutional clusters require a password or a one-time code on EVERY new
connection. If a command fails with a permission or authentication error
(`Permission denied`, `no supported authentication methods`), do NOT retry, and
do not report the failure yet: call the **`ssh_connect`** tool with that host.
It asks the desktop UI to prompt the user, and returns once the shared
connection is up, then retry your command unchanged.

Two errors that sign-in cannot fix, so do not call the tool for them: a host-key
error (`Host key verification failed`, the user must verify the fingerprint in
their own terminal once) and a network error (unreachable, timed out, unknown
host).

## 1 · Pick the machine

The rest: https://github.com/ai4s-research/open-science/blob/HEAD/runtime/skills/core/remote-compute/SKILL.md