SKILLEMALL.ai

BF cuopt-numerical-optimization-api

LP, MILP, and QP (beta) with cuOpt — Python, C, and CLI. Use when the user is solving LP, MILP, or QP with any cuOpt interface.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 1 140 tokens open source ↗ analyzed 4 h ago

LP, MILP, and QP (beta) with cuOpt — Python, C, and CLI.

As a process F 39/100 · Will not run — References files that are not bundled: references/python_api.md, references/c_api.md, references/cli_api.md

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
F
39/100
Will not run
References files that are not bundled: references/python_api.md, references/c_api.md, references/cli_api.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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-ref reference to a missing file: references/python_api.md
  • warning missing-ref reference to a missing file: references/c_api.md
  • warning missing-ref reference to a missing file: references/cli_api.md

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: references/python_api.md, references/c_api.md, references/cli_api.md
  • 0Tools and files. 3 referenced file(s) missing: references/python_api.md, references/c_api.md, references/cli_api.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 70When it triggers. States when to use, but not when not to
  • 85Steps. 10 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1140 tokens
  • 100Running it twice. No mutating operations

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
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 127: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 10 items
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.