Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-03 | ✗→✓ | ▲ Improved | -39% | 0% |
| case-01 | ✗→✓ | ▲ Improved | -55% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -59% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -45% | 0% |
| case-09 | ✗→✓ | ▲ Improved | -63% | 0% |
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.
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.
and configuration with input_paths.
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.
Other measured skills in the registry, with their headline benchmark lift.