Install and verify cuPyNumeric for Python — requirements, commands, verification. Source builds are out of scope.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add nvidia/skills/cupynumeric-installCompatible with
Supported agents
| name | cupynumeric-install |
| description | Install and verify cuPyNumeric for Python — requirements, commands, verification. Source builds are out of scope. |
| license | CC-BY-4.0 OR Apache-2.0 |
| compatibility | linux-x86_64, linux-aarch64, darwin-aarch64, wsl-x86_64 |
| metadata | author: "NVIDIA Corporation <legate@nvidia.com>" version: "2.0.0" tags: - cupynumeric - legate - numpy - installation - conda - gpu - distributed-computing upstream: https://github.com/nv-legate/cupynumeric docs: https://docs.nvidia.com/cupynumeric/latest/installation.html |
Use this skill to install cuPyNumeric for use from Python and to verify the install actually works (including GPU usage). Apply it whenever a user wants cuPyNumeric running via conda or pip. Do not use it to build from source (to modify or contribute) — that is out of scope.
pip install, conda install, or any installer. Print the command; let the user run it.--version checks are fine.Confirm these system requirements before recommending any install:
Follow these steps in order: confirm the prerequisites, ask the scoping questions, install via the chosen path, then verify.
conda --version and pip --version. Prefer conda (upstream-recommended); fall back to pip.nvidia-smi / nvcc --version.If neither conda nor pip is available, install one. Provide the command and the docs link; do not run it — curl | bash requires user trust.
curl -L -O "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-$(uname)-$(uname -m).sh"
bash "Miniforge3-$(uname)-$(uname -m).sh"
Docs: https://github.com/conda-forge/miniforge
Install Python from your OS package manager (apt/dnf/brew) or https://www.python.org/downloads/. If pip is missing on an existing Python: python -m ensurepip --upgrade.
After installing, open a new shell so the binary is on PATH.
conda create -n cupynumeric -c conda-forge -c legate cupynumeric
conda activate cupynumeric
Into an existing env: conda install -c conda-forge -c legate cupynumeric.
conda auto-selects the GPU vs CPU variant from whether nvidia-smi works at install time. To override that, see below.
Set CONDA_OVERRIDE_CUDA only when no GPU is visible at install time (e.g. building a container for a GPU host). Use the runtime host's CUDA version:
CONDA_OVERRIDE_CUDA="12.2" conda install -c conda-forge -c legate cupynumeric
conda install -c conda-forge -c legate-nightly cupynumeric
python -m venv .venv
source .venv/bin/activate
pip install nvidia-cupynumeric
Run a self-contained script through the legate launcher — no repo checkout needed.
TMP=$(mktemp -d)
cat > "$TMP/smoke.py" <<'EOF'
import cupynumeric as np
a = np.arange(10)
b = np.ones((4, 4))
print("sum:", a.sum()) # expect 45
print("matmul:", (b @ b).sum()) # expect 64.0
EOF
legate "$TMP/smoke.py"
rm -rf "$TMP"
Expect sum: 45 and matmul: 64.0. If legate is missing, the env is not activated — see Troubleshooting.
A passing smoke test does not prove GPU usage — a CPU-variant install on a GPU box produces correct results too. Run both steps.
1. Force a GPU launch. legate --gpus N requests N GPUs; fails fast if no GPU is visible or the CPU variant is installed.
TMP=$(mktemp -d)
cat > "$TMP/check.py" <<'EOF'
import cupynumeric as np
print(np.ones((4096, 4096)).sum())
EOF
legate --gpus 1 "$TMP/check.py"
rm -rf "$TMP"
Expect 16777216.0. If you see CUDA driver, libcudart, or no GPUs available, the CPU variant is installed; reinstall with CONDA_OVERRIDE_CUDA.
2. Confirm the GPU was touched. Run a deadline-bounded matmul loop alongside nvidia-smi, all from one shell — no second-terminal race:
TMPDIR_GPU=$(mktemp -d)
SCRIPT="$TMPDIR_GPU/cupynumeric_gpu_check.py"
cat > "$SCRIPT" <<'EOF'
import cupynumeric as np, time
a = np.ones((10000, 10000))
deadline = time.time() + 20
iters = 0
while time.time() < deadline:
b = a @ a
_ = float(b.sum()) # force sync so the matmul actually runs
iters += 1
print("iters:", iters)
EOF
legate --gpus 1 "$SCRIPT" &
WORKLOAD=$!
sleep 5 # buffer for Legate startup
for _ in $(seq 10); do # 10 samples at 1s — covers slow startup
nvidia-smi --query-gpu=utilization.gpu,memory.used --format=csv,noheader
sleep 1
done
wait "$WORKLOAD"
rm -rf "$TMPDIR_GPU"
Expect memory.used in the GiB range across most samples and non-trivial utilization.gpu in several. If both stay at baseline across every sample, the GPU variant is not installed — check conda list cupynumeric for *_gpu (not *_cpu).
See verification_examples.md for multi-GPU checks, CPU fallback, container, and troubleshooting.
pip uninstall nvidia-cupynumeric or conda remove cupynumeric first.legate launcher for multi-GPU / multi-rank runs. Plain python runs single-process: legate --gpus 2 script.py.CONDA_OVERRIDE_CUDA. conda otherwise auto-selects the CPU or GPU variant from nvidia-smi at install time.conda --version ≥ 24.1. Older releases silently break variant selection.ModuleNotFoundError: No module named 'cupynumeric' → Run which python and pip list | grep cupynumeric (or conda list | grep cupynumeric) from the same shell to find the env mismatch.ImportError mentioning CUDA / libcudart → Reinstall with CONDA_OVERRIDE_CUDA="<your-cuda-version>"; the CPU variant is on a GPU box, or CUDA versions are mismatched.legate: command not found → Activate the env, then run which legate to confirm.AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncupynumeric-installExecute the skills CLI command in your project's root directory to begin installation:
epx add nvidia/skills/cupynumeric-installFetches cupynumeric-install from nvidia/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/cupynumeric-install
Restart Cursor to activate cupynumeric-install. Access via /cupynumeric-install in your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
nemo-rl-auto-research
nvidia/skills · nemo · same repo
tao-finetune-cosmos-reason
nvidia/skills · tao · same repo
aiq-deploy
nvidia/skills · aiq · same repo
jetson-flash-image
nvidia/skills · jetson · same repo
dynamo-router-starter
nvidia/skills · dynamo · same repo
nemoclaw-user-deploy-remote
nvidia/skills · nemoclaw · same repo
We added cupynumeric-install from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in cupynumeric-install — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
cupynumeric-install reduced setup friction for our internal harness; good balance of opinion and flexibility.
cupynumeric-install has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend cupynumeric-install for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for cupynumeric-install matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: cupynumeric-install is focused, and the summary matches what you get after install.
cupynumeric-install has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: cupynumeric-install is the kind of skill you can hand to a new teammate without a long onboarding doc.
cupynumeric-install has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 66