mcpbeat

Probe Compute Environment

xuzhougeng/probe-compute-environment

Inspect a registered execution server before compute planning and interpret its persisted capability profile. Use when a server is added, when the user clicks Probe, before enabling an unfamiliar SSH/WSL resource, or when deciding whether GPU, sudo/root, a scheduler, Python, R, conda, mamba, or environment modules are available.

504 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
859
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/xuzhougeng/wisp-science --skill probe-compute-environment

The instruction itself

1 sections, as written by the author

Probe compute environment

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:

  • Treat persisted capabilities as the server contract until it is probed again.
  • Treat gpu_summary: null as no usable GPU. Plan CPU work and never add

CUDA/GPU flags speculatively.

  • Treat 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.

  • Use a detected scheduler rather than running long work on a login node.
  • Use the recorded interpreter paths and environment managers. Do not assume

python, Rscript, conda, mamba, or modulecmd exists when absent.

  • If the probe failed, inspect the saved error and ask the user to check the

connection before manually probing again. Never loop or automatically retry

an SSH probe. If it is merely stale relative to a server change, probe again

before submitting work.

How to use it

Copy the folder

Take xuzhougeng/probe-compute-environment from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.