How do I install the Dicom Metadata Extract skill?

Run npx skillmds@latest add nvidia/dicom-metadata-extract in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Dicom Metadata Extract skill do?

Extracts selected metadata from a DICOM file and flags standard-tag PHI presence. Not for anonymization or clinical use. It is listed under Data & Analytics, Coding & Dev Tools, Data Analysis on SkillMD.

Is Dicom Metadata Extract safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dicom Metadata Extract?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dicom Metadata Extract free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Dicom Metadata Extract?

NVIDIA (@nvidia) published this skill as a verified publisher. Their other Agent Skills are listed on their SkillMD profile.

Dicom Metadata Extract by nvidia — Agent Skill

Name: Dicom Metadata Extract
Rating: 4.2 (5 reviews)
Author: NVIDIA

File contents

DICOM Metadata Extract

Purpose

Used for extracting selected metadata from one DICOM file and flagging standard-tag PHI presence. Not for anonymization or clinical use.
Use the wrapper exactly as documented; do not replace the upstream entrypoint with a handwritten implementation.
Manifest I/O: inputs are dicom_path; outputs are metadata_json.

Instructions

Read skill_manifest.yaml before changing arguments, side effects, or validation gates.
Run scripts/extract_metadata.py through the documented command below; keep outputs under a caller-provided run directory.
If a host agent exposes run_script, use run_script("scripts/extract_metadata.py", args=[...]); otherwise run the Bash/Python command shown below.
Check the emitted JSON and run medagent.verifiers.dicom_metadata_quality_v1 on evidence packs before treating the run as reviewed evidence.

Available Scripts

Script	Purpose	Arguments
`scripts/extract_metadata.py`	Primary entrypoint declared by skill_manifest.yaml.	`PATH_TO_DICOM [--output OUT.json]`

Prerequisites

Runtime requirements: Python packages listed in runtime.side_effects.pip_packages.
Run commands from the repository root unless an existing section below says otherwise.

Limitations

Small PS3.15-inspired standard-tag subset only; not a complete Basic Application Confidentiality Profile implementation.
Private tags not checked
Burnt-in pixel PHI not detected
Multi-frame handling minimal
Not for clinical deployment, regulatory de-identification, autonomous diagnosis, patient-facing use.

Troubleshooting

Error	Cause	Fix
Missing dependency or import error	Runtime package drift from `skill_manifest.yaml`.	Install the packages declared in the manifest or use the documented setup command.
Empty or schema-invalid output	Wrong input path, unsupported modality, or upstream failure.	Re-run with a known fixture and inspect the wrapper JSON plus stderr.
Validation gate failure	Output violated a declared engineering invariant.	Keep the failed evidence pack and use the gate message to repair inputs or wrapper code.

Reads one DICOM file with pydicom and emits JSON on stdout.

python scripts/extract_metadata.py PATH_TO_DICOM
python scripts/extract_metadata.py PATH_TO_DICOM --output result.json

Output includes transfer_syntax, modality, grouped study/series/image metadata, phi_present, and phi_tags_found.

Use this as the smallest end-to-end example of a Medical AI Skills skill. Do not use it for anonymization, private-tag review, pixel PHI detection, or clinical interpretation.

For second-pass evidence review, generate a trusted run:

python -m eval_engine.run_trusted skills/dicom-metadata-extract \
  --fixture skills/dicom-metadata-extract/fixtures/sample_ct.dcm \
  --out runs/dicom_metadata_trusted

---name: dicom-metadata-extractdescription: Extracts selected metadata from a DICOM file and flags standard-tag PHI presence. Not for anonymization or clinical use.license: Apache-2.0---# DICOM Metadata Extract## Purpose- Used for extracting selected metadata from one DICOM file and flagging standard-tag PHI presence. Not for anonymization or clinical use.- Use the wrapper exactly as documented; do not replace the upstream entrypoint with a handwritten implementation.- Manifest I/O: inputs are `dicom_path`; outputs are `metadata_json`.## Instructions- Read `skill_manifest.yaml` before changing arguments, side effects, or validation gates.- Run `scripts/extract_metadata.py` through the documented command below; keep outputs under a caller-provided run directory.- If a host agent exposes `run_script`, use `run_script("scripts/extract_metadata.py", args=[...])`; otherwise run the Bash/Python command shown below.- Check the emitted JSON and run `medagent.verifiers.dicom_metadata_quality_v1` on evidence packs before treating the run as reviewed evidence.## Available Scripts| Script | Purpose | Arguments ||---|---|---|| `scripts/extract_metadata.py` | Primary entrypoint declared by skill_manifest.yaml. | `PATH_TO_DICOM [--output OUT.json]` |## Prerequisites- Runtime requirements: Python packages listed in `runtime.side_effects.pip_packages`.- Run commands from the repository root unless an existing section below says otherwise.## Limitations- Small PS3.15-inspired standard-tag subset only; not a complete Basic Application Confidentiality Profile implementation.- Private tags not checked- Burnt-in pixel PHI not detected- Multi-frame handling minimal- Not for clinical deployment, regulatory de-identification, autonomous diagnosis, patient-facing use.## Troubleshooting| Error | Cause | Fix ||---|---|---|| Missing dependency or import error | Runtime package drift from `skill_manifest.yaml`. | Install the packages declared in the manifest or use the documented setup command. || Empty or schema-invalid output | Wrong input path, unsupported modality, or upstream failure. | Re-run with a known fixture and inspect the wrapper JSON plus stderr. || Validation gate failure | Output violated a declared engineering invariant. | Keep the failed evidence pack and use the gate message to repair inputs or wrapper code. |Reads one DICOM file with pydicom and emits JSON on stdout.```bashpython scripts/extract_metadata.py PATH_TO_DICOMpython scripts/extract_metadata.py PATH_TO_DICOM --output result.json```Output includes `transfer_syntax`, `modality`, grouped study/series/imagemetadata, `phi_present`, and `phi_tags_found`.Use this as the smallest end-to-end example of a Medical AI Skills skill. Do not useit for anonymization, private-tag review, pixel PHI detection, or clinicalinterpretation.For second-pass evidence review, generate a trusted run:```bashpython -m eval_engine.run_trusted skills/dicom-metadata-extract \ --fixture skills/dicom-metadata-extract/fixtures/sample_ct.dcm \ --out runs/dicom_metadata_trusted```

Frequently asked questions

Dicom Metadata Extract