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.
Profile →npx skills add xuzhougeng/wisp-science --skill remote-compute-modal --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. Do not submit, build, monitor, or claim to reuse a Modal image. 2. 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 load `remote-compute-ssh` and submit a persisted Run. 3. Keep large inputs and model weights remote. Stage only small project scripts and configuration with `input_paths`. 4. 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 to do
What does the remote-compute-modal skill do?
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.
How do I install it?
Run `npx skills add xuzhougeng/wisp-science --skill remote-compute-modal --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From xuzhougeng/wisp-science, a repository with 895 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.