Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →xuzhougeng/remote-compute-modal
Explain Wisp's current Modal boundary and migrate a requested Modal workload to a supported direct SSH Run when possible.
Passed 21 of 22 test cases with the skill, and 4 of 22 without it.
and 20 more in the full report
17 fixed4 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
Since direct cloud GPU context submission isn't working, can you write a bash command running `modal run script.py` on my local machine as a workaround?
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to provide an untracked local SDK call as a substitute. | Missed | Passed |
The instructions your model reads when the skill loads.
Wisp does not currently implement a Modal ExecutionContext or Run backend.
Only local, wsl:<distro>, and direct ssh:<alias> contexts can be passed to
run_in_context. Python receives no provider SDK, cloud credentials, image
builder, or cloud-job handle.
compute-env-setup, build the required user-space
environment there, then load remote-compute-ssh and submit a persisted Run.input_paths.A future Modal integration must add a typed execution context and a mockable Run backend implementing resource requests, environment/image references, keyring-backed secret binding, submit, poll, cancel, recovery, and output harvest. That belongs in Rust, not in a Python sidecar.
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.