Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aipoch/remote-compute-ssh
Evaluate and use SSH Remote Compute before choosing where to run GPU, high-memory, parallel, batch, model-inference, bioinformatics, or other long-running scientific work; supports short remote commands and asynchronous jobs with automatic harvest and analysis.
Passed 17 of 21 test cases with the skill, and 3 of 21 without it.
and 21 more in the full report
16 fixed4 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
During the analysis turn for completed job `job-501`, I want to publish `summary.csv` using `write_artifact_file`. The result object `r` has `r.producer_run_id` set to `'notebook-run-8821'`. Should I generate a new UUID or pass `r.producer_run_id` when registering the artifact?
| Checked | Without skill | With skill |
|---|---|---|
| Directs passing r.producer_run_id as producerRunId in the write_artifact_file payload. | Missed | Passed |
| Explains that using producer_run_id preserves execution lineage across analysis turns. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill covers remote compute over SSH, including direct execution and Slurm submission:
listing hosts, creating handles, running short remote commands (callCommand), reading/writing host
knowledge docs, and the full async job lifecycle — submit → save job_id → read non-blocking
snapshots by that ID →
harvest → analysis turn → publish artifacts.
Where host.compute runs: host.compute lives ONLY on the control-plane REPL kernel — run
every example below with the repl_execute tool (JavaScript), the same kernel that hosts
host.mcp. The python/r data kernels have NO host.compute (SSH and approvals stay outside
the sandbox workspace); calling it from a python/r cell will fail with host.compute is undefined.
Only Compute Hosts enabled for this Session are visible or callable. Discover them in one catalog;
each entry has role selected or available. A non-empty selected pool is an execution instruction:
run tool-backed task work on one or more selected hosts as the task requires. The pool has no
priority and does not imply automatic multi-host scheduling. If no host is selected, choose from the
available entries. Read details() only for candidates that need closer evaluation.
Never guess or reuse a provider id absent from the catalog. A user naming a disabled host does not make it callable; explain that it must first be enabled for this Session. If no eligible host is usable, explain the blocker and ask the user how to proceed.
const hosts = await host.compute.listHosts()
const selectedHosts = hosts.filter((host) => host.role === 'selected')
const candidates = selectedHosts.length > 0 ? selectedHosts : hosts
Each list item is a compact summary with provider_id, display_name, shape, execution_mode,
status, and role
(last_probe_ok, probe_failed, or not_probed). last_probe_ok means the most recent persisted
Probe succeeded; it does not assert live connectivity. Knowledge documents and resource probe
snapshots are deliberately excluded from discovery results.
// List this Session's enabled hosts as one role-bearing compact catalog
const hosts = await host.compute.listHosts()
test cases passed, vs 3 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.