Radiology Table logo

Radiology Table

CommunityPopular
huang-sir1
radiology-table

Create/audit editable publication tables with source reconciliation; not figures or statistical inference.

Overview

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

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

Use it in TypingMind

Enable Radiology Table 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 Table 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 Table 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 Publication Tables

Build tables as scientific evidence, not decorative summaries. Each table should answer one question, expose the correct denominator and uncertainty, and remain traceable to analysis output.

Core stance

  • Shell before formatting. Define the population, row variables, column groups, estimand, precision, and footnotes before filling cells.
  • One canonical value. Reconcile values to source output or the radiology-pipeline reported_values.csv; do not retype numbers from prose.
  • Denominators stay visible. State cohort n, events, missingness, and subgroup denominators.
  • Reference levels are explicit. Regression and subgroup tables name reference categories.
  • Estimate plus uncertainty. Report effect estimate with 95% CI; use exact p values under the target venue's policy.
  • Editable and inspectable. Prefer DOCX/XLSX/LaTeX for editing plus CSV/source data for audit.
  • No false polish. A visually clean table with inconsistent counts or unsupported precision fails.

When to open extra files

FileOpen when
references/table-archetypes.mdChoosing Table 1, performance, regression, feature, reader, radiogenomics, ablation, or supplement structure
references/survival-and-model-tables.mdCox/KM/prognostic, logistic, nomogram, time-dependent metrics, calibration, DCA, or feature-weight tables
references/table-style-and-qa.mdApplying target-journal style, fitting wide/long tables, footnotes, pagination, export, and final visual QA

Workflow

Choose advisory, audit or create-edit from the request. Advisory work returns an inline plan; audit checks existing tables and reports supported findings without rewriting them. Steps 5–7 apply to authorized creation/editing; do not export a replacement merely because a table was reviewed.

  1. Classify the table. Identify its scientific question, target venue, main/supplement role, population, cohort(s), endpoint, timepoint, and source artifact.
  2. Write the table contract. Use the asset assets/table-spec.template.csv for a table set, or state: This table should let the reader compare/estimate [question] in [population] using [estimand], with [uncertainty and boundary].
  3. Choose the archetype from table-archetypes.md; define row order and columns before values.
  4. Reconcile inputs. Check cohort flow, source-data file, statistical output, and canonical value keys. Mark missing/contradictory values; never infer them.
  5. Populate with one display policy. Use consistent decimals, units, CI notation, p-value style, missing-data display, and reference labels. Keep exact source values in machine-readable output.
  6. Write title and footnotes. Define population, abbreviations, tests, summary statistics, reference categories, multiplicity adjustment, missingness, and simulation status.
  7. Export. For actual DOCX/XLSX/LaTeX artifacts, load the relevant document or spreadsheet skill/tool. Also preserve a CSV/source-data version when feasible.
  8. Audit. Open table-style-and-qa.md; render or preview the final editable table, inspect page width and breaks, and cross-check values against figures and manuscript text.

Output contract

Return the applicable subset: a bounded question needs its answer; audit needs findings, evidence locations and the checks actually performed. Completed files and export QA apply only when files were requested and produced. Missing analysis output does not block review of visible structure.

  1. Table plan - table ID, question, cohort, estimand, source, main/supplement role.
  2. Table shell - ordered rows, columns, group headings, reference levels, and footnote plan.
  3. Completed table - only supplied/computed values; placeholders remain explicit.
  4. Editable files - DOCX/XLSX/LaTeX as requested, plus CSV/source data where feasible.
  5. Value crosswalk - cell/row to value key and source location for primary results.
  6. QA report - denominator, CI/p-value, reference, missingness, abbreviation, width, pagination, simulation, and cross-artifact checks.
  7. Author input needed - unresolved facts or outputs only the author/analyst can supply.

Handoffs

  • Statistical method and computed results -> radiology-stats.
  • Radiomics feature selection/coefficient provenance -> radiology-radiomics.
  • Deep-learning performance/ablation/fairness outputs -> radiology-deep-learning.
  • Imaging-omics associations/pathways/cell composition -> radiology-radiogenomics.
  • Figure-table value reconciliation -> radiology-figure / radiology-pipeline.
  • Reuse or simplify a frozen table for a scientific presentation -> radiology-paper2ppt with canonical value keys, denominator/uncertainty context and editable source.
  • Table callouts and legends in manuscript prose -> radiology-writing / radiology-polishing.
  • Reporting checklist and final package -> radiology-reporting / radiology-submission.

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

Create/audit editable publication tables with source reconciliation; not figures or statistical inference.

Why use Radiology Table on TypingMind?

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

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

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

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