CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cuopt-user-rules

Base rules for end users calling NVIDIA cuOpt (routing/LP/MILP/QP/install/server). Not for cuOpt internals — use cuopt-developer for those.

56

Quality

71%

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 ./plugins/nvidia/skills/cuopt-user-rules/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is a well-organized, highly actionable rule set with explicit verification checkpoints and concrete commands and templates. Its weaknesses are redundancy across the three overlapping 'ask first' sections and the absence of a single unified ordered workflow or an end-to-end solver example.

Suggestions

Merge 'Ask Before Assuming', 'Handle Incomplete Questions', and 'Clarify Data Requirements' into one consolidated section to remove repetition and save tokens.

Consolidate 'Never Install Packages Automatically' with the package-install row in the 'Ask Before Running' table so the rule is stated once.

Add a brief numbered end-to-end workflow (clarify -> verify understanding -> check environment -> solve -> report status/objective -> post-correction check) so the thematic sections hang on one explicit sequence.

DimensionReasoningScore

Conciseness

The sections 'Ask Before Assuming', 'Handle Incomplete Questions', and 'Clarify Data Requirements' overlap heavily, and 'Never Install Packages Automatically' repeats the install rule already in the 'Ask Before Running' table. Mostly dense rule-oriented content, but the repetition and restated emphasis (MUST/MANDATORY) could be consolidated — more than minor trimming, less than pervasive padding.

3 / 5

Actionability

Provides verbatim question templates, a copy-paste confirmation skeleton ('Let me confirm I understand: ...'), concrete environment checks ('import cuopt', 'curl http://localhost:8000/cuopt/health'), and a package/interface table. Not 5 because no complete end-to-end solver invocation example is shown; not 3 because the guidance is concrete and executable rather than pseudocode.

4 / 5

Workflow Clarity

An explicit sequence exists ('Formulate once carefully (with verified understanding), solve, then sanity-check the result... Decide, implement, verify, then move on') with explicit checkpoints (MUST Verify Understanding, Check Results, mandatory post-correction check). Not 5 because the sections are organized thematically rather than as one unified ordered workflow; not 3 because validation checkpoints are explicit, not implicit or missing.

4 / 5

Progressive Disclosure

A single SKILL.md with clear, well-ordered section headers; one clearly signaled one-level-deep reference (skills/skill-evolution/SKILL.md) plus external documentation links in Resources. No bundle files exist and no bulk content needs offloading, but at ~215 lines it exceeds the under-50-line simple-skill exemption for a top score.

4 / 5

Total

15

/

20

Passed

Description

65%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.

The description is compact and well-bounded, with a clear niche, an explicit anti-conflict pointer to cuopt-developer, and good domain keywords. Its main weakness is the missing explicit 'Use when...' trigger clause, which caps completeness and weakens when-to-use guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user is calling the cuOpt SDK, installing it, or deploying the cuOpt server (routing, LP, MILP, or QP problems).'

Include spelled-out synonyms alongside abbreviations (e.g. 'linear programming (LP)', 'mixed-integer linear programming (MILP)', 'solver', 'optimization') to broaden natural trigger coverage.

Enumerate one or two concrete actions beyond 'calling' (e.g. writing solver input, checking solution status) to raise specificity.

DimensionReasoningScore

Specificity

Names the domain concretely ('calling NVIDIA cuOpt (routing/LP/MILP/QP/install/server)') but the only action described is 'calling' — no list of several concrete capabilities. Matches 'names domain and 1-2 concrete actions, but not comprehensive', not 4 (no several specific actions) and not 2 (the parenthetical adds real scope beyond a bare domain).

3 / 5

Completeness

Has a clear 'what' ('Base rules for end users calling NVIDIA cuOpt') but the 'when' is only weakly implied by 'for end users calling' — there is no explicit 'Use when...' clause, which caps completeness at 3 per the judging guidelines. The explicit exclusion ('Not for cuOpt internals') narrows scope but is not a trigger.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'routing', 'install', 'server', 'cuOpt', plus practitioner terms 'LP/MILP/QP'. Falls short of 5 because spelled-out synonyms like 'linear programming', 'solver', or 'optimization' are missing; above 3 because coverage is solid, not partial.

4 / 5

Distinctiveness Conflict Risk

Clear niche with an explicit boundary — 'Not for cuOpt internals — use cuopt-developer for those' — that both distinguishes it from sibling skills and prevents wrong-skill triggering. Minimal conflict risk.

5 / 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

openai/plugins

Path

plugins/nvidia/skills/cuopt-user-rules/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.