Agent skill

Compute Env Setup

by xuzhougeng in xuzhougeng/wisp-science

Set up and validate a reproducible Python or R environment on a Wisp execution context.

Apache-2.0Auto-check passedTesting & QA

Install Compute Env Setup

skills CLI
$ npx skills add xuzhougeng/wisp-science --skill compute-env-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install xuzhougeng/wisp-science compute-env-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/xuzhougeng/wisp-science.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/compute-env-setup .claude/skills/compute-env-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
compute-env-setup
GitHub stars
1k
Token cost
~1.1k tokens
SKILL.md length
468 words
Files
2 (incl. references)
Skills in repo
25
Repo updated
First seen
Licence
Apache-2.0

At a glance

Set up and validate a reproducible Python or R environment on a Wisp execution context.

  • Works in 7 steps: Require a selected ssh: context with a… → If a scheduler is detected, stop. Do not… → Use at most a few bounded read-only… → …
  • A selected local
  • SKILL.md covers Plan the environment, Direct SSH workflow, Setup-script requirements and Local and WSL boundary, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Compute Env Setup is an agent skill from xuzhougeng/wisp-science. Set up and validate a reproducible Python or R environment on a Wisp execution context. Use for a selected local, WSL, or direct SSH context when installing scientific packages, configuring caches, recording interpreter activation, or producing an environment smoke test. Do not use for scheduler clusters or managed cloud providers that Wisp cannot track yet.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/envs_reference.md`).

It sits in Testing & QA, covering QA and bug reports. It works with Python. The repository describes itself as: Open-source, local-first desktop AI research workbench for scientific computing with Python/R, MCP bioinformatics tools, SSH/WSL/GPU runtimes, and OpenAI/Anthropic models. The licence is Apache-2.0.

When your agent uses it

  • A selected local
  • Direct SSH context when installing scientific packages
  • Configuring caches
  • Recording interpreter activation

Example prompts

  • “/compute-env-setup”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Require a selected ssh: context with a recent Probe result. Respect
  2. If a scheduler is detected, stop. Do not install or run long work on a
  3. Use at most a few bounded read-only shell commands to confirm free space,
  4. Write an idempotent project script such as
  5. Submit the setup script through one persisted Run
  6. Replace all example paths with probed absolute paths. Call monitor_run
  7. Record the validated activation command, versions, cache paths, GPU witness,

What it can do on your machine

Read from SKILL.md and the folder at commit b77b170. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Compute Env Setup loads about 1.1k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 468 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from xuzhougeng/wisp-science at commit b77b170, republished under its Apache-2.0 licence (© xuzhougeng). 468 words, ~1,071 tokens.

Download SKILL.mdSave it as .claude/skills/compute-env-setup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
compute-env-setup
description
Set up and validate a reproducible Python or R environment on a Wisp execution context. Use for a selected local, WSL, or direct SSH context when installing scientific packages, configuring caches, recording interpreter activation, or producing an environment smoke test. Do not use for scheduler clusters or managed cloud providers that Wisp cannot track yet.
license
Apache-2.0

Set up a compute environment

Treat the selected and probed ExecutionContext as authoritative. Wisp currently supports local, wsl:<distro>, and direct ssh:<alias> contexts; it does not expose an authenticated provider SDK inside Python.

Plan the environment

Define before installing:

  • Python or R version;
  • ordered conda/pip/R package phases with important pins;
  • required CUDA capability and minimum VRAM;
  • cache variables and durable weight locations;
  • import checks, CLI checks, and one seeded representative workload;
  • the exact activation command later Runs must include.

Use references/envs_reference.md for package-order and cache examples, but replace container-specific paths with paths valid on the selected context.

Direct SSH workflow

  1. Require a selected ssh:<alias> context with a recent Probe result. Respect recorded GPU, privilege, interpreter, conda/mamba, module, and scheduler capabilities.
  2. If a scheduler is detected, stop. Do not install or run long work on a shared login node; Wisp needs a scheduler-aware Run backend first.
  3. Use at most a few bounded read-only shell commands to confirm free space, existing environments, and cache paths.
  4. Write an idempotent project script such as runs/setup-<environment>.sh. It must use user-writable paths, fail fast, activate the environment explicitly, run all smoke checks, and write a small JSON manifest only after validation succeeds.
  5. Submit the setup script through one persisted Run:
json
{
  "context_id": "ssh:gpu-box",
  "title": "Set up singlecell environment",
  "command": "bash setup-singlecell.sh /home/me/envs/singlecell /home/me/wisp-env-manifests/singlecell.json",
  "timeout_secs": 14400,
  "input_paths": ["runs/setup-singlecell.sh"],
  "output_specs": [
    {
      "glob": "ssh://gpu-box/home/me/wisp-env-manifests/singlecell.json",
      "kind": "environment-manifest",
      "residency": "remote"
    }
  ]
}
  1. Replace all example paths with probed absolute paths. Call monitor_run when waiting is useful (again after wait_interrupted; do not resubmit). Use one get_run snapshot later or cancel_run when requested.
  2. Record the validated activation command, versions, cache paths, GPU witness, date, and known limitations in a normal project file such as environments/<context>/<name>.md. This file is documentation, not a hidden resolver.
Show full SKILL.md (199 more words)Show less

Setup-script requirements

  • Make repeated execution safe: reuse a matching environment or stop with an actionable version mismatch.
  • Keep pip install phases ordered; a later dependency resolver must not silently replace pinned torch, CUDA, JAX, NumPy, or compiled extensions.
  • Never use sudo unless the Probe explicitly records suitable privilege and the user authorizes it. Prefer conda packages, modules, or user paths.
  • Put multi-gigabyte weights in durable remote storage. Populate them with the model's real loader, verify non-empty content and completion markers, then run a representative inference witness.
  • Write the manifest atomically only after imports, GPU visibility, and the representative workload pass.

Local and WSL boundary

Local and WSL Runs are currently capped at 300 seconds and do not support input_paths. Use local-env-setup for normal interactive setup. Use run_in_context only for a bounded command that finishes within that limit and writes outputs to host-visible project paths.

Unsupported backends

Wisp has no scheduler, Modal, RunPod, cloud Batch, container-service, or managed endpoint execution context today. Do not invent a provider id or hide those lifecycles inside an SSH submission command. Explain the boundary or use a dedicated direct SSH host until a backend implementing submit, poll, cancel, recovery, secrets, and artifact harvest exists.

© xuzhougeng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/compute-env-setup of xuzhougeng/wisp-science.

  • SKILL.md
  • references/envs_reference.md

Open the folder on GitHubat commit b77b170

Compare with similar skills

Compute Env Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Compute Env Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Compute Env Setup this skillxuzhougeng/wisp-science1k—~1.1kAutomated safety check: PassApache-2.0
Fake Model Provider Faultsdifferent-ai/openwork24k—~642Automated safety check: PassCustom licence
Agentacct Workflowmikehasa/agentacct766—~1.6kAutomated safety check: PassMIT
Pipensx Bug Report Triagei3sey/pipensx220—~1.5kAutomated safety check: NotesGPL-3.0
Sage Wiki Integratexoai/sage-wiki620—~861Automated safety check: PassMIT
Antigravity SDK End-to-End Testingomnigent-ai/omnigent11k—~2.7kAutomated safety check: PassApache-2.0

Similar skills

  • Fake Model Provider Faults

    different-ai/openwork

    Makes the desktop app's model provider fail on demand, with refused connections, resets, stalls and HTTP 4xx and 5xx errors, so error and retry states can be reproduced.

    24k GitHub stars~642 tokensUpdated today
    Testing & QAAuto-check passed
  • Agentacct Workflow

    mikehasa/agentacct

    A skill your agent uses when working in a repo with agentacct MCP configured, or when asked to track coding-agent work, smoke-test agentacct integrations, or report objective AI-agent task evidence.

    766 GitHub stars~1.6k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Decodes QR-code bug report photos and screenshots from the pipensx app into a log, then triages crashes and update, download or install failures.

    220 GitHub stars~1.5k tokensUpdated 6 days ago
    Testing & QAAuto-check: notes
  • Sage Wiki Integrate

    xoai/sage-wiki

    Pipeline skill that wires sage-wiki into an existing project — detects language, installs the client, runs a smoke test, and reports.

    620 GitHub stars~861 tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Spins up a local Omnigent server and exercises the Antigravity (Gemini) SDK harness end to end: building agents, running real turns, smoke tests and bug-bashing.

    11k GitHub stars~2.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Diagnose

    ipea/geobr

    Root-cause a failing or wrong geobr call with a disciplined check-the-environment-first loop instead of guessing.

    959 GitHub stars~1.5k tokensUpdated 11 days ago
    Testing & QAAuto-check passed

More from xuzhougeng/wisp-science

All 25 skills in this repo
  • Singlecell Qc

    xuzhougeng/wisp-science

    A skill your agent uses when designing, reviewing, or implementing single-cell RNA-seq QC in Python or R with a human-in-the-loop, data-driven approach.

    1k GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Research Integrity Audit

    xuzhougeng/wisp-science

    学术审查 / research-integrity screening of a manuscript's figures and reported numbers.

    1k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Distill Concept Books

    xuzhougeng/wisp-science

    将概念、理论或分析方法类图书蒸馏为证据可追溯、经人工门禁审核且不暴露书名、作者、出版社等来源身份的任务型 Skill 候选。用于新建或恢复图书蒸馏、以本地 Tesseract 扫描 DOCX 全部内嵌图像或 Poppler 渲染的扫描 PDF 全页、建立 source map 与 evidence/claim/relation/capability…

    1k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Skill Creator

    xuzhougeng/wisp-science

    Create, update, validate, and evaluate Wisp skills. An agent skill from xuzhougeng/wisp-science.

    1k GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Word Zotero Citations

    xuzhougeng/wisp-science

    Build, audit, authorize, recover, or finalize dynamic Zotero citations and bibliographies in Microsoft Word DOCX files with a protected-source, digest-bound workflow.

    1k GitHub stars~3.7k tokensUpdated today
    Auto-check passed
  • Indication Dossier

    xuzhougeng/wisp-science

    Build a sourced research dossier for one therapeutic indication — patient population, epidemiology, disease biology, standard of care, regulatory path, and landmark trials.

    1k GitHub stars~1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Compute Env Setup

What does Compute Env Setup do?

Set up and validate a reproducible Python or R environment on a Wisp execution context. Compute Env Setup is an agent skill from xuzhougeng/wisp-science. Set up and validate a reproducible Python or R environment on a Wisp execution context.

When should I use Compute Env Setup?

Compute Env Setup fits situations like: A selected local; direct SSH context when installing scientific packages; configuring caches; recording interpreter activation.

How do I install Compute Env Setup in Claude Code?

Run `npx skills add xuzhougeng/wisp-science --skill compute-env-setup -a claude-code`. Or copy the skill folder (skills/compute-env-setup in xuzhougeng/wisp-science) into .claude/skills/compute-env-setup in your project. Claude Code loads it when a task matches its description.

How do I install Compute Env Setup in Codex?

Run `npx skills add xuzhougeng/wisp-science --skill compute-env-setup -a codex`. Or copy the skill folder (skills/compute-env-setup in xuzhougeng/wisp-science) into .agents/skills/compute-env-setup in your project. Codex loads it when a task matches its description.

Can I use Compute Env Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add xuzhougeng/wisp-science --skill compute-env-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/compute-env-setup, .gemini/skills/compute-env-setup, .github/skills/compute-env-setup and .opencode/skills/compute-env-setup in your project.

What does Compute Env Setup need to run?

SKILL.md names no scripts, command-line tools or credentials: Compute Env Setup is instructions for the agent only. Our summary lists: Python 3.

Does Compute Env Setup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Compute Env Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Compute Env Setup use?

Compute Env Setup is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Compute Env Setup use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Compute Env Setup?

Skills that share tags, products or a category with Compute Env Setup: Fake Model Provider Faults (different-ai/openwork, 24k stars), Agentacct Workflow (mikehasa/agentacct, 766 stars), Pipensx Bug Report Triage (i3sey/pipensx, 220 stars) and Sage Wiki Integrate (xoai/sage-wiki, 620 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Compute Env Setup?

xuzhougeng (a GitHub user) maintains it in xuzhougeng/wisp-science, which has 1,017 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 8, 2026.

Source: xuzhougeng/wisp-science on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.