科研 Skill
医学影像模型架构选型
model-selection
Picks a paper-grounded architecture family and vets a repo’s license and provenance. Use when choosing which model to use for a medical-imaging study.
SKILL.md
Model-Selection Skill
Two questions, in this order. Phases 1–3 answer a literature question with a stable answer: which architecture family suits the task. Phases 4–6 answer a provenance question: which concrete artifact — repository, revision, checkpoint — will be run, and what its numbers may claim. The skill writes decision notes and runs one stdlib gate; it never downloads, runs, trains or benchmarks a model, and it describes archetypes, not a live SOTA leaderboard.
Elsewhere: building the repo → /model-scaffold; profiling data and planning preprocessing →
/imaging-data; validation design, metrics, uncertainty, explainability → /model-assessment;
documenting a model you built → /model-card; an LLM/MLLM, including benchmark contamination in
that setting → /mllm-eval; AI-vs-expert reader study → /design-ai-benchmarking.
Workflow
Phase 1 — Frame the question
State the task (classification / segmentation / detection / synthesis / transfer), the modality and dimensionality (2-D vs 3-D volume), the labelled-data scale (events / structures, not just images), label availability (lots / few / unlabelled pool), and the constraints (class imbalance, small structures, interpretability, deployment compute).
Phase 2 — Walk the decision tree, read the family card
Follow references/index.md (task → constraints → default pick). It routes to
one card; each gives the source paper, core idea, when-to-use, medical-imaging use, reference
implementation, and the typical validation setup for that class.
| Card | Families |
|---|---|
references/classification.md | ResNet / DenseNet / EfficientNet / Inception / ConvNeXt / ViT / Swin / DeiT |
references/segmentation.md | U-Net / 3-D U-Net / V-Net / Attention & Residual U-Net / nnU-Net (+ ResEnc, MedNeXt, STU-Net) / SegResNet / Swin-UNETR / Mask R-CNN |
references/detection.md | nnDetection / Faster R-CNN + FPN / Mask R-CNN / RetinaNet / YOLO / DETR |
references/synthesis.md | Pix2Pix / CycleGAN / SPADE / diffusion (DDPM, latent) / VAE / fastMRI reconstruction |
references/foundation_models.md | SAM / MedSAM / MedSAM2 / nnInteractive / VISTA3D / TotalSegmentator / SegVol / BiomedCLIP / DINO / MAE / SimCLR / MoCo |
references/graph.md | GCN / GraphSAGE / GAT / GIN / BrainGNN for connectomes and population graphs (PyTorch Geometric / DGL; not scaffolded by /model-scaffold) |
Never recommend an architecture for a modality or data scale it does not suit (a from-scratch ViT on a few hundred images, 2-D slices for a volumetric structure) — the decision-tree constraints exist to prevent exactly that. If asked for "the best" model, say the zoo is a curated archetype map, not a current SOTA ranking.
Phase 3 — Write the architecture decision note
Write decisions/architecture_choice.md: the task, the chosen architecture, its source paper
(mandatory — the Methods cite it), the reason against the constraints, the runner-up and why not,
and the matching /model-scaffold template. Never invent a benchmark number or paper claim: cite it
(verify via /search-lit), or write [VERIFY] and ask. A reference without a /search-lit-confirmed
DOI/PMID is marked [UNVERIFIED - NEEDS MANUAL CHECK].
Phase 4 — Write the model dossier for the concrete artifact
When a concrete candidate exists (a GitHub repo, a Hugging Face checkpoint, a paper's released
weights), write model_dossier.json recording what is known; leave unknowns unstated, never
guessed — the gate turns an absence into a finding.
{
"model": "OrganSeg-3D v2.5.1",
"source": {"kind": "github", "url": "...", "version": "v2.5.1", "commit": "abc1234"},
"licence": {"spdx": "Apache-2.0", "verified_from": "LICENSE at commit abc1234"},
"intended_use": "research",
"weights": {"pretrained": false},
"task": {"model": "3d_ct_organ_segmentation", "study": "3d_ct_organ_segmentation"},
"reported_validation": [{"dataset": "ExampleBench", "metric": "Dice", "source": "J Ex 2021"}],
"developed_on": ["ExampleBench"],
"evaluation_arms": [{"name": "external", "dataset": "OtherCohort-2026"}],
"hardware": {"claimed": "any CUDA GPU", "verified_on": "GTX 1080 Ti", "verified": true}
}
Read each field from the artifact, not from memory:
- Licence — only from the licence file at the pinned revision, and record which file
(
verified_from). Never from a README badge, a model-card summary, or memory; an unstated licence isLICENCE_UNSTATED, never "probably MIT". developed_on— the paper's own account of where the method was built and tuned. It is the field people skip and the one the gate needs: a method that won a challenge was tuned on it.hardware.verified— true only after it actually ran. A support matrix is a different claim: a CUDA capability one compiler accepts may still be refused by another in the same stack.
Phase 5 — Gate the dossier
python3 scripts/check_model_provenance.py --dossier model_dossier.json \
--out qc/model_provenance.json --strict
Stdlib-only and network-free: nothing is fetched and no licence resolved online.
| Verdict | Severity | Fires when |
|---|---|---|
BENCHMARK_PROVENANCE_CONFLICT | Major | an evaluation arm uses a dataset the model was developed or tuned on |
EVAL_DATA_IN_TRAINING | Major | an evaluation arm's dataset is inside the pretraining corpus |
LICENCE_UNSTATED | Major | no licence recorded — not the same as a permissive one |
LICENCE_INCOMPATIBLE | Major | non-commercial / research-only licence under commercial or deployment intent |
WEIGHTS_PROVENANCE_UNKNOWN | Major | pretrained weights whose training corpus is not stated |
DEVELOPED_ON_UNSTATED | Major | the developed_on key is absent, so the conflict check could not run |
EVALUATION_ARMS_UNSTATED | Major | the evaluation_arms key is absent, so neither provenance check could run |
INTENDED_USE_UNSTATED | Major | intended_use is absent, so licence compatibility could not be checked |
TASK_MISMATCH | Minor | the model's task is not the study's task |
NO_VERSION_PIN | Minor | no commit, tag or revision |
VALIDATION_UNREPORTED | Minor | no reported validation (dataset + metric + source) |
HARDWARE_UNVERIFIED | Minor | hardware support claimed but never executed |
LICENCE_UNVERIFIED | Minor | a licence is named but not the file it was read from |
The gate flags a relationship, not a reputation: developed_on: ExampleBench passes cleanly as
long as no evaluation arm uses ExampleBench (the clean fixture proves this). Dataset names match as
token sequences with a small family-alias table — MSD Task09 Spleen matches MSD,
MS Cohort 2026 does not — never by substring.
An explicit empty list ("developed_on": []) states "none" and is not a finding; an absent key is.
intended_use must be research, commercial or clinical_deployment, and developed_on /
weights.trained_on must be lists of strings; anything else is an input error (exit 2), never a pass.
Known limits. LICENCE_INCOMPATIBLE recognises non-commercial / research-only markers in the
licence string (NC, non-commercial, research-only, in SPDX or spaced form). A free-text licence
that restricts use without those markers (e.g. "academic use only"), or a copyleft licence under
closed deployment, is not detected: read the licence file and record the conclusion yourself.
Phase 6 — Turn a Major into a study decision
A BENCHMARK_PROVENANCE_CONFLICT rarely means abandoning the model (it is often the best-engineered
option precisely because it was tuned hard). It changes what the arm may claim:
- Report that arm as a demonstration that the pipeline runs end to end, not as evidence the method works.
- Put the evidential weight on an arm whose data post-dates the model, and say so with dates.
- State the conflict in Methods and Limitations rather than leaving a reviewer to find it.
Never report a flagged arm as independent validation. An EVAL_DATA_IN_TRAINING arm is different in
kind: it produces a training-set score and cannot be reported as validation at all. Write this
arm-by-arm decision into the study record.
Outputs and hand-off
decisions/architecture_choice.md— the architecture decision note (Phase 3).model_dossier.json— the provenance record (Phase 4);qc/model_provenance.json— the audit (Phase 5).- The arm-by-arm decision (Phase 6).
Carry them to /model-scaffold (instantiate the template), /model-assessment (arm and validation
design, what each arm may claim, metrics), /model-card (provenance section), and /write-paper
(Methods cite the source paper; Limitations state any conflict). Gate regression:
bash scripts/check_model_provenance_challenge/verify.sh and
bash tests/test_model_provenance.sh.
示例提示词
帮我给这个结节检测任务选一个有论文支撑的模型架构。
所属插件
安装该插件会一并获得同领域的 58 个 Skill / MCP。
同插件的其他科研 Skill
- 医学AI论文检索优化Optimizes a medical AI paper’s title, abstract and metadata for AI search engines. Use when a paper should be findable and citable by RAG tools and AI search.
- 临床数据统计分析与建模Generates reproducible Python or R code for clinical statistics and tables. Use when collected data needs Table 1, regression, survival or agreement analysis.
- 作者发表记录与策略分析Analyzes a PubMed author record to classify study types and authorship patterns. Use when planning a publication strategy from a researcher’s track record.
- 批量队列暴露结局分析Generates one cohort-analysis script per exposure-outcome pair from one template. Use when a validated method must run across many variable combinations at once.
- 样本量估算与检验效能Walks a decision tree to the right test and computes sample size with IRB text. Use when planning how many patients a study needs before data collection.
- 因果推断方法设计Runs DAG-based, instrumental-variable, difference-in-differences or RD analyses. Use when an association in observational data must support a causal claim.
- 报告规范逐条核查Audits a manuscript item by item against 49 reporting and risk-of-bias checklists. Use when checking a draft against STROBE, CONSORT, TRIPOD or similar guidelines.
- 临床数据清洗与画像Profiles a clinical dataset and generates cleaning code in staged, approved steps. Use when a CSV or Excel dataset needs missing-value and outlier checks before analysis.
- 跨国队列数据协调对比Harmonizes variables and runs parallel weighted analyses across national surveys like KNHANES and NHANES. Use when comparing one exposure-outcome link across countries.
- 变量定义与截断值溯源Maps exposure, outcome and covariate definitions to a cited guideline and DB columns. Use when variable cutoffs need a citable basis before the study protocol.
- 本地化临床数据脱敏Runs a local, network-free script that detects and removes identifiers from clinical data. Use when data may contain PHI and must be de-identified before LLM analysis.
- AI对标专家基准研究设计Plans the arms, rubrics, calibration probes and reviewer panel for an AI-vs-expert benchmark. Use before data collection when designing an AI-vs-human rating study.
- 放射影像AI研究设计审查Reviews a study’s analysis unit, cohort logic, leakage risk and reporting-guideline fit. Use when checking a clinical or medical-AI study design before drafting.
- 传染病仓室模型拟合Builds and fits SIR, SEIR and SEIHR compartmental models with Rt estimation. Use when an outbreak or epidemic’s spread needs mathematical modeling in Python.
- ICMJE利益冲突声明填写Clones a pre-filled synthetic ICMJE COI form, replacing only date, name and title. Use when each author on a submission needs a disclosure form filled quickly.
- 机构Word表单内容填充Fills an institutional Word form, such as an IRB protocol, without breaking its layout. Use when drafted content must be rendered into a CJK-aware .docx template.
- 队列数据库选题挖掘Profiles a longitudinal cohort database and ranks research-topic proposals with gap evidence. Use when looking for a question an available cohort or registry can answer.
- 投稿期刊匹配推荐Matches a manuscript abstract against curated journal profiles and ranks candidates. Use when choosing where to submit, or re-targeting after a rejection.
- DOI全文批量获取Batch-downloads open-access PDFs for a list of DOIs via Unpaywall, PMC and OpenAlex. Use when full texts are needed for a screening set such as a meta-analysis.
- 数据集编码本自动生成Profiles every variable in a tabular dataset into a structured, citable codebook. Use when a CSV, Excel or Stata dataset needs a data dictionary before analysis.
- 全球卫生数据获取分析Accesses and analyzes global health data from WHO GHO, IHME GBD and Our World in Data. Use when DALYs, age-standardized rates or choropleth maps are needed.
- 医学AI项目基金申请书撰写Structures a grant proposal’s significance, innovation, approach, aims and milestones. Use when drafting a research funding proposal, including a Korean grant plan.
- 卫生经济学评价建模Builds Markov cohort models with QALYs, PSA and cost-effectiveness planes. Use when a health intervention needs a formal cost-effectiveness evaluation.
- AI写作痕迹识别改写Scans a manuscript for AI writing patterns and rewrites flagged passages carefully. Use when a draft or response letter reads as obviously AI-written.
常见问题
医学影像模型架构选型能做什么?
Picks a paper-grounded architecture family and vets a repo’s license and provenance. Use when choosing which model to use for a medical-imaging study。
如何安装医学影像模型架构选型?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「医学影像模型架构选型」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
医学影像模型架构选型需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
医学影像模型架构选型经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。