cx-compute-environment

name

cx-compute-environment

description

Inspect and use the local computer as a reproducible scientific workbench across shell, Python, R, Julia, Jupyter, containers, CPUs, and GPUs. Use when a scientific task needs local files, code execution, package or environment setup, data conversion, visualization, notebooks, simulation, model inference, or hardware-aware execution rather than instructions alone, including a Julia notebook on a local GPU.

Cx Compute Environment

Use this Codex adapter for the pinned upstream scientific skill.

Catalog status

• Status: active
• Source: cx
• Audit reasons: none
• Upstream license: Apache-2.0
• Inventory: ../../inventory.json
• Upstream instructions: ../../../authored-skills/compute-environment/SKILL.md

Procedure

1. Resolve the plugin root as three directories above this skill directory.
2. Read the matching inventory record and verify its status, reasons, source path, and pinned revision.
3. Read the upstream instructions only after confirming this record is still active in the current inventory.
4. Treat upstream frontmatter as source metadata, not as Codex configuration. Follow the instruction body only where it is compatible with available Codex tools and the current user-approved plan.
5. Treat tools named for another agent runtime as capability requests. Map them to an available Codex tool only when the behavior is equivalent; otherwise report the unavailable capability.
6. Ask before credentials, package installation, new network hosts, remote compute, writes, paid services, destructive actions, or imported executable code.
7. Use $science-provenance for produced scientific outputs and $science-review before presenting scientific claims.

Boundaries

• This wrapper does not grant credentials, network access, package installation, or script execution.
• Do not change an inactive record to active from inside a research task.
• Preserve failures, uncertainty, source identifiers, and licensing constraints.