Probe Compute Environment Agent Skill

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

files

instructions only

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.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

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.