SkillAgentSearch skills...

dicom-metadata-extract

Used for extracting selected metadata from one DICOM file and flagging standard-tag PHI presence. Not for anonymization or clinical use.

Install / Use

npx skills add NVIDIA/skills --skill dicom-metadata-extract

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Tags

Our assessment of dicom-metadata-extract

dicom-metadata-extract scores 87/100 on our quality scale, 349th of 770 Content & Media skills we index (top 46%).

Its SKILL.md is 3.2 KB long, split into 7 sections with 2 code examples: a solid amount of guidance for an agent.

With 3,421 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
16/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 5 days ago, so dicom-metadata-extract is actively maintained.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

dicom-metadata-extract compared with similar skills

All 4 of these similar skills score higher than dicom-metadata-extract; compare them before choosing.

SkillScoreStarsUpdatedFormat
dicom-metadata-extract (this skill)by NVIDIA873.4k5d agoSKILL.md
siyuanby siyuan-note10046.5ktodayMCP Server
algorithmic-artby anthropics100177.9k6d agoSKILL.md
pptxby anthropics100177.9k6d agoSKILL.md
designby nextlevelbuilder100130.2k7d agoSKILL.md

Frequently asked questions

How do I install dicom-metadata-extract?
Run npx skills add NVIDIA/skills --skill dicom-metadata-extract. The install tabs above show the steps for each supported agent.
Which AI agents does dicom-metadata-extract work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is dicom-metadata-extract safe to use?
It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is dicom-metadata-extract still maintained?
The repository was last updated 5 days ago, so dicom-metadata-extract is actively maintained.

name: dicom-metadata-extract description: Used for extracting selected metadata from one DICOM file and flagging standard-tag PHI presence. Not for anonymization or clinical use. license: Apache-2.0 allowed-tools: Bash permissions: [file_read, file_write, shell] metadata: author: 'NVIDIA MedTech Team' tags: - MedTech - DICOM - metadata

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

Related Skills

View on GitHub
GitHub Stars3.4k
CategoryContent
Updated5d ago
Forks412

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions