nvidia-skill-finder
Use for NVIDIA-related requests where an NVIDIA skill might help, even if the user did not ask for a skill. Trigger on NVIDIA products, hardware, software,…
Exports sanitized metadata, parameters, reproducibility details, quality metrics, and optional review artifacts from Medical AI inference runs or evidence packs to MLflow. Use after inference, including NV-Generate runs; not for live training tracking, model registration, or
$ npx -y skills add NVIDIA/skills --skill medtech-model-evidence-export --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/medtech-model-evidence-exportContext preview
The summary Claude sees to decide when to auto-load this skill.
Exports sanitized metadata, parameters, reproducibility details, quality metrics, and optional review artifacts from Medical AI inference runs or evidence packs to MLflow. Use after inference, including NV-Generate runs; not for live training tracking, model registration, or
name: medtech-model-evidence-export description: Exports sanitized metadata, parameters, reproducibility details, quality metrics, and optional review artifacts from Medical AI inference runs or evidence packs to MLflow. Use after inference, including NV-Generate runs; not for live training tracking, model registration, or clinical use. license: Apache-2.0 allowed-tools: Bash permissions: [env, file_read, file_write, network, shell] metadata: author: 'NVIDIA MedTech <noreply@nvidia.com>'
Mirror an existing medical-inference result or evidence pack into MLflow after the run and emit the `export_result` JSON contract. Keep the original evidence pack as the source of truth. Training skills should add MLflow inside their training loops instead.
1. Run `scripts/export_evidence_pack.py` in the default `dry-run` mode. 2. Inspect `params`, `metrics`, `artifact_plan`, and `mlflow.note.content`. 3. Choose `--mode local` or `--mode databricks` only after checking the target. 4. Keep `--artifact-policy metadata` unless the target is approved for images. 5. For `preview` or `all` in a live mode, also pass `--confirm-medical-artifact-upload`. 6. Keep `--source-ref`, `--note`, config filenames, and artifact filenames free of patient or secret identifiers; always review the dry-run output first.
Hosts with a script helper can use `run_script("scripts/export_evidence_pack.py", args=["PACK_OR_RESULT", "--mode", "dry-run"])`.
| Script | Purpose | Arguments | |---|---|---| | `scripts/export_evidence_pack.py` | Export post-hoc inference evidence through MLflow. | `PACK_OR_RESULT --mode dry-run --artifact-policy metadata` |
configured Databricks profile. The declared network endpoint is `https://<caller-provided-mlflow-or-databricks-workspace>`; Docker and GPU are not required.
`<current-working-directory>/mlruns`.
Preview the export without contacting MLflow:
python skills/medtech-model-evidence-export/scripts/export_evidence_pack.py \ runs/inference_pack --mode dry-run --artifact-policy metadata
Export a direct NV-Generate result with reproducibility metadata:
python skills/medtech-model-evidence-export/scripts/export_evidence_pack.py \ runs/nv-generate/result.json \ --mode local \ --experiment-name medical-ai-inference \ --config configs/chest_lung_tumor.json \ --seed 0 \ --source-ref git:61c4ec709b84cad468852243c48e250bec732074
Log downsampled slice previews, but not raw NIfTI files:
python skills/medtech-model-evidence-export/scripts/export_evidence_pack.py \ runs/nv-generate/result.json \ --mode databricks \ --experiment-name /Shared/medical-ai-inference \ --artifact-policy preview \ --confirm-medical-artifact-upload
`--artifact-policy all` additionally uploads discovered or explicitly supplied NIfTI images and masks, subject to `--max-artifact-mb`. Use `--image` and `--mask` when paths are not present in the result JSON.
The exporter logs:
(generic intensity statistics otherwise), a documented intensity-SNR heuristic, mask foreground percentage, and mapped tumor volume percentage when a tumor label mapping is available;
raw image/mask artifacts only under the explicit `all` policy.
checks, not image-quality or clinical-performance claims.
caller must approve the destination and data policy before upload.
source evidence pack.
| Error | Cause | Fix | |---|---|---| | Evidence source not recognized | No direct result JSON or pack `manifest.json`. | Pass the result file, evidence-pack directory, or trusted-run root. | | MLflow import fails | Live mode lacks the declared package. | Install `mlflow>=2.10,<4` or use `--mode dry-run`. | | Preview/all confirmation error | A live image upload was not acknowledged. | Review the destination, then pass `--confirm-medical-artifact-upload`. | | Referenced image not found | Result paths moved after inference. | Pass current paths with `--image` and `--mask`. |
Official, NVIDIA-verified Agent Skills for Claude Code, Codex, and other coding agents.
Use for NVIDIA-related requests where an NVIDIA skill might help, even if the user did not ask for a skill. Trigger on NVIDIA products, hardware, software,…
Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, nullable semantics, and…
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras;…
Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample…