Back to Skills

nv-segment-ctmr

Used for running NV-Segment-CTMR on CT or MRI NIfTI volumes and recording label-map evidence. Not for clinical interpretation.

2,791stars324forksUpdated 8/5/2026

Security Assessment

Safe(91/100)
Security Score91/100

About nv-segment-ctmr

nv-segment-ctmr is a thin wrapper skill from the NVIDIA MedTech Team that runs the upstream NV-Segment-CTMR (VISTA3D) MONAI segmentation bundle on CT or MRI NIfTI volumes and records the resulting label-map as evidence. It solves the problem of reproducibly invoking a complex medical-imaging model: rather than reimplementing inference, the skill shells out to the documented `python -m monai.bundle run` entrypoint and then inspects the produced NIfTI label map against an output schema. The documentation is emphatic that this is not for clinical interpretation, diagnosis, regulatory submission, or treatment planning.

The workflow centers on a single entrypoint, `scripts/run_ctmr.py`, which takes an input volume, a modality flag (CT_BODY, MRI_BODY, or MRI_BRAIN), and an output directory, and can optionally accept label prompts. It performs automatic "segment everything" inference, loads label names from upstream configs when available, and emits a JSON result plus verifier guidance. A skill_manifest.yaml declares inputs (ct_or_mr_volume), outputs (label_map, result_json), validation gates, and side effects such as caching model assets under the Hugging Face cache and contacting github.com or huggingface.co during one-time setup. GPU/CUDA may be required, and a pinned set of Python packages (monai, numpy<2, nibabel, scipy, etc.) must be installed.

The target users are medical-imaging engineers, MONAI/VISTA3D practitioners, and ML pipeline builders who need a deterministic, evidence-recording wrapper around CT/MRI whole-body or brain segmentation. It is explicitly a research/engineering harness, not a clinical tool, so its realistic use cases are benchmarking, pipeline integration, and label-map evidence generation rather than any patient-facing decision.

FAQ

What inputs and outputs does it work with?

It takes a CT or MRI NIfTI volume plus a modality flag (CT_BODY, MRI_BODY, or MRI_BRAIN) and writes a segmentation label map and a result JSON under a caller-provided output directory.

Can I use this for clinical diagnosis?

No. The documentation repeatedly states it makes no clinical, diagnostic, regulatory, or treatment-planning claims and is not for clinical deployment or autonomous diagnosis.

Does it implement the segmentation model itself?

No. It is a thin wrapper; all inference, preprocessing, and postprocessing are delegated to the upstream NV-Segment-CTMR MONAI bundle. The wrapper only invokes the documented entrypoint and inspects the output.

What are the runtime prerequisites?

A GPU/CUDA when declared by the manifest, and a pinned set of Python packages (monai>=1.5,<1.6, numpy<2, nibabel, scipy, typer, PyYAML, fire, huggingface_hub, pytorch-ignite, einops). Model assets may be fetched from Hugging Face during one-time setup.

Why must MRI_BRAIN inputs be preprocessed?

The default path runs automatic inference, but MRI_BRAIN inputs must already follow the upstream brain preprocessing requirements before being passed in.

All Files

10 files
evals/evals.json1.2 KB
View
tests/test_run_ctmr.py3.9 KB
View
SKILL.md8.8 KB
View
BENCHMARK.md3.9 KB
View
skill.oms.sig5.6 KB
View
scripts/run_ctmr.py20.4 KB
View
skill_manifest.yaml7.0 KB
View
skill-card.md3.9 KB
View
fixtures/README.md0.6 KB
View
validators/output_schema.json4.6 KB
View

Install nv-segment-ctmr

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

nvidia/skills