BF cuopt-developer
Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.
Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI).
As a process F 62/100 · Will not run — References files that are not bundled: references/first_time_setup.md, ../../CONTRIBUTING.md, references/build_and_test.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/first_time_setup.md - warning
missing-refreference to a missing file: ../../CONTRIBUTING.md - warning
missing-refreference to a missing file: references/build_and_test.md - warning
missing-refreference to a missing file: references/python_bindings.md - warning
missing-refreference to a missing file: references/contributing.md - warning
missing-refreference to a missing file: references/conventions.md - warning
missing-refreference to a missing file: references/troubleshooting.md - warning
missing-refreference to a missing file: ../../ci/README.md - warning
missing-refreference to a missing file: ../../ci/release/README.md - warning
missing-refreference to a missing file: ../../docs/cuopt/README.md - warning
missing-refreference to a missing file: references/vrp_skills.md
Process rating: all ten parameters 62/100
- 0Tools and files. 11 referenced file(s) missing: references/first_time_setup.md, ../../CONTRIBUTING.md, references/build_and_test.md
- 0Result and completion. Does not say what the result is
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 56 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3119 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 148: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.