GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Inspect a registered execution server before compute planning and interpret its persisted capability profile.
Install Probe Compute Environment
$ npx skills add xuzhougeng/wisp-science --skill probe-compute-environment -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install xuzhougeng/wisp-science probe-compute-environment --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/xuzhougeng/wisp-science.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/probe-compute-environment .claude/skills/probe-compute-environment && rm -rf skills-srcUse ~/.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/
Install the "probe-compute-environment" agent skill from https://github.com/xuzhougeng/wisp-science/tree/main/skills/probe-compute-environment into .claude/skills/probe-compute-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "probe-compute-environment", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/xuzhougeng/wisp-science/tree/main/skills/probe-compute-environmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add xuzhougeng/wisp-science --skill probe-compute-environment -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install xuzhougeng/wisp-science probe-compute-environment --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xuzhougeng/wisp-science.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/probe-compute-environment .agents/skills/probe-compute-environment && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "probe-compute-environment" agent skill from https://github.com/xuzhougeng/wisp-science/tree/main/skills/probe-compute-environment into .agents/skills/probe-compute-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "probe-compute-environment", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add xuzhougeng/wisp-science --skill probe-compute-environment -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install xuzhougeng/wisp-science probe-compute-environment --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xuzhougeng/wisp-science.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/probe-compute-environment .cursor/skills/probe-compute-environment && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "probe-compute-environment" agent skill from https://github.com/xuzhougeng/wisp-science/tree/main/skills/probe-compute-environment into .cursor/skills/probe-compute-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "probe-compute-environment", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/xuzhougeng/wisp-science.git --path skills/probe-compute-environment--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add xuzhougeng/wisp-science --skill probe-compute-environment -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install xuzhougeng/wisp-science probe-compute-environment --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xuzhougeng/wisp-science.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/probe-compute-environment .gemini/skills/probe-compute-environment && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "probe-compute-environment" agent skill from https://github.com/xuzhougeng/wisp-science/tree/main/skills/probe-compute-environment into .gemini/skills/probe-compute-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "probe-compute-environment", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install xuzhougeng/wisp-science probe-compute-environmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add xuzhougeng/wisp-science --skill probe-compute-environment -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/xuzhougeng/wisp-science.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/probe-compute-environment .github/skills/probe-compute-environment && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "probe-compute-environment" agent skill from https://github.com/xuzhougeng/wisp-science/tree/main/skills/probe-compute-environment into .github/skills/probe-compute-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "probe-compute-environment", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add xuzhougeng/wisp-science --skill probe-compute-environment -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install xuzhougeng/wisp-science probe-compute-environment --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xuzhougeng/wisp-science.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/probe-compute-environment .opencode/skills/probe-compute-environment && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "probe-compute-environment" agent skill from https://github.com/xuzhougeng/wisp-science/tree/main/skills/probe-compute-environment into .opencode/skills/probe-compute-environment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "probe-compute-environment", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
probe-compute-environment- GitHub stars
- 1k
- Token cost
- ~447 tokens
- SKILL.md length
- 209 words
- Files
- 2
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Inspect a registered execution server before compute planning and interpret its persisted capability profile.
- Works in 6 steps: Treat persisted capabilities as the… → Treat gpu_summary: null as no usable… → Treat privilege: unprivileged as no root… → …
- A server is added
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The user clicks Probe
What it does
Probe Compute Environment is an agent skill from xuzhougeng/wisp-science. 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.
Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Research & Science. 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 AGPL-3.0.
When your agent uses it
- A server is added
- The user clicks Probe
- Before enabling an unfamiliar SSH/WSL resource
- Deciding whether GPU
Example prompts
- “/probe-compute-environment”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- 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
- Treat privilege: unprivileged as no root or passwordless sudo. Do not
- Use a detected scheduler rather than running long work on a login node.
- Use the recorded interpreter paths and environment managers. Do not assume
- If the probe failed, inspect the saved error and ask the user to check the
What it can do on your machine
Read from SKILL.md and the folder at commit 2ba143b. 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.
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
Probe Compute Environment loads about 447 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 209 words of instructions outside code blocks.
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 2ba143b, republished under its AGPL-3.0 licence (© xuzhougeng). 209 words, ~447 tokens.
Download SKILL.mdSave it as
.claude/skills/probe-compute-environment/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- probe-compute-environment
- description
- 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.
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: nullas no usable GPU. Plan CPU work and never add CUDA/GPU flags speculatively. - Treat
privilege: unprivilegedas no root or passwordless sudo. Do not usesudo, 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.
© xuzhougeng, AGPL-3.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 in skills/probe-compute-environment of xuzhougeng/wisp-science.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 2ba143b
Compare with similar skills
Probe Compute Environment 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Probe Compute Environment this skillxuzhougeng/wisp-science | 1k | — | ~447 | Automated safety check: Pass | AGPL-3.0 | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT | |
| NetworkxzLanqing/codex-claude-academic-skills | 4.7k | 15 repos | ~3.2k | Automated safety check: Pass | BSD-3-Clause | |
| Nature-Style Scientific FiguresYuan1z0825/nature-skills | 47k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Citation ManagementK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.9k | Automated safety check: Notes | MIT |
Similar skills
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Networkx
zLanqing/codex-claude-academic-skills
Comprehensive toolkit for creating, analyzing, and visualizing complex networks and graphs in Python.
Nature-Style Scientific Figures
Yuan1z0825/nature-skills
Creates, revises, audits and exports manuscript-ready scientific figures in Python or R, and routes AI-generated graphical abstracts to a separate workflow.
Citation Management
K-Dense-AI/claude-scientific-writer
Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
More from xuzhougeng/wisp-science
All 25 skills in this repoSinglecell 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.
Research Integrity Audit
xuzhougeng/wisp-science
学术审查 / research-integrity screening of a manuscript's figures and reported numbers.
Distill Concept Books
xuzhougeng/wisp-science
将概念、理论或分析方法类图书蒸馏为证据可追溯、经人工门禁审核且不暴露书名、作者、出版社等来源身份的任务型 Skill 候选。用于新建或恢复图书蒸馏、以本地 Tesseract 扫描 DOCX 全部内嵌图像或 Poppler 渲染的扫描 PDF 全页、建立 source map 与 evidence/claim/relation/capability…
Skill Creator
xuzhougeng/wisp-science
Create, update, validate, and evaluate Wisp skills. An agent skill from xuzhougeng/wisp-science.
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.
Compute Env Setup
xuzhougeng/wisp-science
Set up and validate a reproducible Python or R environment on a Wisp execution context.
Related
Works with
Categories
Questions about Probe Compute Environment
What does Probe Compute Environment do?
Inspect a registered execution server before compute planning and interpret its persisted capability profile. Probe Compute Environment is an agent skill from xuzhougeng/wisp-science. Inspect a registered execution server before compute planning and interpret its persisted capability profile.
When should I use Probe Compute Environment?
Probe Compute Environment fits situations like: A server is added; the user clicks Probe; before enabling an unfamiliar SSH/WSL resource; deciding whether GPU.
How do I install Probe Compute Environment in Claude Code?
Run `npx skills add xuzhougeng/wisp-science --skill probe-compute-environment -a claude-code`. Or copy the skill folder (skills/probe-compute-environment in xuzhougeng/wisp-science) into .claude/skills/probe-compute-environment in your project. Claude Code loads it when a task matches its description.
How do I install Probe Compute Environment in Codex?
Run `npx skills add xuzhougeng/wisp-science --skill probe-compute-environment -a codex`. Or copy the skill folder (skills/probe-compute-environment in xuzhougeng/wisp-science) into .agents/skills/probe-compute-environment in your project. Codex loads it when a task matches its description.
Can I use Probe Compute Environment 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 probe-compute-environment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/probe-compute-environment, .gemini/skills/probe-compute-environment, .github/skills/probe-compute-environment and .opencode/skills/probe-compute-environment in your project.
What does Probe Compute Environment need to run?
SKILL.md names no scripts, command-line tools or credentials: Probe Compute Environment is instructions for the agent only.
Does Probe Compute Environment 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 Probe Compute Environment 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 Probe Compute Environment use?
Probe Compute Environment is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Probe Compute Environment use?
About 447 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Probe Compute Environment?
Skills that share tags, products or a category with Probe Compute Environment: GitHub Deep Research (bytedance/deer-flow, 84k stars), Last30days (mvanhorn/last30days-skill, 64k stars), Networkx (zLanqing/codex-claude-academic-skills, 4.7k stars) and Nature-Style Scientific Figures (Yuan1z0825/nature-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Probe Compute Environment?
xuzhougeng (a GitHub user) maintains it in xuzhougeng/wisp-science, which has 1,026 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 10, 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.