cuopt-installation-common

$npx mdskill add NVIDIA/skills/cuopt-installation-common

Verify GPU and CUDA prerequisites before cuOpt deployment.

  • Confirms hardware compatibility and software versions for installation.
  • Checks NVIDIA driver, CUDA runtime, and compute capability.
  • Asks about environment type, usage mode, and package manager.
  • Delivers a checklist of required system and environment details.

SKILL.md

.github/skills/cuopt-installation-commonView on GitHub ↗
---
name: cuopt-installation-common
version: "26.06.00"
description: Install cuOpt — system and environment requirements only. Domain concepts; no install commands or interface guidance.
---

# cuOpt Installation (common)

Domain concepts for installing and running cuOpt. No install commands or interface details here.

## System requirements

- **GPU**: NVIDIA with Compute Capability ≥ 7.0 (Volta or newer). Examples: V100, A100, H100, RTX 20xx/30xx/40xx. Not supported: GTX 10xx (Pascal).
- **CUDA**: 12.x or 13.x. Package and runtime must match (e.g. cuopt built for CUDA 12 with a CUDA 12 driver).
- **Driver**: Compatible NVIDIA driver for the CUDA version in use.

## Required questions (environment)

Ask these if not already clear:

1. **Environment** — Local machine with GPU, cloud instance, Docker/Kubernetes, or no GPU (need remote/server)?
2. **CUDA version** — What is installed or planned? (e.g. `nvcc --version`, `nvidia-smi`.)
3. **Usage** — In-process (library/API) vs server (REST)? Which language or runtime (Python, C, server)?
4. **Package manager** — pip, conda, or Docker preferred?

## Notes

- Python API and C API are separate installables; having one does not provide the other.
- Server deployment typically uses Docker or a dedicated server package; client can be any language.

More from NVIDIA/skills

SkillDescription
accessing-mlflowQuery and browse evaluation results stored in MLflow. Use when the user wants to look up runs by invocation ID, compare metrics across models, fetch artifacts (configs, logs, results), or set up the MLflow MCP server. ALWAYS triggers on mentions of MLflow, experiment results, run comparison, invocation IDs in the context of results, or MLflow MCP setup.
ad-add-fusion-transformation>
ad-conf-check>
ad-graph-dump>
ad-model-onboard>
ad-pipeline-failure-pr>
add-benchmark>
aiq-deploy|
aiq-research|
byobCreate custom LLM evaluation benchmarks using the BYOB decorator framework. Use when the user wants to (1) create a new benchmark from a dataset, (2) pick or write a scorer, (3) compile and run a BYOB benchmark, (4) containerize a benchmark, or (5) use LLM-as-Judge evaluation. Triggers on mentions of BYOB, custom benchmark, bring your own benchmark, scorer, or benchmark compilation.