Radiology Method Evaluation logo

Radiology Method Evaluation

CommunityPopular
huang-sir1
radiology-method-evaluation

Audit parameter provenance, metric fit, fair comparisons and robustness; not execution or paper review.

Overview

Publisherhuang-sir1
Repositoryradiology-skills
Skill nameradiology-method-evaluation
Stars
2K
Forks
20
Bundled files
6
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.

  • 6 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 Method Evaluation 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.
    https://github.com/huang-sir1/radiology-skills/tree/main/radiology-skills/skills/radiology-method-evaluation
  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/skills/radiology-method-evaluation .claude/skills/radiology-method-evaluation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Radiology Method Evaluation 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 Method Evaluation 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 Method Evaluation 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.

Parameter and methodology evaluation

Use this skill to decide whether a parameter choice, evaluation metric, or analytical method is scientifically defensible and whether the available evaluation is sufficient for the stated claim. It is an independent entry point and a cross-cutting reviewer/mentor module, not a sub-skill of statistics, radiogenomics, writing, or prereview.

Core stance

  • Treat parameters/settings, evaluation metrics/readouts, and methodology as three separate objects. Do not hide one behind another.
  • Use exact evidence anchors. Report whether evidence is PLANNED, AUTHOR_REPORTED, PARTLY_VERIFIED, VERIFIED, or NOT_ASSESSABLE.
  • Return PASS, CONDITIONAL, or STOP per decision-bearing object and claim. Do not average a fatal defect into a composite quality score.
  • Be constructive: identify the criterion, minimum feasible repair, stronger option and its cost, closure evidence, and the claim that survives if the repair cannot be completed.
  • Review is read-only by default. Do not alter code, data, configurations, or manuscript files unless the user explicitly asks for implementation or editing.
  • Never invent a parameter range, run, result, effect, uncertainty interval, software version, benchmark, ablation, or validation.

Choose the entry mode

ModeUse whenRequired output emphasis
planthe evaluation has not been rundecision-bearing parameters, defensible alternatives/ranges, fair comparison design, controls, freeze point and analysis handoff
auditMethods, configurations, code, logs or result artifacts existprovenance, selection timing, leakage, metric fit, method assumptions, fairness, evidence gaps and atomic repairs
interpretreal evaluation results are supplieddirection/magnitude, uncertainty, stability/failure boundary, heterogeneity, claim consequence and residual limit
writing-packagethe science is fixed and must be placed in a paperexact Methods/Results/Figure/Supplement/Discussion jobs without implying unrun analyses

Also declare focus: parameters | evaluation-metrics | methodology | combined and the active scope/modalities. A request may enter with an incomplete manuscript or a single configuration file; do not require a prior pipeline task.

Minimal intake

Record what is available and mark the rest AUTHOR_INPUT_NEEDED:

  1. study question, estimand or intended use and affected Claim IDs;
  2. scope and modalities; cohort/specimen hierarchy and true independent unit;
  3. frozen method/model/pipeline version and data/split/test-access state;
  4. parameter values, defaults, candidate ranges/levels, units and rationale sources;
  5. when and on which data each setting, threshold, model or metric was selected;
  6. comparators, controls, ablations, evaluation metrics, tuning/compute budget and hardware;
  7. supplied results, uncertainty, run/seed structure, failures and exact artifact locations.

Required workflow

  1. Open the canonical assessment reference.
  2. Reconstruct the chain: question/estimand -> unit -> measurement -> preprocessing -> representation -> selection -> method/model -> metric -> validation -> claim.
  3. Build separate methodology-fit, parameter, metric/readout, and sensitivity/robustness tables.
  4. Activate only evaluations that can change a decision or claim. Do not demand every possible grid, ablation, or alternative method.
  5. For each finding, bind the exact evidence anchor, criterion, affected claim, minimum repair, optional stronger route/cost, closure evidence, and manuscript placement.
  6. If actual comparison outputs need statistical inference, hand off the paired predictions or estimates, independent unit, resampling hierarchy and multiplicity family to radiology-stats.
  7. Use the reusable assessment matrix when a durable artifact is useful.
  8. When the team wants to reuse institution- or platform-specific experience, open the local experience registry. Transfer only rows whose platform, specimen, data state, endpoint, unit and intended claim are compatible; preserve failed and null experience as well as successful settings.

Scientific red lines

  • Tuning selects a configuration; sensitivity analysis evaluates a locked conclusion. Do not present the tuning trace as independent robustness evidence.
  • The protected test set cannot select parameters, methods, thresholds, features, stopping rules, favourable seeds, figures or claims.
  • Fair method comparison holds cases, splits, preprocessing, endpoint, metric and—where relevant— tuning budget, pretraining information, implementation and hardware conditions comparable.
  • Folds, seeds, patches, slices, lesions, cells, spots, tiles and model runs are not new patients or donors. Preserve the actual sampling and resampling hierarchy.
  • If changing a setting changes the estimand, inclusion population, spatial scale, cell identity, biological object or decision threshold, treat it as a distinct analysis question—not a routine sensitivity check.
  • Perturbation dose, time, guide design/number, assignment and target-engagement criteria are experimental-design factors. Do not optimize them against the desired phenotype as if they were ordinary machine-learning hyperparameters.
  • An ablation supports the component's conditional contribution in the evaluated pipeline and data; it does not prove universal necessity, biological mechanism or causality.
  • Stability is not correctness. Simulation, generated molecular layers and synthetic perturbations are not external or biological validation.
  • A package default, popular paper or high-impact venue is not by itself a scientific rationale.

Domain routing

Use this skill as the evaluation owner; open the relevant internal domain reference only for the meaning, plausible alternatives and operational constraints of the active parameter or method.

DomainDomain execution/source ownerTypical decision-bearing evaluation
image formation/quantitationradiology-acquisition-qcseries/phase/sequence acceptance, DICOM quantitative transforms, acquisition/reconstruction, contrast/tracer timing, dose, artifacts, phantom/test-retest, site qualification and protocol drift
radiomics/imaging analysisradiology-radiomics, radiology-annotationresampling/interpolation, binning, segmentation perturbation, stability cutoff, harmonisation, feature selection and threshold freeze after the measurement passport
deep imagingradiology-deep-learninginput scale/patch, architecture/pretraining, augmentation, loss/optimizer/schedule, search budget, seeds, checkpointing, ablation, OOD and efficiency
bulk RNAexecution: radiology-transcriptomics-analysis; meaning: radiology-radiogenomics bulk playbookfiltering, normalization, design/contrast, batch/composition, model family, FDR/effect thresholds, gene-set universe
sc/snRNAexecution: radiology-transcriptomics-analysis; meaning: radiology-radiogenomics single-cell playbookQC, ambient/doublet handling, normalization/HVG, integration, PCs/kNN/resolution, annotation, pseudobulk unit, trajectory root
spatialexecution: radiology-transcriptomics-analysis; meaning: radiology-radiogenomics spatial playbooksegmentation, coordinate error, deconvolution, smoothing, domain resolution/seed, radius/kernel/k, spatial null and patient aggregation
pathologyradiology-radiogenomics pathology playbookstain/scoring, magnification/tile, colour normalization, segmentation, phenotype cutoff, ROI sampling and patient aggregation
multi-omicsradiology-radiogenomics integration playbooksmatched intersection, missing-modality policy, scaling, factor/latent dimension, modality weights, alignment objective, unimodal ablation
perturbationdesign/audit source: radiology-experiment-design; mechanism meaning: radiology-radiogenomics perturbation playbookassignment, efficiency, off-target, dose-time, target engagement, toxicity, control/rescue and multiplicity
imaging-mechanismradiology-radiogenomics bridge playbookall active modality settings plus patient-lesion-region-block-section-cell/time mapping, bridge sensitivity and discordance

Output contract

Return the shortest complete set needed for the request, in this order:

  1. Evaluation scope and claim — mode, focus, scope, active modalities, independent unit, materials and evidence boundary.
  2. Methodology-fit matrix — question/estimand, data layer/unit, assumptions, comparator/control, validation and verdict.
  3. Parameter ledger — role, value/range/unit, rationale, selection data/timing, search budget, freeze state, sensitivity, provenance and claim consequence.
  4. Evaluation-metric/readout matrix — task fit, aggregation, threshold/prevalence dependence, uncertainty, tuning-objective overlap and blind spot.
  5. Benchmark/ablation/control matrix and Sensitivity/robustness results or plan — matched conditions, execution state, failure boundary and negative results.
  6. Strengths and atomic findings — evidence anchor, criterion, severity, minimum repair, stronger option/cost and closure evidence.
  7. Statistical handoff — only the comparisons requiring estimation, intervals, tests or multiplicity control.
  8. Writing placement — Methods, Results, Figure/Table, Supplement/config/code, Discussion and Abstract/title constraints.
  9. Claim verdict and next action — PASS / CONDITIONAL / STOP, surviving claim ceiling, the single next decision-bearing action and AUTHOR_INPUT_NEEDED fields.

Handoffs and non-ownership

  • Configure or run a radiomics/DL pipeline → its imaging execution skill; configure, run, audit or reproduce bulk/sc/snRNA/spatial workflows → radiology-transcriptomics-analysis.
  • Design functional IHC/mIF, tissue, cell, organoid, animal, perturbation, target-engagement or rescue evidence → radiology-experiment-design; this skill may later audit its method choices.
  • Estimate paired differences, CIs, cluster bootstrap, run variability or multiplicity → radiology-stats after this skill defines the comparison and hierarchy.
  • Audit all dimensions of a full manuscript → radiology-prereview; it consumes these findings without replacing the criterion or closure evidence.
  • Draft prose from fixed evidence → radiology-writing; sentence-level polish → radiology-polishing.
  • Turn reviewer comments into a response/verification ledger → radiology-response.
  • Audit journal upload files and format rules → radiology-submission.

Do not silently broaden a focused parameter/method question into a full manuscript review or an unrequested execution project.

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

Audit parameter provenance, metric fit, fair comparisons and robustness; not execution or paper review.

Why use Radiology Method Evaluation on TypingMind?

Because you install it once and use it with any model. Radiology Method Evaluation 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 Method Evaluation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/huang-sir1/radiology-skills/tree/main/radiology-skills/skills/radiology-method-evaluation. 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 Method Evaluation?

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 Method Evaluation?

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

Is the Radiology Method Evaluation AI skill free?

It is published on GitHub by huang-sir1. Check the repository for licensing terms. 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 👇