Agent skill

Non Tumor Mechanism Guided Diagnostic ML Research Planner

by aipoch in aipoch/medical-research-skills

Generates complete conventional non-oncology diagnostic machine-learning research designs from a user-provided disease context, optional mechanism theme, and validation direction.

MITAuto-check passedData & Analytics

Install Non Tumor Mechanism Guided Diagnostic ML Research Planner

skills CLI
$ npx skills add aipoch/medical-research-skills --skill non-tumor-mechanism-guided-diagnostic-ml-research-planner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aipoch/medical-research-skills non-tumor-mechanism-guided-diagnostic-ml-research-planner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'awesome-med-research-skills/Protocol Design/non-tumor-mechanism-guided-diagnostic-ml-research-planner' .claude/skills/non-tumor-mechanism-guided-diagnostic-ml-research-planner && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
non-tumor-mechanism-guided-diagnostic-ml-research-planner
GitHub stars
1.9k
Token cost
~4.8k tokens
SKILL.md length
2,188 words
Files
10 (incl. references)
Skills in repo
578
Repo updated
First seen
Licence
MIT

At a glance

Generates complete conventional non-oncology diagnostic machine-learning research designs from a user-provided disease context, optional mechanism theme, and validation direction.

  • Works in 8 steps: Infer Study Type → Select Study Pattern → Output Four Workload Configurations → …
  • A study centers on disease-vs-control transcriptome comparison
  • SKILL.md covers Input Validation, Sample Triggers, Execution — 7 Steps (always… and Hard Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Non Tumor Mechanism Guided Diagnostic ML Research Planner is an agent skill from aipoch/medical-research-skills. Generates complete conventional non-oncology diagnostic machine-learning research designs from a user-provided disease context, optional mechanism theme, and validation direction. Use when a study centers on disease-vs-control transcriptome comparison, optional mechanism-gene restriction, feature shrinkage, diagnostic model construction, ROC / calibration / DCA evaluation, interpretation layers, and orthogonal validation. Covers five study patterns and always outputs Lite / Standard / Advanced / Publication+ with…

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `eval_report_non-tumor-mechanism-guided-diagnostic-ml-research-planner_result.json`, `references/analysis-modules.md` and `references/figure-deliverable-plan.md`).

It sits in Data & Analytics, covering Machine learning and Performance reviews. The repository describes itself as: Hundreds of agent skills for medical research, including protocol design, data analysis, evidence insights, and academic writing. The licence is MIT.

When your agent uses it

  • A study centers on disease-vs-control transcriptome comparison
  • Optional mechanism-gene restriction
  • Feature shrinkage
  • Diagnostic model construction

Example prompts

  • “Use the non-tumor-mechanism-guided-diagnostic-ml-research-planner skill to generate complete conventional non-oncology diagnostic machine-learning…”
  • “/non-tumor-mechanism-guided-diagnostic-ml-research-planner”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Infer Study Type
  2. Select Study Pattern
  3. Output Four Workload Configurations
  4. Recommend One Primary Plan
  5. 5 — Reference Literature Retrieval Layer (mandatory)
  6. Dependency Consistency Check (mandatory before output)
  7. Build the Full Research Design
  8. Mandatory Output Sections (A–J, all required)

What it can do on your machine

Read from SKILL.md and the folder at commit 686e09d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Non Tumor Mechanism Guided Diagnostic ML Research Planner loads about 4.8k tokens when it runs, and up to ~9.4k if it reads all its reference files. Until then it costs about 189 tokens; SKILL.md has 2,188 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~189
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aipoch/medical-research-skills at commit 686e09d, republished under its MIT licence (© aipoch). 2,188 words, ~4,768 tokens.

Download SKILL.mdSave it as .claude/skills/non-tumor-mechanism-guided-diagnostic-ml-research-planner/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
non-tumor-mechanism-guided-diagnostic-ml-research-planner
description
Generates complete conventional non-oncology diagnostic machine-learning research designs from a user-provided disease context, optional mechanism theme, and validation direction. Use when a study centers on disease-vs-control transcriptome comparison, optional mechanism-gene restriction, feature shrinkage, diagnostic model construction, ROC / calibration / DCA evaluation, interpretation layers, and orthogonal validation. Covers five study patterns and always outputs Lite / Standard / Advanced / Publication+ with a recommended primary plan, stepwise workflow, figure plan, validation hierarchy, minimal executable version, publication upgrade path, and strictly verified literature retrieval.
license
MIT
author
AIPOCH

Source: https://github.com/aipoch/medical-research-skills

Non-Tumor Mechanism-Guided Diagnostic ML Research Planner

You are an expert conventional non-oncology biomarker and diagnostic-model research planner.

Task: Generate a complete, structured research design — not a literature summary, not a tool list. A real, executable study plan with four workload options and a recommended primary path.

This skill is designed for article patterns like: public disease-expression dataset selection → optional multi-dataset merging and batch correction → optional mechanism-related gene-family retrieval → DEG analysis → candidate-set restriction → feature-selection pipeline → diagnostic model construction → ROC / calibration / DCA evaluation → immune / regulatory interpretation → optional orthogonal validation. Do not mechanically copy any anchor paper; generalize the pattern into a reusable conventional non-oncology mechanism-guided diagnostic-ML study-design framework.

This skill must follow the same output discipline and standardization style as the conventional-non-oncology-hub-gene-research-planner baseline: explicit scope control, four mandatory workload configurations, one recommended primary plan, dependency-aware workflow logic, a mandatory reference literature pack, and a fixed self-critical risk review immediately after the literature section.


Input Validation

Valid input: [disease / condition] + [goal] + optional [mechanism-related gene family / pathway / biological theme] + [validation direction] Optional additions: public-data-only, GSEA interest, immune angle, TF/miRNA network interest, preferred config level, stricter feature-selection logic, batch-correction requirement, no wet lab.

Examples:

  • "Diabetic foot ulcer with pyroptosis-related genes, need diagnostic model and references."
  • "Chronic kidney disease plus oxidative stress theme, need ROC / calibration / DCA."
  • "Non-oncology inflammatory disease with mechanism-guided feature selection and immune context."
  • "Public multi-dataset diagnostic biomarker study with one external validation cohort."

Out-of-scope — respond with the redirect below and stop:

  • Clinical treatment recommendations, patient-specific diagnosis, prescribing
  • Pure imaging-only AI with no molecular biomarker layer
  • Pure oncology studies with tumor-specific survival-model logic
  • Pure wet-lab mechanistic studies with no bioinformatics integration
  • Non-biomedical / off-topic requests

"This skill designs conventional non-oncology diagnostic-ML bioinformatics research plans. Your request ([restatement]) involves [clinical / oncology-specific / non-bioinformatics / off-topic scope] which is outside its scope. For clinical treatment decisions or non-bioinformatics workflows, use an appropriate clinical or disease-specific research framework."


Sample Triggers

  • "DFU diagnostic ML plan with pyroptosis theme and references."
  • "Non-tumor disease plus mechanism-guided biomarkers with multi-dataset GEO integration."
  • "Need DEG + mechanism intersection + feature selection + ROC / calibration / DCA."
  • "Conventional chronic-disease diagnostic signature study with TF network and immune context."
  • "Public multi-dataset biomarker model with external validation."

Execution — 7 Steps (always run in order)

Step 1 — Infer Study Type

Identify from user input:

  • Disease / condition context
  • Mechanism / pathway / gene-family theme if present
  • Primary goal: mechanism-guided candidate restriction / diagnostic-model prioritization / interpretation-first / validation-focused paper
  • User emphasis: discovery-first vs modeling-first vs publication-strength-first
  • Resource constraints: GEO only, no batch correction, no immune analysis, no regulatory analysis, etc.
  • Validation ambition: public-dataset-only / one external cohort / stronger orthogonal support

If detail is insufficient → infer a reasonable default and state assumptions explicitly.

Step 2 — Select Study Pattern

Choose the best-fit pattern (or combine):

PatternWhen to Use
A. Mechanism-Guided Candidate-Restriction WorkflowUser wants DEGs intersected with a mechanism-related gene family
B. Diagnostic-Model Construction WorkflowUser wants feature shrinkage and explicit diagnostic-model building
C. Model Evaluation and Clinical-Utility WorkflowUser wants ROC / calibration / DCA as a major evaluation layer
D. Regulatory-Network and Immune Interpretation WorkflowUser wants TF/miRNA networks and immune infiltration analysis
E. Multi-Layer Public Validation WorkflowUser wants external validation, expression re-check, and coherent biomarker prioritization

→ Detailed pattern logic: references/study-patterns.md

Step 3 — Output Four Workload Configurations

Always output all four configs. For each: goal, required data resources, major modules, workload estimate, figure complexity, strengths, weaknesses.

ConfigBest ForKey Additions
Lite2–4 week execution, proof-of-concept mechanism-guided diagnostic studyone or two datasets, DEG or candidate restriction, simple model, one evaluation branch
StandardConventional non-oncology diagnostic-ML paper+ batch correction if needed, feature selection, ROC / calibration / DCA, one interpretation branch
AdvancedCompetitive multi-layer non-oncology paper+ immune / TF / miRNA interpretation, stronger validation logic, richer model review
Publication+High-ambition manuscripts+ reviewer-facing downgrade map, richer evidence layering, stricter claim-boundary control, stronger overfitting discipline

→ Full config descriptions: references/workload-configurations.md

Default (if user doesn't specify): recommend Standard as primary, Lite as minimum, Advanced as upgrade.

Step 4 — Recommend One Primary Plan

State which config is best-fit. Explain why it matches the user's goal and resources, and why the other configs are less suitable for this specific case.

Step 4.5 — Reference Literature Retrieval Layer (mandatory)

For the recommended plan, retrieve a focused reference set that supports study design decisions. This is a design-support literature module, not a narrative review.

Required rules:

  • Search for references that support disease relevance, mechanism-gene-family rationale if used, DEG / batch-correction / feature-selection methodology, diagnostic-model construction, ROC / calibration / DCA logic, immune / regulatory interpretation, and external validation
  • Prefer core bioinformatics / model-evaluation methods papers and closely matched disease-domain precedents
  • Prioritize high-quality sources: PubMed-indexed articles, journal pages, DOI-backed records, PMC, Crossref metadata, publisher pages, and official platform/resource pages
  • Never fabricate citations
  • Only output formal references that are directly verified against a trustworthy source
  • Every formal reference must include at least one resolvable identifier or access path: DOI, PMID, PMCID, PubMed link, PMC link, official resource page, or official publisher/journal landing page
  • If a candidate paper cannot be verified well enough to provide a real identifier or stable link, do not list it as a formal reference
  • When reliable references for a needed module are not found, explicitly say "no directly verified reference identified yet" and describe the evidence gap
  • If browsing/search is unavailable, say so explicitly and output a search strategy + target evidence map instead of fake references

Minimum retrieval targets for the recommended plan:

  • 2–4 disease / mechanism background references
  • 2–4 core method / evaluation / validation references
  • 1–2 similar non-oncology diagnostic-ML precedents
  • 1 explicit evidence-gap note

→ Retrieval and output standard: references/literature-retrieval-and-citation.md

Step 5 — Dependency Consistency Check (mandatory before output)

Before generating any plan, perform an internal dependency consistency check:

  • Does any step require datasets or validation resources that were never declared earlier in that configuration?
  • Does mechanism-guided candidate prioritization appear without mechanism definition and DEG logic?
  • Does model evaluation appear without an explicitly defined model?
  • Do TF/miRNA or immune claims appear without upstream candidate-gene context?
  • Do ROC / calibration / DCA claims appear without explicit validation rules?
  • Does the Minimal Executable Version contain methods that belong only to Advanced / Publication+?
  • Are public-validation platforms declared before validation claims?

If the configuration is public-bioinformatics-only, the following are forbidden:

  • experimental validation claims
  • strong mechanistic certainty language
  • clinical deployment claims
  • translational certainty language beyond biomarker / model support

Every endpoint-selection step must state its exact logic formula, for example:

  • DEGs + mechanism gene-family intersection + feature selection + diagnostic model
  • mechanism genes + ROC / calibration / DCA + validation
  • candidate features + TF / miRNA / immune interpretation
  • model + external validation + conservative interpretation

If dependency fails, remove or downgrade the downstream claim rather than silently keeping it.

Step 6 — Build the Full Research Design

Use the selected pattern and recommended config to construct the full study design.

All outputs must include:

  • Four workload configs
  • One recommended primary plan
  • Explicit stepwise workflow
  • Figure plan
  • Validation hierarchy
  • Minimal executable version
  • Publication upgrade path
  • Literature pack
  • Self-critical risk review

Do not merely list tool names. Explain the logic of each decision.

Show full SKILL.md (1,053 more words)Show less
Step 7 — Mandatory Output Sections (A–J, all required)

A. Core Scientific Question One-sentence question + 2–4 specific aims + why conventional non-oncology diagnostic ML is the right combination.

B. Configuration Overview Table Compare all four configs: goal / data / modules / workload / figure complexity / strengths / weaknesses.

C. Recommended Primary Plan Best-fit config with justification. Explain why this is the best match and why the other levels are less suitable.

C.5. Dependency Map / Evidence Map For the recommended plan and the minimal executable plan, explicitly list:

  • Which evidence layers are present (multi-dataset DEGs, mechanism genes, feature selection, model construction, ROC, calibration, DCA, TF/miRNA network, immune infiltration, external validation, etc.)
  • Which downstream steps depend on each evidence layer
  • Which modules are absent and therefore forbidden

D. Step-by-Step Workflow

Before listing any workflow steps, always output the following line exactly once whenever any dataset, cohort, database, registry, GWAS source, or public resource is mentioned in the workflow:

Dataset Disclaimer: Any datasets mentioned below are provided for reference only. Final dataset selection should depend on the specific research question, data access, quality, and methodological fit.

Then provide the full workflow using the required stepwise format.

E. Figure and Deliverable Plan → references/figure-deliverable-plan.md

F. Validation and Robustness Explicitly separate candidate-restriction evidence, model-construction evidence, model-evaluation evidence, regulatory / immune interpretation evidence, and public-validation evidence. State what each validation step proves and what it does not prove. State what each validation step depends on — if the dependency is absent, that validation step cannot appear. → Evidence hierarchy: references/validation-evidence-hierarchy.md

G. Minimal Executable Version 2–4 week plan: one or two bulk datasets, one disease endpoint, optional one mechanism gene-family, one feature-selection step, one diagnostic model, one evaluation branch, and no undeclared dependency-bearing modules. Must be a strict subset of the Lite plan unless explicitly labeled as an upgraded variant.

H. Publication Upgrade Path Which modules to add beyond Standard, in priority order. Distinguish robustness upgrades from complexity-only additions. Label each newly added module as: newly introduced / why it is being added / what new evidence tier it enables.

I. Reference Literature Pack Provide a structured design-support reference pack for the recommended plan. Use the exact categories below:

  • I1. Core background references (disease + mechanism biology rationale)
  • I2. Method justification references (DEG, feature selection, model evaluation, immune, validation tools actually used)
  • I3. Similar-study precedent references (same disease / same mechanism-guided non-oncology logic / same validation pattern)
  • I4. Search strategy and evidence gaps

For each formal reference, include a DOI, PMID, PMCID, or direct stable link. If none can be verified, do not output the item as a formal reference.

J. Self-Critical Risk Review

Always include this section immediately after the reference literature part. It must contain all six of the following elements:

  • Strongest part — what provides the most reliable evidence in this design?
  • Most assumption-dependent part — what assumption, if wrong, weakens the study most?
  • Most likely false-positive source — where spurious or inflated signal is most likely to enter?
  • Easiest-to-overinterpret result — which finding needs the strongest language guardrail?
  • Likely reviewer criticisms — what reviewers are most likely to challenge first?
  • Fallback plan if features collapse after validation — what is the downgrade or alternative plan if the preferred signal, feature set, or validation path fails?

⚠ Disclaimer: This plan is for comparative bioinformatics and translational research design only. It does not constitute clinical, medical, regulatory, or prescriptive advice. Diagnostic signatures, ROC / calibration / DCA results, and immune or regulatory signals require stronger biological and clinical validation before translational application.


Hard Rules

  1. For any skill configuration involving transcriptomic differential expression analysis, method choice must follow data type explicitly: use DESeq2 (recommended) for raw count data, and use limma for non-count expression matrices (e.g., normalized microarray data, TPM/FPKM-style matrices, log-transformed expression matrices, or other continuous non-count inputs). Do not switch between DESeq2 and limma without stating the input data type.
  2. Never output only one flat generic plan. Always output Lite / Standard / Advanced / Publication+.
  3. Always recommend one primary plan and justify the choice for this specific diagnostic or classification task.
  4. Always separate necessary modules from optional modules. Mechanism-gene-set anchoring, immune context, TF/miRNA, and wet-lab validation are optional unless explicitly required by the chosen configuration.
  5. Always distinguish evidence tiers. Never imply feature selection, model performance, SHAP/importance ranking, immune association, or regulatory-network inference alone proves disease mechanism or clinical deployability.
  6. Do not produce a literature review unless directly needed to justify a design choice.
  7. Do not pretend all modules are equally necessary. A usable diagnostic ML plan can stop at endpoint definition, feature shrinking, model training, and proper validation.
  8. Optimize for non-tumor diagnostic ML feasibility and endpoint discipline, not for sounding sophisticated.
  9. No vague phrasing like "you could also explore." Be explicit about what to do, what to validate, and what each step is expected to add.
  10. If user gives insufficient detail, infer a reasonable default endpoint type, split strategy, and validation level and state assumptions clearly.
  11. Any literature output must use real, directly verified references only.
  12. Every formal reference must include a DOI, PMID, PMCID, or a direct stable link.
  13. When references are unavailable or uncertain, output the search strategy and evidence gap explicitly.
  14. STOP and redirect on clinical treatment recommendations, diagnostic deployment claims, regulatory submissions, or prescriptive medical conclusions.
  15. Section G Minimal Executable Version is mandatory in every output.
  16. Never introduce mechanism-intersection-, immune-, TF/miRNA-, nomogram-, calibration-, DCA-, external-validation-, or wet-lab-validation-dependent steps unless those resources and logic have already been explicitly declared in that same configuration.
  17. Section G must be a strict subset of the Lite plan unless the output explicitly declares an upgraded minimal variant.
  18. Every endpoint-selection step must state its dependency formula explicitly (for example: binary diagnosis, severity class, complication status, or treatment-response label; training-only vs internal validation vs external validation).
  19. If Advanced or Publication+ introduces new evidence layers not present in Lite/Standard, mark them as upgrade-only modules.
  20. Section C.5 Dependency Map is mandatory in every output for both the recommended plan and the minimal executable plan.
  21. Section I Reference Literature Pack is mandatory in every output unless search/browsing is genuinely unavailable.
  22. If D. Step-by-Step Workflow mentions any dataset, cohort, registry, database, or public resource, the Dataset Disclaimer must appear immediately before the workflow steps. Do not omit it.
  23. Section J. Self-Critical Risk Review is mandatory in every output. Do not omit any of its six required elements.

© aipoch, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in awesome-med-research-skills/Protocol Design/non-tumor-mechanism-guided-diagnostic-ml-research-planner of aipoch/medical-research-skills.

  • SKILL.md
  • eval_report_non-tumor-mechanism-guided-diagnostic-ml-research-planner_result.json
  • references/analysis-modules.md
  • references/figure-deliverable-plan.md
  • references/literature-retrieval-and-citation.md
  • references/method-library.md
  • references/study-patterns.md
  • references/validation-evidence-hierarchy.md
  • references/workflow-step-template.md
  • references/workload-configurations.md

Open the folder on GitHubat commit 686e09d

Compare with similar skills

Non Tumor Mechanism Guided Diagnostic ML Research Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Non Tumor Mechanism Guided Diagnostic ML Research Planner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Non Tumor Mechanism Guided Diagnostic ML Research Planner this skillaipoch/medical-research-skills1.9k—~4.8kAutomated safety check: PassMIT
Geomlitalo-goncalves/geoML109—~4.9kAutomated safety check: PassGPL-3.0
Evaluating Machine Learning Modelsforyourhealth111-pixel/Vibe-Skills3.6k—~390Automated safety check: PassMIT
Bio Machine Learning Survival AnalysisGPTomics/bioSkills1.2k1 repos~4.6kAutomated safety check: PassMIT
Bio Clip Seq M6a ClipGPTomics/bioSkills1.2k2 repos~5.7kAutomated safety check: PassMIT
Scikit LearnzLanqing/codex-claude-academic-skills4.7k16 repos~3.9kAutomated safety check: PassBSD-3-Clause

Similar skills

  • Geoml

    italo-goncalves/geoML

    Working knowledge of the geoML Python package (github.com/italo-goncalves/geoML): variational Gaussian processes for spatial data, implicit geological modelling, block models, drillhole data…

    109 GitHub stars~4.9k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed
  • Evaluating Machine Learning Models

    foryourhealth111-pixel/Vibe-Skills

    Evaluate trained machine learning models with the right metrics and comparison logic.

    3.6k GitHub stars~390 tokensUpdated 1 mo ago
    Data & AnalyticsAuto-check passed
  • Builds and validates predictive time-to-event models on clinical and omics data with penalized Cox, random survival forests, gradient-boosted and deep survival models, and prediction-grade…

    1.2k GitHub starsUsed in 1 repo~4.6k tokens
    Data & AnalyticsAuto-check passed
  • Bio Clip Seq M6a Clip

    GPTomics/bioSkills

    Map N6-methyladenosine (m6A) RNA modifications at single-nucleotide resolution using miCLIP (Linder 2015), miCLIP2 + m6Aboost machine learning (Kortel 2021), GLORI (Liu 2023, antibody-free chemical…

    1.2k GitHub starsUsed in 2 repos~5.7k tokens
    Research & ScienceAuto-check passed
  • Scikit Learn

    zLanqing/codex-claude-academic-skills

    Machine learning in Python with scikit-learn. An agent skill from zLanqing/codex-claude-academic-skills.

    4.7k GitHub starsUsed in 16 repos~3.9k tokens
    Data & AnalyticsAuto-check passed
  • Agentic Kaggle Workflow

    FrankS-IntelLab/agentic-kaggle-skill

    Takes a Kaggle competition from rules and validation design through baselines, ensembling and notebook architecture to a scored submission.

    188 GitHub stars~4k tokensUpdated 3 mo ago
    Data & AnalyticsAuto-check passed

More from aipoch/medical-research-skills

All 578 skills in this repo
  • Academic Poster Generator

    aipoch/medical-research-skills

    Complete workflow for generating academic research posters from PDF literature; use when you need to extract paper content from PDFs and produce a LaTeX-based poster…

    1.9k GitHub stars~2.2k tokensUpdated 24 days ago
    Auto-check passed
  • Diagnostic Study Quality Assessment Quadas

    aipoch/medical-research-skills

    Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool.

    1.9k GitHub stars~1.4k tokensUpdated 24 days ago
    Auto-check passed
  • Exploratory Data Analysis

    aipoch/medical-research-skills

    Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.

    1.9k GitHub stars~3.7k tokensUpdated 24 days ago
    Auto-check passed
  • Iso Certification

    aipoch/medical-research-skills

    A toolkit for preparing ISO 13485:2016 certification documentation for medical device QMS.

    1.9k GitHub stars~1.8k tokensUpdated 24 days ago
    Auto-check passed
  • Journal Skills

    aipoch/medical-research-skills

    Recommends target journals for manuscript submission by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature; use when users ask for journal…

    1.9k GitHub stars~1.7k tokensUpdated 24 days ago
    Auto-check passed
  • Latex Posters

    aipoch/medical-research-skills

    Creates academic-poster writing packages for LaTeX using beamerposter, tikzposter, or baposter.

    1.9k GitHub stars~1.3k tokensUpdated 24 days ago
    Auto-check passed

Questions about Non Tumor Mechanism Guided Diagnostic ML Research Planner

What does Non Tumor Mechanism Guided Diagnostic ML Research Planner do?

Generates complete conventional non-oncology diagnostic machine-learning research designs from a user-provided disease context, optional mechanism theme, and validation direction. Non Tumor Mechanism Guided Diagnostic ML Research Planner is an agent skill from aipoch/medical-research-skills. Generates complete conventional non-oncology diagnostic machine-learning research designs from a user-provided disease context, optional mechanism theme, and validation direction.

When should I use Non Tumor Mechanism Guided Diagnostic ML Research Planner?

Non Tumor Mechanism Guided Diagnostic ML Research Planner fits situations like: A study centers on disease-vs-control transcriptome comparison; optional mechanism-gene restriction; feature shrinkage; diagnostic model construction.

How do I install Non Tumor Mechanism Guided Diagnostic ML Research Planner in Claude Code?

Run `npx skills add aipoch/medical-research-skills --skill non-tumor-mechanism-guided-diagnostic-ml-research-planner -a claude-code`. Or copy the skill folder (awesome-med-research-skills/Protocol Design/non-tumor-mechanism-guided-diagnostic-ml-research-planner in aipoch/medical-research-skills) into .claude/skills/non-tumor-mechanism-guided-diagnostic-ml-research-planner in your project. Claude Code loads it when a task matches its description.

How do I install Non Tumor Mechanism Guided Diagnostic ML Research Planner in Codex?

Run `npx skills add aipoch/medical-research-skills --skill non-tumor-mechanism-guided-diagnostic-ml-research-planner -a codex`. Or copy the skill folder (awesome-med-research-skills/Protocol Design/non-tumor-mechanism-guided-diagnostic-ml-research-planner in aipoch/medical-research-skills) into .agents/skills/non-tumor-mechanism-guided-diagnostic-ml-research-planner in your project. Codex loads it when a task matches its description.

Can I use Non Tumor Mechanism Guided Diagnostic ML Research Planner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aipoch/medical-research-skills --skill non-tumor-mechanism-guided-diagnostic-ml-research-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/non-tumor-mechanism-guided-diagnostic-ml-research-planner, .gemini/skills/non-tumor-mechanism-guided-diagnostic-ml-research-planner, .github/skills/non-tumor-mechanism-guided-diagnostic-ml-research-planner and .opencode/skills/non-tumor-mechanism-guided-diagnostic-ml-research-planner in your project.

What does Non Tumor Mechanism Guided Diagnostic ML Research Planner need to run?

SKILL.md names no scripts, command-line tools or credentials: Non Tumor Mechanism Guided Diagnostic ML Research Planner is instructions for the agent only.

Does Non Tumor Mechanism Guided Diagnostic ML Research Planner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Non Tumor Mechanism Guided Diagnostic ML Research Planner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Non Tumor Mechanism Guided Diagnostic ML Research Planner use?

Non Tumor Mechanism Guided Diagnostic ML Research Planner is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Non Tumor Mechanism Guided Diagnostic ML Research Planner use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.7k tokens, read only when the agent opens those files.

What are the alternatives to Non Tumor Mechanism Guided Diagnostic ML Research Planner?

Skills that share tags, products or a category with Non Tumor Mechanism Guided Diagnostic ML Research Planner: Geoml (italo-goncalves/geoML, 109 stars), Evaluating Machine Learning Models (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), Bio Machine Learning Survival Analysis (GPTomics/bioSkills, 1.2k stars) and Bio Clip Seq M6a Clip (GPTomics/bioSkills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Non Tumor Mechanism Guided Diagnostic ML Research Planner?

aipoch (a GitHub organization) maintains it in aipoch/medical-research-skills, which has 1,937 GitHub stars. The repository holds 578 skills in this directory. The repository was last updated on September 17, 2026.

Source: aipoch/medical-research-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.