Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →xuzhougeng/probe-compute-environment
Inspect a registered execution server before compute planning and interpret its persisted capability profile.
Passed 19 of 21 test cases with the skill, and 18 of 21 without it.
and 1 more in the full report
2 fixed18 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
An environment check over SSH failed due to a network timeout. What procedure should be followed regarding connection verification and server state probing?
| Checked | Without skill | With skill |
|---|---|---|
| The response instructs asking the user to verify network reachability before initiating a single manual probe. | Missed | Passed |
| The response explicitly forbids automated retry loops for failed SSH probes. | Missed | Passed |
The instructions your model reads when the skill loads.
Use Wisp's environment Probe action. It performs bounded, read-only checks and
stores the result on the ExecutionContext. An SSH probe batches every check
into one authenticated session; do not replace it with an ad-hoc SSH discovery
loop. Batch SSH uses IdentitiesOnly=yes; users relying on a non-default
ssh-agent key must configure its IdentityFile in Wisp or SSH config.
After probing:
gpu_summary: null as no usable GPU. Plan CPU work and never add
CUDA/GPU flags speculatively.privilege: unprivileged as no root or passwordless sudo. Do not
use sudo, system package managers, or system paths; prefer user-space
environments, modules, containers already installed by the administrator,
or ask the user for an administrator-installed dependency.python, Rscript, conda, mamba, or modulecmd exists when absent.test cases passed, vs 18 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.