dataset-preprocessing
Skill4 starsChanged 7 months agoMITView on GitHub
Provides preprocessing pipelines and techniques for radiology datasets used in AI development. Use when user mentions "preprocess radiology data", "DICOM preprocessing", "image normalization", "data augmentation", or needs to prepare datasets.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- public/llms.txtllms.txt
- ai-detection-pipelineSkill
- ai-quality-reviewSkill
- ai-report-assistSkill
- care-gap-closureSkill
- cross-reference-linkingSkill
- dicom-web-querySkill
- followup-trackingSkill
- guideline-integrationSkill
- image-quality-auditSkill
- imaging-referralSkill
- imaging-study-reviewSkill
- llm-radiology-useSkill
- modality-detectionSkill
- model-validationSkill
- pacs-workflowSkill
- patient-education-materialSkill
- patient-results-letterSkill
- radiology-contextSkill
- radiology-dataset-guideSkill
- radiology-metricsSkill
- radiology-report-analysisSkill
- radiology-researchSkill
- report-quality-reviewSkill
- structured-reportingSkill
The file
Files
Dataset Preprocessing Skill
Triggers
- "preprocess radiology data"
- "DICOM preprocessing"
- "image normalization"
- "data augmentation"
- "quality control pipeline"
- "mask generation"
- "multi-site harmonization"
- "training data preparation"
Parameters
input_format(required): Source data formatdicom- DICOM filesnifti- NIfTI volumesmetadata- Header/excel datamixed- Multiple formats
task_type(required): Downstream ML taskdetection- Object/bounding box detectionsegmentation- Pixel-level segmentationclassification- Image classificationregression- Continuous value prediction
modality(optional): Imaging modalitymulti_vendor(optional): Boolean for multi-site/multi-vendor datadataset_scale(optional): Small (<1K), medium (1K-100K), large (>100K)
Preprocessing Components
Image Processing
- Intensity normalization (z-score, min-max, percentile-based)
- Windowing/leveling for CT/MRI
- Resampling to isotropic voxel size
- Brain extraction (skull stripping)
- Bias field correction for MRI
Quality Control
- Automated quality scoring
- Artifact detection
- Contrast-to-noise ratio
- Resolution verification
- Human-in-the-loop review for edge cases
Augmentation
- Geometric: rotation, flip, scale, elastic deformation
- Intensity: noise, contrast, brightness
- Modality-specific: CT windowing variants, MRI sequence mixing
- Generative: synthetic data augmentation
Format Conversion
- DICOM to NumPy/PyTorch/TensorFlow
- DICOM to NIfTI for volumetric data
- Annotation format conversion (CSV, COCO, YOLO, Pascal VOC)
Output Format
Returns structured JSON with:
- Processing pipeline steps
- Code snippets for each transformation
- Validation checks and statistics
- Expected output specifications
- Common pitfalls and mitigations
Usage Examples
input_format: dicom
task_type: detection
modality: CT
multi_vendor: true
input_format: nifti
task_type: segmentation
dataset_scale: largeDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

