Radiology Crossmodal Mapping logo

Radiology Crossmodal Mapping

CommunityPopular
huang-sir1
radiology-crossmodal-mapping

Use when an imaging study must map radiology phenotypes or habitats to single-cell, spatial-omics, or pathology-derived cell states across patients, lesions, specimens, regions, or time points. Designs paired, weakly paired, or unpaired cross-modal mapping; audits alignment, deconvolution, label transfer, contrastive learning, validation, scale mismatch, and biological-claim limits. Never treats unpaired public omics as direct patient-level mechanism proof.

Overview

Publisherhuang-sir1
Repositoryradiology-skills
Skill nameradiology-crossmodal-mapping
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 Crossmodal Mapping 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-crossmodal-mapping .claude/skills/radiology-crossmodal-mapping
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Radiology Crossmodal Mapping 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 Crossmodal Mapping 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 Crossmodal Mapping 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.

Radiology Cross-Modal Mapping

Use this skill when the central problem is how to align an imaging phenotype or habitat with single-cell, spatial-omics, or pathology-derived cellular states. Make the mapping unit and its uncertainty explicit before choosing a method.

Core stance

  • Map at the finest common unit with verified correspondence; coarsen until defensible. Never promote cohort concordance to patient-, lesion-, region-, or cell-level evidence.
  • Classify each link as direct, weak, unpaired, or unresolved; separately classify cohort completeness as fully or partially paired.
  • Treat registration, sampling, timing, treatment, and spatial-scale mismatch as analysis variables, not footnotes.
  • Audit identity, eligibility, and provenance metadata before splitting; do not use outcomes, biological measurements, or apparent correspondence to resolve links. Then split by patient and, when applicable, center, keeping every fitted step inside training data.

Required intake

Collect the phenotype, assay, anatomy, endpoint, cohorts/centers, hierarchy identifiers, dates, intervening treatment, registration evidence, modality missingness, batch/site variables, intended claim, and validation material. Mark unknown or conflicting links as unresolved.

Create a mapping-unit table before analysis:

Imaging recordVerified patientLesionImaging/timeSpecimen/sectionRegion/cell stateLink correspondenceFinest verified common unitUncertainty
one row per proposed linkID/noneIDdate/phaseID(s)ID/labeldirect/weak/unpaired/unresolvedpatient/lesion/regionsource/magnitude

Add a cohort summary stating eligible counts, modality availability, and whether completeness is fully or partially paired. See alignment and pairing for definitions, scale mismatch, and permitted inference.

Workflow

  1. Define the estimand. State the imaging feature or habitat, cellular state or spatial neighborhood, shared unit, endpoint, direction of mapping, and whether the aim is discovery, prediction, annotation transfer, or biological corroboration.
  2. Audit metadata before splitting. Using identity, provenance, modality availability, dates, and prespecified eligibility only, trace patient -> lesion -> specimen -> section -> region -> cell. Assign link correspondence and cohort completeness; freeze unresolved links. Do not inspect outcomes, expression, cell states, imaging features, or biological plausibility.
  3. Split, then align. Split eligible patients and reserve centers when applicable. Apply the prespecified finest common unit with verified metadata correspondence and coarsen until defensible; learn any image-, omics-, or biology-driven alignment in training only.
  4. Choose the mapping route. Match pseudobulk, deconvolution, canonical correlation, contrastive mapping, graph alignment, or habitat linkage to the link status, scale, and sample size. Transfer labels across imaging and omics only through a paired bridge, shared measured features, or an independently validated cross-modal mapper; otherwise transfer within omics and validate the imaging association separately.
  5. Lock leakage-safe validation. Keep feature selection, habitat discovery, normalization, anchor learning, label transfer, deconvolution tuning, embedding, graph construction, and threshold selection inside training. Add held-out-center or external validation when transportability is claimed.
  6. Run controls. Include mapping permutations, biologically implausible or negative regions, null features, method-specific nulls, and site/batch-aware baselines.
  7. Run sensitivity analyses. Vary registration tolerance, temporal window, aggregation level, habitat definition, cell-state reference, preprocessing, covariates, and borderline links.
  8. Validate biology. Prefer an independent cohort and orthogonal IHC, multiplex immunofluorescence, in situ hybridization, pathology, or separately measured spatial evidence.
  9. Bound claims. Tie each conclusion to its link status, cohort completeness, shared unit, validation, and unresolved alternative explanations.

Open mapping and validation to select a method and specify patient/center separation, negative controls, sensitivity analyses, external validation, and orthogonal biological validation.

Output contract

Return the applicable components:

  1. Mapping question: phenotype, cell state, purpose, direction, and estimand.
  2. Mapping-unit table: hierarchy, dates, link status, verified common unit, uncertainty.
  3. Pairing/alignment audit: completeness, mismatch, exclusions, permitted inference.
  4. Mapping plan: method, assumptions, preprocessing, covariates, simple baseline.
  5. Leakage-safe validation: patient/center splits and train-only operations.
  6. Controls/sensitivities: nulls and alternative alignment, timing, aggregation, references.
  7. Validation plan: internal, external, orthogonal evidence, success criteria.
  8. Bounded claims: supported wording, prohibited wording, uncertainty, missing inputs.

Routes

  • Use radiology-radiogenomics when general imaging-omics association, integration, prediction, or biological interpretation is central and cross-scale alignment is not the primary problem.
  • Route annotation/registration to radiology-annotation, inference/resampling to radiology-stats, representation design to radiology-deep-learning, reporting to radiology-reporting, and data provenance/sharing to radiology-data.

Red lines

  • Do not treat unpaired public omics or a reference atlas as direct patient-level, lesion-level, or mechanistic proof.
  • Do not call disease-, anatomy-, or time-matched different patients weakly paired; without a shared verified patient key they are unpaired and support cohort-level inference only.
  • Do not call deconvolved or transferred labels directly measured cells.
  • Do not transfer labels directly between imaging and omics without a paired bridge, shared measured features, or an independently validated cross-modal mapper.
  • Reserve co-localized for directly registered regional evidence; describe patient- or lesion-level relationships as associated or correlated.
  • Do not call evaluation independent when a test patient appears in an atlas, mapper-training set, or pretrained reference. Exclude the overlap or label the evaluation non-independent/model-exposed.
  • Do not mix cells, regions, lesions, or time points from one patient across training and test sets.
  • Do not fit habitats, anchors, embeddings, thresholds, or feature selection on held-out data.
  • Do not use causal or therapeutic language without an appropriate causal or experimental design.
  • Never invent identifiers, pairings, registration quality, biological associations, validation results, or missing metadata.

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 Crossmodal Mapping AI skill do?

Use when an imaging study must map radiology phenotypes or habitats to single-cell, spatial-omics, or pathology-derived cell states across patients, lesions, specimens, regions, or time points. Designs paired, weakly paired, or unpaired cross-modal mapping; audits alignment, deconvolution, label transfer, contrastive learning, validation, scale mismatch, and biological-claim limits. Never treats unpaired public omics as direct patient-level mechanism proof.

Why use Radiology Crossmodal Mapping on TypingMind?

Because you install it once and use it with any model. Radiology Crossmodal Mapping 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 Crossmodal Mapping 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-crossmodal-mapping. 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 Crossmodal Mapping?

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 Crossmodal Mapping?

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

Is the Radiology Crossmodal Mapping 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 👇