CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cuopt-routing-api-python

Vehicle routing (VRP, TSP, PDP) with cuOpt — Python API only. Use when the user is building or solving routing in Python.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cuopt-routing-api-python/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient reference for the cuOpt Python routing API with concrete API examples, a status-check feedback loop, and clean one-level-deep progressive disclosure into real bundle files. The main gaps are placeholder values in the flagship example that prevent copy-paste execution, and slight redundancy between the Debugging section and the Common Issues/Solution Checking material.

Suggestions

Make the Minimal VRP Example fully runnable by replacing '[...]' with a real 4x4 cost matrix and constructed cudf.Series values, mirroring assets/vrp_basic/model.py.

Fold the Debugging section into the Common Issues table (or Solution Checking) to remove the duplicated error-message guidance.

Add a brief numbered workflow line (gather answers → build DataModel → add constraints → solve → check status → apply fix table) to make the sequence and validation checkpoint explicit.

DimensionReasoningScore

Conciseness

The body is lean reference material with no explanations of concepts Claude already knows; every section adds API-specific knowledge (dtypes, status codes, gotchas like 'compute_waypoint_sequence alters route_df'). It falls short of a 5 due to minor redundancy: the Debugging section repeats status/error guidance already shown in Solution Checking and the Common Issues table.

4 / 5

Actionability

Mostly executable guidance with real API calls (add_cost_matrix, set_order_time_windows, add_capacity_dimension), explicit dtypes, and concrete status-code handling with a fix table. It is not a 5 because the primary example is not copy-paste ready — 'cudf.DataFrame([...])' and undefined variables like 'earliest_series'/'transit_time_matrix' are placeholders; it is above a 3 because the API usage shown is concrete and specific rather than pseudocode.

4 / 5

Workflow Clarity

A coherent implied sequence (required questions → DataModel → constraints → solve → check status) with a genuine feedback loop: status != 0 leads to get_error_message(), get_infeasible_orders(), and the Common Issues fix table. It is not a 5 because the sequence is implicit in section order rather than explicitly numbered, and there is no stated validation checkpoint before reporting results.

4 / 5

Progressive Disclosure

The SKILL.md is a lean overview that clearly signals one-level-deep references, all of which exist: [examples.md](references/examples.md), [server_examples.md](references/server_examples.md), assets/vrp_basic/, assets/pdp_basic/, and assets/README.md, each labeled with its content. The bundle structure matches what the body claims and nothing nests deeper than one level, matching the clear-overview anchor.

5 / 5

Total

17

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, niche-scoped description with good domain keyword coverage and an explicit 'Use when' trigger. Its main weakness is that the 'what' names the domain and problem types but few concrete capabilities, and 'routing' alone carries some overlap risk with non-vehicle routing requests.

Suggestions

Add 2-3 concrete capability phrases to the 'what' clause, e.g., 'solve VRP/TSP/pickup-delivery instances, model time windows, capacities and precedence, retrieve routes and total cost'.

Include more natural trigger synonyms such as 'route optimization', 'traveling salesman', or 'pickup and delivery' to broaden natural-term coverage.

Qualify 'routing' with 'vehicle routing / fleet' in the trigger clause to reduce overlap with network-routing or pathfinding requests.

DimensionReasoningScore

Specificity

The description names the domain and problem types concretely ('Vehicle routing (VRP, TSP, PDP) with cuOpt — Python API only') with only two generic actions ('building or solving routing'), matching the anchor for a named domain with 1-2 concrete actions but not comprehensive. It is not a 4 because it does not list several specific actions (e.g., setting time windows, capacities, or retrieving routes), and not a 2 because the domain and problem variants are explicitly named.

3 / 5

Completeness

Both parts are present: the 'what' ('Vehicle routing (VRP, TSP, PDP) with cuOpt — Python API only') and an explicit 'when' ('Use when the user is building or solving routing in Python'), matching the anchor where both exist but the when/what could be more specific. It is not a 5 because the 'what' is a topic statement rather than concrete capability phrases, and the trigger clause is narrower than concrete trigger-phrase coverage.

4 / 5

Trigger Term Quality

Good keyword coverage with natural domain synonyms users would say: 'vehicle routing', 'VRP', 'TSP', 'PDP', 'routing', 'Python', 'cuOpt'. It falls short of the 5 anchor because common natural variations like 'route optimization', 'traveling salesman problem', 'pickup and delivery', or file extensions are missing; it is above a 3 because multiple distinct natural terms and synonyms are present.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (cuOpt, Python-only) with mostly distinct triggers, fitting 'mostly distinct; minor overlap risk'. It is not a 5 because the word 'routing' alone is ambiguous (network routing, pathfinding, generic route planning), so a user's generic 'routing in Python' request could pull this skill when a different tool was intended.

4 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NVIDIA/skills

Path

skills/cuopt-routing-api-python/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.