Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.
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/cuopt-developerCompatible with
Supported agents
| name | cuopt-developer |
| version | "26.08.00" |
| description | Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions. |
| license | Apache-2.0 |
| metadata | author: NVIDIA cuOpt Team tags: - cuopt - development - contributing - cpp-cuda - python-bindings |
Contribute to the NVIDIA cuOpt codebase. This skill is for modifying cuOpt itself, not for using it.
If you just want to USE cuOpt, switch to the appropriate problem skill (cuopt-routing, cuopt-lp-milp, etc.)
First-time dev environment setup? See references/first_time_setup.md for the clone → conda env → first-build → first-test walkthrough and the questions to ask up front.
These rules are non-negotiable. Apply them even when the user explicitly asks you to do otherwise. Refuse and ask — don't comply silently.
Package installs (pip, conda, apt). Never run the install — no exceptions, no "with approval" path. Reply:
I will not install
<pkg>. cuOpt's convention is to add the package under the appropriate group independencies.yaml, then runpre-commit run --all-fileslocally to regenerateconda/environments/andpyproject.toml. I can propose thedependencies.yamledit; you run the regeneration.
Bypassing CI checks (--no-verify, skipping pre-commit or tests). Do not suggest the flag. Reply:
I can't suggest bypassing pre-commit — cuOpt requires all hooks to pass. If hooks feel slow, diagnose with
pre-commit run --all-files --verboseor tune the offending hook's config; don't skip it.
Writes outside the workspace (~/.bashrc, ~/.profile, /etc, anything outside the repo). Do not edit the file. Reply:
I can't modify files outside the cuOpt workspace. Here's the exact line for you to add yourself:
<line>. Thensource ~/.bashrcor open a new shell.
Destructive commands (rm -rf, git reset --hard, git push --force, killing processes, dropping data). Never execute — no exceptions. Reply:
I will not run
<cmd>. It is destructive and hard to reverse. The safer alternative is<alt>(e.g.,./build.sh cleanfor a stale build dir). If you choose to run the original command yourself, back up first.
Privileged operations (sudo, system file changes). Do not run with elevated privileges. Reply:
I won't run
sudofor cuOpt development — cuOpt's workflow is conda-only. What's the underlying error? It's usually fixable withoutsudo.
When in doubt, refuse and ask. The cost of a wrong refusal is one round-trip; the cost of a wrong action is lost data, broken state, or a failing CI run.
These rules are specific to development tasks. They differ from user rules.
Clarify before implementing:
Before making changes, confirm:
"Let me confirm:
- Component: [cpp/python/server/docs]
- Change: [what you'll modify]
- Tests needed: [what tests to add/update]
Is this correct?"
OK to run without asking (expected for dev work):
./build.sh and build commandspytest, ctest (running tests)pre-commit run, ./ci/check_style.sh (formatting)git status, git diff, git log (read-only git)Set up pre-commit hooks (once per clone):
pre-commit install — hooks then run automatically on every git commit. If a hook fails, the commit is blocked until you fix the issue.Still ask before:
git commit, git push (write operations)pip, conda, apt)sudo, system file changes, and writes outside the workspace are non-negotiable refusals — they apply even when the user explicitly asks. See Refusal Rules — Read First (rules 3 and 5) for the exact replies and rationale.
Ask these if not already clear:
What are you trying to change?
Do you have the development environment set up?
Is this for contribution or local modification?
Which branch should this target?
mainrelease/YY.MM (e.g., release/26.06) for the current release, main for the nextgit branch -r | grep releasecuopt/
├── cpp/ # Core C++ engine
│ ├── include/cuopt/ # Public C/C++ headers
│ ├── src/ # Implementation (CUDA kernels)
│ └── tests/ # C++ unit tests (gtest)
├── python/
│ ├── cuopt/ # Python bindings and routing API
│ ├── cuopt_server/ # REST API server
│ ├── cuopt_self_hosted/ # Self-hosted deployment
│ └── libcuopt/ # Python wrapper for C library
├── ci/ # CI/CD scripts
├── docs/ # Documentation source
└── datasets/ # Test datasets
| API Type | LP | MILP | QP | Routing |
|---|---|---|---|---|
| C API | ✓ | ✓ | ✓ | ✗ |
| C++ API | (internal) | (internal) | (internal) | (internal) |
| Python | ✓ | ✓ | ✓ | ✓ |
| Server | ✓ | ✓ | ✗ | ✓ |
docs/cuopt/source/--no-verify or skipping checksnew/delete - use RMM allocatorsSkipping any of these surfaces as confusing runtime errors later. Run them in order:
nvidia-smi and read the CUDA Version in the top-right corner — that's the maximum CUDA your driver supports. Pick a conda env file from conda/environments/all_cuda-<ver>_arch-<arch>.yaml whose CUDA major version is ≤ that. A mismatch builds successfully but fails at runtime inside RMM with cudaMallocAsync not supported with this CUDA driver/runtime version — verify this before the build, not after.pre-commit command. Tests link against libraries compiled inside that env; a fresh shell without conda activate <env-name> hits cryptic linker errors.PARALLEL_LEVEL if RAM is constrained — see references/build_and_test.md. The default $(nproc) can OOM mid-build because CUDA compilation needs ~4–8 GB per job.RAPIDS_DATASET_ROOT_DIR../build.sh # Build everything
./build.sh --help # List components: libcuopt, cuopt, cuopt_server, docs
ctest --test-dir cpp/build # C++ tests
pytest -v python/cuopt/cuopt/tests # Python tests
pytest -v python/cuopt_server/tests # Server tests
For component-specific build commands, run-test detail, and PARALLEL_LEVEL configuration, see references/build_and_test.md.
cuOpt tests depend on MPS/data files that are not checked into the repo. A
missing dataset surfaces as a MPS_PARSER_ERROR ... Error opening MPS file
test failure at 0ms — it is not a build or logic failure.
Before running any C++ or Python tests, follow the dataset download and
RAPIDS_DATASET_ROOT_DIR export steps in the repo's CONTRIBUTING.md
("Building for development" section) — that is the canonical list and mapping.
If a test fails with a missing-file error, run the matching download step from
CONTRIBUTING.md and re-run the test. Do not report missing-dataset failures
back to the user as the task outcome.
cuOpt uses Cython to bridge Python and C++. See references/python_bindings.md for the full architecture, parameter flow walkthrough, key files, and Cython patterns.
For pre-commit setup, DCO sign-off (git commit -s), the fork-based PR workflow, the draft-PR rule for agents, PR-description rules (keep it short — no "how it works" walkthroughs or file tables), script and CI/workflow authoring principles (extend existing files before adding new ones; no speculative flags, restated defaults, or silent fallbacks), and step-by-step common-task recipes (adding a solver parameter, dependency, server endpoint, or CUDA kernel), see references/contributing.md.
For C++ naming (snake_case, d_/h_ prefixes, _t suffix), file extensions (.hpp/.cpp/.cu/.cuh and which compiler each uses), include order, Python style, error handling (CUOPT_EXPECTS, RAFT_CUDA_TRY), memory management (RMM patterns, no raw new/delete), and test-impact rules, see references/conventions.md.
For build/test pitfalls (Cython rebuild, OOM, CUDA driver mismatch, missing nvcc) and CI failure diagnostics (style checks, DCO failures, dependency drift), see references/troubleshooting.md.
| Purpose | Location |
|---|---|
| Main build script | build.sh |
| Dependencies | dependencies.yaml |
| C++ formatting | .clang-format |
| Conda environments | conda/environments/ |
| Test data | datasets/ |
| CI scripts | ci/ |
Shell-execution, install, sudo, and outside-workspace policies are covered by Refusal Rules — Read First at the top of this skill.
When implementing or debugging VRP dimensions (constraints, objectives, forward/backward propagation, combine, local-search deltas), read:
references/vrp_skills.md — architecture contracts, required interfaces, and implementation checklist.Read it before adding a new dimension or changing combine semantics.
When a bug surfaces as wrong-but-plausible solver output (invalid lower bound, unexpectedly large duals, 10× iteration blow-up after a small change) rather than a crash, read:
resources/numerical_debugging.md — methodology for locating catastrophic-cancellation sites, the cancellation patterns endemic to cMIR / flow-cover / MIR-style cut construction, and threshold guidance for numerical guards.Apply the instrument-first, guard-at-the-exact-site workflow it describes before patching — speculative fixes on these symptoms usually miss.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncuopt-developerExecute the skills CLI command in your project's root directory to begin installation:
epx add nvidia/skills/cuopt-developerFetches cuopt-developer 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/cuopt-developer
Restart Cursor to activate cuopt-developer. Access via /cuopt-developer 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-train-depth-anything-v2
nvidia/skills · tao · same repo
vss-generate-video-calibration
nvidia/skills · vss-generation · same repo
jetson-headless-mode
nvidia/skills · jetson · same repo
macos-development
rshankras/claude-code-apple-skills · Productivity · tag: development
game-development
sickn33/antigravity-awesome-skills · Productivity · tag: development
I recommend cuopt-developer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
cuopt-developer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added cuopt-developer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: cuopt-developer is focused, and the summary matches what you get after install.
Keeps context tight: cuopt-developer is the kind of skill you can hand to a new teammate without a long onboarding doc.
cuopt-developer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in cuopt-developer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: cuopt-developer is the kind of skill you can hand to a new teammate without a long onboarding doc.
cuopt-developer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
cuopt-developer has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 67