Source profileQuality 61/100

xuzhougeng/wisp-science/skills/probe-compute-environment/SKILL.md

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.

Source repository stars
560
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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; user…

Best for

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

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/xuzhougeng/wisp-science --skill "skills/probe-compute-environment"
Safe inspection promptEditorial

Inspect the Agent Skill "probe-compute-environment" from https://github.com/xuzhougeng/wisp-science/blob/95d2c13d1665d46a388b5bdc998dcce0d5ec2eee/skills/probe-compute-environment/SKILL.md at commit 95d2c13d1665d46a388b5bdc998dcce0d5ec2eee. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

The source does not provide enough structured workflow evidence for a step-by-step guide.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score61/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars560SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
xuzhougeng/wisp-science
Skill path
skills/probe-compute-environment/SKILL.md
Commit
95d2c13d1665d46a388b5bdc998dcce0d5ec2eee
License
AGPL-3.0
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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:

  1. Treat persisted capabilities as the server contract until it is probed again.
  2. Treat gpu_summary: null as no usable GPU. Plan CPU work and never add CUDA/GPU flags speculatively.
  3. 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.
  4. Use a detected scheduler rather than running long work on a login node.
  5. Use the recorded interpreter paths and environment managers. Do not assume python, Rscript, conda, mamba, or modulecmd exists when absent.
  6. 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.

Alternatives

Compare before choosing

Computed 9831,966

K-Dense-AI/scientific-agent-skills

dask

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

Computed 9831,966

K-Dense-AI/scientific-agent-skills

medchem

Medicinal chemistry filters for compound triage. Apply drug-likeness rules (Lipinski, Veber, CNS), structural alert catalogs (PAINS, NIBR, ChEMBL), complexity metrics, and the medchem query language for library filtering.

Computed 9831,966

K-Dense-AI/scientific-agent-skills

neurokit2

Use NeuroKit2 to build or audit reproducible research workflows for physiological time-series preprocessing, event/interval analysis, multimodal alignment, variability, and complexity. Trigger when code imports neurokit2 or needs its current APIs, schemas, and method-aware validation—not for diagnosis or device validation.

Computed 97234,327

affaan-m/ECC

plan-orchestrate

Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts. Generative only — never invokes /orchestrate itself. Use when the user has a multi-step plan and wants to drive it through orchestrate without composing chains by hand.