evals: add benchmark evals for cuopt-developer skill

[rgsl888prabhu]

Adds skills/cuopt-developer/evals/evals.json with 3 eval cases covering the benchmarks/ folder.

[coderabbitai]

Linter diff in the way? Review this PR in Change Stack to focus on meaningful changes and expand context only when needed.

📝 Walkthrough

Walkthrough

A new evaluation registry file is added containing three benchmark evaluation entries for cuOpt developer skill assessment: Mittelmann LP benchmark with LP-specific build configuration, MIPLIB benchmark with per-instance logging and time limits, and multi-GPU MIPLIB batching scenario with machine-level instance distribution.

Changes

Benchmark Evaluation Configurations

Layer / File(s)	Summary
New benchmark evaluation entries skills/cuopt-developer/evals/evals.json	Three structured evaluation items define benchmark questions, required build flags and environment setup in ground_truth, and expected response checklist items in expected_behavior for Mittelmann LP, MIPLIB, and multi-GPU MIPLIB batching scenarios.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested labels

non-breaking, improvement

Suggested reviewers

• Iroy30

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title 'evals: add benchmark evals for cuopt-developer skill' clearly and concisely summarizes the main change—adding evaluation cases for the cuopt-developer skill focused on benchmarks.
Description check	✅ Passed	The description 'Adds skills/cuopt-developer/evals/evals.json with 3 eval cases covering the benchmarks/ folder' directly relates to the changeset by specifying the file added and its purpose.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch add-benchmark-evals-cuopt-developer

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[rgsl888prabhu]

/nvskills-ci