Radiology Foundation Models logo

Radiology Foundation Models

CommunityPopular
huang-sir1
radiology-foundation-models

Use when an imaging study must select, adapt, fine-tune, or audit a pretrained medical imaging or vision-language foundation model. Covers zero-shot evaluation, linear probing, full fine-tuning, adapters, LoRA and other parameter-efficient tuning, prompt learning, domain adaptation, 2D/3D and image-text inputs, frozen tests, strong baselines, compute reporting, calibration, uncertainty, subgroups, and external validation. Warns against training a foundation model from scratch without adequate scale.

Overview

Publisherhuang-sir1
Repositoryradiology-skills
Skill nameradiology-foundation-models
Stars
1.7K
Forks
17
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by huang-sir1 on GitHub. Read the source before you install it.

Installation

Install the Radiology Foundation Models AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/huang-sir1/radiology-skills.git /tmp/radiology-skills
mkdir -p .claude/skills
cp -r /tmp/radiology-skills/radiology-skills/modules/radiology-foundation-models .claude/skills/radiology-foundation-models
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Radiology Foundation Models in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Radiology Foundation Models on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Radiology Foundation Models is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Foundation-Model Adaptation for Medical Imaging

Use this skill when a model with broad pretraining intended for adaptability across tasks is central to selection, adaptation, benchmarking, or audit. Treat it as a checkpoint with a specific pretraining history, input contract, and license—not as automatic evidence of robustness or clinical validity.

Core stance

  • Audit the model card, checkpoint, license, pretraining sources, deduplication, and possible evaluation overlap before adaptation.
  • Match modality, anatomy, dimensionality, channels/sequences, text interface, spatial resolution, task, and prediction-time inputs before considering model size.
  • Climb a prespecified adaptation ladder from the least trainable valid route. Include continued self-supervised or domain-adaptive pretraining only when authorized in-domain unlabeled data and a direct fine-tuning baseline make its added value testable.
  • Separate every patient and all of that patient's repeated examinations, lesions, slices, patches, or frames across development and evaluation. Choose site-held-out or temporal separation when the transportability estimand requires it; a same-site internal test is valid when clearly labeled.
  • Compare against strong task-specific and conventional transfer-learning baselines using identical eligible cohorts, split assignments, prediction-time information, and fair tuning rules.
  • Report calibration, uncertainty or abstention, clinically relevant subgroups, external validation, compute, reproducibility, checkpoint identity, and license.
  • Bound claims to the tested task, population, comparator, adaptation route, and validation domain.

Required intake

Collect the intended use, endpoint, unit of analysis, reference standard, target population, modality and input geometry, prediction-time inputs, paired text or prompts, cohort/site/time structure, repeated measures, candidate model cards/checkpoints/licenses, pretraining sources, labels/events, compute constraints, baselines, and validation material. Mark unknown pretraining overlap, prompt provenance, incompatible licenses, and unavailable frozen tests as unresolved risks.

When to open extra files

FileOpen when
references/adaptation-strategies.mdChoosing or comparing zero-shot, linear probing, partial/full tuning, adapters, LoRA, prompt learning, continued pretraining, or domain adaptation; specifying text or spatial prompts
references/evaluation-and-reporting.mdAuditing overlap/leakage, selecting patient/site/time splits, setting fair baselines and budgets, or reporting calibration, uncertainty, subgroups, external validation, compute, carbon, checkpoints, and licenses

Compact workflow

1. Define the estimand and model class

State the population, prediction time, available input, output, reference standard, intended use, unit, and primary metric. Confirm that each candidate has broad pretraining intended to support adaptability across tasks. Route a narrow single-task pretrained backbone and ordinary transfer learning to radiology-deep-learning.

2. Audit provenance and compatibility

Record architecture, checkpoint/hash, license, objective, pretraining modalities and sources, deduplication, intended use, limitations, and input contract. Match these to the downstream modality, anatomy, 2D/3D/temporal structure, text or prompt interface, and output. Classify each evaluation cohort as overlap excluded, overlap removed, model-exposed, or overlap unknown.

3. Lock the adaptation ladder

Include only valid rungs and justify exclusions:

  1. native zero-shot or prompt-based inference;
  2. frozen encoder with a linear or shallow probe;
  3. partial tuning;
  4. adapters, LoRA, prompt learning, or other parameter-efficient tuning;
  5. full fine-tuning;
  6. continued self-supervised/domain-adaptive pretraining followed by downstream adaptation;
  7. explicit domain adaptation for a prespecified source-target shift.

Define trainable components, prompts, objective, preprocessing, optimizer, tuning space, stopping, seeds, and checkpoint selection before test access. Use adaptation strategies for route-specific controls.

4. Freeze development and evaluation boundaries

Split by patient and keep all repeated or nested observations together. Let the estimand determine whether evaluation is same-site internal, temporal, site-held-out, or fully external; label it accurately. Fit preprocessing, prompt selection, representation pooling, calibration, and thresholds using authorized development data only. Keep the final test sealed until the pipeline is locked.

5. Lock fair baselines and resources

Include a clinically meaningful comparator when available, a strong task-specific model, conventional transfer learning, a frozen-feature baseline, and adaptation ablations needed to isolate the contribution. Use identical patients, splits, outcomes, prediction-time inputs, and a prespecified tuning-budget policy. Record actual parameters, trials, failures, hardware, memory, runtime, accelerator-hours, energy/carbon method when available, software, seeds, and hashes.

6. Evaluate reliability and transportability

Report task-appropriate performance with confidence intervals and paired comparisons. Add calibration and threshold behavior, uncertainty or abstention utility, prespecified subgroup and site/scanner results, and external evaluation when transportability is claimed. Follow evaluation and reporting for exposure, split, compute, checkpoint, and license disclosures.

7. Bound conclusions

State what the comparison supports and what remains untested. Retrospective metric improvement does not establish generality, causal understanding, clinical utility, fairness, safety, or deployment readiness. Unknown pretraining overlap prevents an unqualified independence claim.

Output contract

Return the applicable sections:

  1. Task and input contract — intended use, endpoint, unit, modality, geometry, and prediction-time inputs.
  2. Model-card and overlap audit — foundation-model eligibility, provenance, license, compatibility, overlap class, and unresolved risks.
  3. Adaptation ladder — included/excluded rungs, prompts, continued-pretraining objective, trainable components, budget, and rationale.
  4. Frozen validation design — patient/repeated-measure separation, estimand-driven site/time choice, train-only operations, test label, and external cohort.
  5. Baseline and budget table — comparators, identical inputs/splits, search policy, parameters, and compute.
  6. Reliability evaluation — task metrics, uncertainty, calibration, subgroups, shifts, and external results or plans.
  7. Reproducibility and release record — versions, hashes, seeds, hardware, runtime, energy/carbon, access, and licenses.
  8. Bounded claims and missing inputs — supported conclusion, prohibited extrapolations, failure modes, and required information.

Boundary, routes, and red lines

  • Use this module only when broad pretrained-model adaptability, adaptation, or exposure is central. Route narrow single-task pretrained backbones, ordinary ImageNet transfer, CNN/Transformer design, optimization, task heads, and input pipelines to radiology-deep-learning.
  • Route cohort design to radiology-design; performance inference to radiology-stats; annotation and reference standards to radiology-annotation; sharing and FAIR metadata to radiology-data; checklist audits to radiology-reporting; deployment and reader studies to radiology-translation; and evidence verification to radiology-search.
  • Never split repeated observations from one patient across development and evaluation.
  • Never call same-site internal evaluation external; do not require site or time separation when the estimand is internal performance.
  • For promptable segmentation, never conceal whether points, boxes, or masks came from ground truth, a human, or an upstream model; oracle prompts are not deployable prompts.
  • Never adapt on a frozen test set or call a model-exposed/unknown-overlap evaluation unqualified independent validation.
  • Never call ordinary supervised fine-tuning a newly trained foundation model or recommend foundation-model training from scratch without commensurate scale, diversity, compute, governance, and validation.
  • Never invent provenance, prompt effort, overlap checks, performance, compute, or validation.

This skill supports research design and audit, not patient-specific diagnosis, treatment advice, or authorization to use restricted data or checkpoints.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Radiology Foundation Models AI skill do?

Use when an imaging study must select, adapt, fine-tune, or audit a pretrained medical imaging or vision-language foundation model. Covers zero-shot evaluation, linear probing, full fine-tuning, adapters, LoRA and other parameter-efficient tuning, prompt learning, domain adaptation, 2D/3D and image-text inputs, frozen tests, strong baselines, compute reporting, calibration, uncertainty, subgroups, and external validation. Warns against training a foundation model from scratch without adequate scale.

Why use Radiology Foundation Models on TypingMind?

Because you install it once and use it with any model. Radiology Foundation Models is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Radiology Foundation Models in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/huang-sir1/radiology-skills/tree/main/radiology-skills/modules/radiology-foundation-models. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Radiology Foundation Models?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Radiology Foundation Models?

As many as you like. As long as a model supports skills, you can use Radiology Foundation Models with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Radiology Foundation Models AI skill free?

Yes. It is published on GitHub by huang-sir1 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇