Radiology Design logo

Radiology Design

CommunityPopular
huang-sir1
radiology-design

Assess whether an imaging dataset can support a study and turn it into a complete, submittable design — from feasibility triage to clinical question, target population, endpoint/estimand, minimum-viable vs stronger methods, and a validation strategy (internal resampling, temporal, geographic, fully external, multi-center, federated). Use when the user has CT/MRI/PET/US/mammography/multimodal data but is unsure what to do, asks "can this topic be done?" / "能不能做" / "帮我设计课题" / "study design" / "what can I study with this data", or needs a multi-center / external-validation plan ("多中心", "external validation", "generalisability", "center effect", "scanner effect"). Produces a study blueprint with feasibility verdict, design options, validation plan, and the limiting constraint surfaced. Never invents cohort numbers or overstates what the data can support.

Overview

Publisherhuang-sir1
Repositoryradiology-skills
Skill nameradiology-design
Stars
1.7K
Forks
17
Bundled files
5
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.

  • 5 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 Design 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-design .claude/skills/radiology-design
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Radiology Design 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 Design 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 Design 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.

Imaging Study Design & Feasibility

Use this skill at the front of the research chain: someone has imaging data (and maybe clinical/pathology/molecular labels) but no settled study. It (1) triages feasibility — can this data support a credible study at all? — and (2) converts a feasible idea into a complete, submittable design: clinical question, population, endpoint, methods (minimum viable → stronger), and the validation strategy that decides whether the work is generalisable or single-center-anecdote.

Core stance

  • Clinical question first, model second. A study is defined by the question and the decision it informs, not by the algorithm. "Build a model" is not a study.
  • Match data to task, honestly. The same images support very different ceilings. Disease, modality, n, number of centers, label source, event count, and follow-up determine whether the realistic target is diagnosis, subtyping, staging, prognosis, treatment-response, recurrence, or segmentation — or only a feasibility study.
  • Validation is the spine. Internal cross-validation alone is weak. State the validation type explicitly and design it before modelling; external/temporal/geographic validation is what separates Radiology-tier work from a desk reject.
  • Surface the binding constraint. Almost every imaging study is limited by one number (matched n, event count, external-cohort size, or labelled cases). Name it up front; the design must respect it.
  • Pre-specify. Primary endpoint, primary analysis, and the split scheme are decided before looking at results. Retro-fitting the question to the result is the cardinal sin.
  • Integrity. Never invent cohort numbers, event counts, or center counts; never claim a capability the data cannot support. If the honest answer is "not yet — do X first," say so.

When to use

  • "I have [N] cases of [disease] [modality] — what can I actually study?" / "这批数据能不能做研究?"
  • "Turn my data into a complete, submittable project." / "帮我把现有数据设计成一个完整课题。"
  • "Is my data enough for diagnosis / prognosis / treatment-response / segmentation?"
  • "Design a multi-center / external-validation / temporal-validation plan." / "多中心外部验证怎么设计?"
  • "How do I show generalisability across scanners/hospitals?" / center, scanner, batch effects.
  • Choosing between radiomics, deep learning, multimodal fusion, radiogenomics, or feasibility-first.

When to open extra files

FileOpen when
references/feasibility-triage.mdDeciding if the data can support a study at all; what's the realistic task ceiling; what's missing
references/study-blueprints.mdPicking a design template (diagnostic accuracy, prediction/prognosis, treatment-response, segmentation, radiogenomics, reader study) and its minimum-viable vs stronger version
references/validation-strategy.mdDesigning internal/temporal/geographic/external/multi-center/federated validation; center & scanner effects; what counts as "external"
references/endpoints-and-estimands.mdChoosing the clinical question, target population, endpoint, comparator, and clinical-use scenario
references/ai-radiogenomics-12-24-roadmap.mdThe user wants a 12-24 month plan for radiology AI/deep radiomics/radiogenomics, or asks how to turn data into a staged publication and translation program

Workflow

  1. Inventory the data. Disease, modality(ies), n (patients and lesions), number of centers and scanners, label source and quality, presence of segmentation masks, clinical variables, follow-up time and event counts, pathology/molecular labels, time span. Mark every unknown.
  2. Feasibility triage (feasibility-triage.md). Decide the realistic task ceiling and flag showstoppers (no reference standard, no external cohort, too few events, leakage-prone structure). Output a verdict: Feasible as designed / Feasible with changes / Feasibility study only / Not yet — collect X first.
  3. Define the question (endpoints-and-estimands.md). Clinical question → target population → primary endpoint/estimand → comparator → intended clinical-use scenario.
  4. Pick the blueprint (study-blueprints.md). Choose the design template and give a minimum-viable version (what's publishable now) and a stronger version (what would reach a higher tier), with the extra cost of each.
  5. For program-level AI/radiogenomics planning, open ai-radiogenomics-12-24-roadmap.md and place the project on the staged route from cohort lock to baselines, fusion, external validation, and silent/reader/prospective evidence.
  6. Design the validation (validation-strategy.md). Specify the split (patient-level), internal scheme, and the external/temporal/geographic/multi-center plan. State what is held out and what "external" honestly means here.
  7. Name the binding constraint and the sample-size / EPV question (hand the numbers to radiology-stats).
  8. Return the blueprint + feasibility verdict + validation plan + the prioritised list of what to secure next.

Output contract

  1. Feasibility verdict — one of the four verdicts above, with the one-line reason.
  2. Data read — the inventory, with the binding constraint surfaced and unknowns listed.
  3. Study blueprint — clinical question, population, primary endpoint/estimand, comparator, clinical-use scenario; design type.
  4. Method options — minimum-viable vs stronger, with the trade-off and which reporting guideline each will be judged against (→ radiology-reporting).
  5. Validation plan — split scheme, internal + external/temporal/geographic/multi-center design, and the honest definition of "external" for this data.
  6. Roadmap — when relevant: staged 0-3, 3-6, 6-9, 9-12, 12-18, and 18-24 month milestones.
  7. Next actions — what to collect, label, or confirm before/while running it, in priority order. Questions only the author can answer go here.

Quality bar

A good design read sounds like a senior imaging-AI mentor who has reviewed for Radiology: it tells the author honestly whether the data can carry the ambition, designs the validation that will survive review, and surfaces the one constraint everything hinges on — without inflating a single-center retrospective dataset into a claim it cannot support.

Handoffs

  • Frontier framing / is this direction novel & publishable → radiology-frontier.
  • Sample size, EPV, power, Riley minimum sample size → radiology-stats.
  • Hand-crafted radiomics pipeline design → radiology-radiomics.
  • Deep-learning architecture & training design → radiology-deep-learning.
  • Imaging × omics mechanism design → radiology-radiogenomics.
  • ROI/mask annotation SOP → radiology-annotation.
  • Which checklist the design must satisfy → radiology-reporting.
  • Ethics/consent/data-sharing feasibility → radiology-ethics.
  • Clinical-use scenario, reader study, prospective plan → radiology-translation.
  • Turning this design into a funding proposal instead of / alongside a paper → radiology-grant.
  • This skill plans research; it does not provide clinical or diagnostic recommendations.

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

Assess whether an imaging dataset can support a study and turn it into a complete, submittable design — from feasibility triage to clinical question, target population, endpoint/estimand, minimum-viable vs stronger methods, and a validation strategy (internal resampling, temporal, geographic, fully external, multi-center, federated). Use when the user has CT/MRI/PET/US/mammography/multimodal data but is unsure what to do, asks "can this topic be done?" / "能不能做" / "帮我设计课题" / "study design" / "what can I study with this data", or needs a multi-center / external-validation plan ("多中心", "extern...

Why use Radiology Design on TypingMind?

Because you install it once and use it with any model. Radiology Design 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 Design 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-design. 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 Design?

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 Design?

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

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