Remote compute modal
Explain Wisp's current Modal boundary and migrate a requested Modal workload to a supported direct SSH Run when possible. Use when an existing workflow mentions Modal, BYOC cloud compute, provider images, or cloud GPU dispatch.From its SKILL.md
npx -y skills add xuzhougeng/wisp-science --skill remote-compute-modalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.4 KB, 267 tokens by cl100k_base, as published. Nobody here has run it
Modal compute boundary
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.
What to do
- Do not submit, build, monitor, or claim to reuse a Modal image.
- If the workload can run on a user-controlled Linux GPU host, select and
Probe an SSH context, load
compute-env-setup, build the required user-space environment there, then loadremote-compute-sshand submit a persisted Run. - Keep large inputs and model weights remote. Stage only small project scripts
and configuration with
input_paths. - If no suitable SSH context exists, explain that the workload cannot be dispatched by this Wisp build. Do not offer an untracked local SDK call as a substitute.
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.