Individual skill

compute-env-setup

Prepare reproducible setup instructions and validate a user-managed named software environment on an Open-Science SSH Compute Host, including direct SSH and Slurm hosts. Use when a remote job needs packages, modules, cache variables, or a repeatable activation that the host does not already provide.

resources/skills/compute-env-setup/SKILL.md

Read pinned source

Source commit 357d1a980056e191f380d0e01ec4fbc7cf529d1b

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
5,494
Repository last updated
Nov 8, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Compute environment setup

Prepare one reproducible environment definition and instructions for one small user-managed host
activation file. Open-Science resolves `submitJob(..., { environment: '<name>' })` by sourcing
`~/.open-science/environments/<name>.sh` before the workload. Existing `~/.openscience/environments/<name>.sh` definitions remain readable in place. Before creating an activation, check both names: update the existing definition at its exact location; if both exist, ask the user which to retain. Never create a second activation just to rename the brand. The file contains activation only; it
does not install packages when a job starts.

Software environment setup and Slurm accounting service configuration are separate concerns.
An unavailable `sacct` service is not evidence that Python, Conda, modules, or the named activation
file are missing. Use the Remote Compute Skill's Slurm troubleshooting reference for scheduler
status and cancellation problems; do not make enabling accounting the only recovery path or assume
the user has administrator privileges.

The environment, package caches, images, and activation file are user-managed durable resources,