SKILLEMALL.ai

AF dynamo-recipe-runner

Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 1 717 tokens Open the sourceclawhub.ai analyzed 26 h ago

Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes.

As a process F 68/100 · Will not run — References files that are not bundled: scripts/check_router_health.py, references/k8s-recipe-workflow.md, scripts/recipe_tool.py

AnalyzerKubernetesInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
F
68/100
Will not run
References files that are not bundled: scripts/check_router_health.py, references/k8s-recipe-workflow.md, scripts/recipe_tool.py
Tools and files w 18
0
Progress reporting w 2
0
Running it twice w 4
30
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: scripts/check_router_health.py
  • warning missing-ref reference to a missing file: references/k8s-recipe-workflow.md
  • warning missing-ref reference to a missing file: scripts/recipe_tool.py

Process rating: all ten parameters 68/100

Will not run. References files that are not bundled: scripts/check_router_health.py, references/k8s-recipe-workflow.md, scripts/recipe_tool.py
  • 0Tools and files. 3 referenced file(s) missing: scripts/check_router_health.py, references/k8s-recipe-workflow.md, scripts/recipe_tool.py
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 9 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 29 steps
  • 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 1717 tokens
  • low 11 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)
  • -2localhost URLs: will not work for another user
  • +2Single-language instructions
  • +3Description length 223: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 29 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)
  • +1License stated

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