Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →xuzhougeng/remote-compute-ssh
Submit recoverable SSH-direct research Runs with live progress cards and model-free monitoring.
Passed 15 of 21 test cases with the skill, and 5 of 21 without it.
and 12 more in the full report
11 fixed6 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to transfer large datasets directly between ssh:server-a and ssh:server-b. The user approved establishing permanent direct SSH trust between the servers. What setup step should be called first?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends calling configure_ssh_trust before transferring. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill after choosing an ssh:<alias> execution context. Wisp owns the
job lifecycle locally: run_in_context creates the Run record, stages explicit
inputs with persisted byte progress, and starts a detached supervisor on the server.
The Runs panel and SQLite record remain authoritative if the conversation ends
or Wisp restarts.
run_in_context calls for read-only discovery such as
nvidia-smi -L, which python3, or module avail. Free-form shell SSH is
disabled. Use the interpreter path reported by the context probe; do not
assume a python alias exists when the probe found python3.run_in_context call. Include environment
activation in the command so the Run is reproducible.monitor_run with the
returned Run id. Wisp inserts a live card in the conversation, suspends
the tool without additional model calls, and resumes the same agent turn
with the terminal result. If the result has wait_interrupted: true, the
remote process is still running: answer the user from the snapshot, then
call monitor_run again with the same id. Do not resubmit. Use cancel_run
only when the user asked to stop. For fire-and-forget work, report the Run id
and end the turn instead.get_run only for one explicit status snapshot; never call it repeatedly
to wait. Use cancel_run when the user asks to stop.Never monitor a Run with Start-Sleep, sleep, ssh ... ps, kill -0, a
shell polling loop, nohup, background &, or hand-written PID files. Those
duplicate the control plane and can strand the agent turn. A transient SSH
error is stored as last_poll_error; do not resubmit, because Wisp retries the
same idempotent remote handle.
{
"context_id": "ssh:gpu-box",
"title": "Motif enrichment across 2,000 backgrounds",
"command": "source ~/miniforge3/etc/profile.d/conda.sh && conda activate genomics && python motif_enrichment_analysis.py",
"timeout_secs": 14400,
"input_paths": ["scripts/motif_enrichment_analysis.py"]
test cases passed, vs 5 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.