skills/cuopt-routing-api-python: update with benchmark details

[ramakrishnap-nv]

update with benchmark details

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[ramakrishnap-nv]

/nvskills-ci

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates the cuopt-routing-api-python skill: reformats skill-card metadata, adds a BENCHMARK.md evaluation report (VERDICT: FAIL), inserts a blank line in SKILL.md frontmatter, and regenerates the Sigstore DSSE signature bundle reflecting new digests.

Changes

cuopt-routing-api-python documentation & attestation

Layer / File(s)	Summary
Skill card metadata and references skills/cuopt-routing-api-python/skill-card.md	Updated Owner/License/Use Case frontmatter, expanded/reordered References, and normalized Skill Output and evaluation-result formatting.
SKILL frontmatter spacing skills/cuopt-routing-api-python/SKILL.md	Inserted a blank line between YAML frontmatter and the "cuOpt Routing — Python API" section header.
NVSkills-Eval benchmark report skills/cuopt-routing-api-python/BENCHMARK.md	Added a 3-tier evaluation report (VERDICT: FAIL) with agents, dimensions, dataset composition, per-dimension scores, Tier1 static findings, Tier2 deduplication findings, and a publication recommendation.
Sigstore DSSE bundle skills/cuopt-routing-api-python/skill.oms.sig	Replaced the DSSE bundle line with updated payload/resource digests and a new signatures[0].sig value reflecting the documentation changes.

---

🎯 3 (Moderate) | ⏱️ ~20 minutes

• NVIDIA/cuopt#1287: Overlaps on skills/cuopt-routing-api-python metadata and signature handling; related to validation/signature compliance work.
• NVIDIA/cuopt#1308: Related changes to the skill attestation bundle and evaluations for the routing skill.
• NVIDIA/cuopt#1301: Touches the same routing skill documentation artifacts (skill-card.md, SKILL.md) and references reorganization.

Suggested reviewers:

• Iroy30
• tmckayus

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is extremely vague and generic, using only 'update with benchmark details' without meaningful context about what was added or changed.	Expand the description to explain the benchmark evaluation results, the changes made to documentation, and the reasoning behind the updates.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change—updating the cuopt-routing-api-python skill with benchmark details, which is reflected in the BENCHMARK.md addition and related updates.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch skills-cuopt-routing-api-python

---

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

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@skills/cuopt-routing-api-python/BENCHMARK.md`:
- Line 72: Update the truncated security finding text in BENCHMARK.md by
replacing the truncated word "reac" with the full word "reach" in the MEDIUM
SECURITY/Unknown (SQP-2) entry so the sentence reads "...making it accessible to
any host that can reach (references/server_examples.md:7)". Ensure no other
words were accidentally altered and run a quick spellcheck on that line.
In `@skills/cuopt-routing-api-python/skill-card.md`:
- Around line 63-70: Add a single blank line after the evaluation results
Markdown table (the table starting with "| Dimension | Num | `claude-code` |
`codex` |") so there is an empty line separating the table from the following
section heading; update the skill-card.md content immediately after that table
to insert one newline before the next heading or paragraph.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 358fec5a-5730-495f-a4fc-cc410a6e4c7d

📥 Commits

Reviewing files that changed from the base of the PR and between 2c0c193 and cc31038.

📒 Files selected for processing (3)

• skills/cuopt-routing-api-python/BENCHMARK.md
• skills/cuopt-routing-api-python/skill-card.md
• skills/cuopt-routing-api-python/skill.oms.sig

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix truncated text.

The finding description is cut off mid-word. "reac" should be "reach".

✏️ Proposed fix

-- MEDIUM SECURITY/Unknown (SQP-2): Binding the cuOpt server to 0.0.0.0 exposes it on all network interfaces, making it accessible to any host that can reac (`references/server_examples.md:7`)+- MEDIUM SECURITY/Unknown (SQP-2): Binding the cuOpt server to 0.0.0.0 exposes it on all network interfaces, making it accessible to any host that can reach (`references/server_examples.md:7`)

📝 Committable suggestion

‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- MEDIUM SECURITY/Unknown (SQP-2): Binding the cuOpt server to 0.0.0.0 exposes it on all network interfaces, making it accessible to any host that can reac (`references/server_examples.md:7`)
	- MEDIUM SECURITY/Unknown (SQP-2): Binding the cuOpt server to 0.0.0.0 exposes it on all network interfaces, making it accessible to any host that can reach (`references/server_examples.md:7`)

🧰 Tools

🪛 LanguageTool

[grammar] ~72-~72: Ensure spelling is correct
Context: ...king it accessible to any host that can reac (references/server_examples.md:7) - L...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/cuopt-routing-api-python/BENCHMARK.md` at line 72, Update the
truncated security finding text in BENCHMARK.md by replacing the truncated word
"reac" with the full word "reach" in the MEDIUM SECURITY/Unknown (SQP-2) entry
so the sentence reads "...making it accessible to any host that can reach
(references/server_examples.md:7)". Ensure no other words were accidentally
altered and run a quick spellcheck on that line.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Add blank line after the table.

The evaluation results table should be followed by a blank line before the next section heading to comply with Markdown formatting standards.

📝 Proposed fix

 | Effectiveness | 2 | 83% (+14%) | 83% (+12%) |
| Efficiency | 2 | 93% (-0%) | 56% (-5%) |
+
## Skill Version(s): <br>

📝 Committable suggestion

‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	| Dimension | Num |`claude-code`|`codex`|
	|---|---:|---:|---:|
	| Security | 2 | 100% (+0%) | 100% (+0%) |
	| Correctness | 2 | 100% (+0%) | 95% (+3%) |
	| Discoverability | 2 | 100% (+0%) | 70% (-5%) |
	| Effectiveness | 2 | 83% (+14%) | 83% (+12%) |
	| Efficiency | 2 | 93% (-0%) | 56% (-5%) |
	| Dimension | Num |`claude-code`|`codex`|
	|---|---:|---:|---:|
	| Security | 2 | 100% (+0%) | 100% (+0%) |
	| Correctness | 2 | 100% (+0%) | 95% (+3%) |
	| Discoverability | 2 | 100% (+0%) | 70% (-5%) |
	| Effectiveness | 2 | 83% (+14%) | 83% (+12%) |
	| Efficiency | 2 | 93% (-0%) | 56% (-5%) |

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 63-63: Tables should be surrounded by blank lines

(MD058, blanks-around-tables)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/cuopt-routing-api-python/skill-card.md` around lines 63 - 70, Add a
single blank line after the evaluation results Markdown table (the table
starting with "| Dimension | Num | `claude-code` | `codex` |") so there is an
empty line separating the table from the following section heading; update the
skill-card.md content immediately after that table to insert one newline before
the next heading or paragraph.