Medical Master Router

Problem

Medical questions often span diagnosis, guidelines, drug safety, genomics, imaging, and report interpretation. If an agent gives a generic answer immediately, it may miss entity normalization and specialized downstream skills, making the response less reliable.

How It Works

Medical Master Router routes requests to narrower medical skills before producing a general answer. It follows several key steps:

• Intent classification: detect the user’s real goal and map it to domains such as clinical care, medication safety, precision oncology, single-cell analysis, CRISPR, and imaging pathology.
• Entity normalization: standardize disease names, generic drug names, gene symbols, cancer stage/histology, and data formats such as FASTQ, VCF, h5ad, and DICOM before retrieval.
• Precise routing: prefer the most specific primary and companion skills; use composite routing for multi-domain questions; fall back to bio-*, clinical-*, or tooluniverse-* families when no exact match is obvious.
• Report-first handling: for lab reports, checkup reports, or imaging reports, first detect the report type, then extract OCR/content, key findings, abnormal items, and missing context before interpretation.

Boundaries

The skill is intended for informational and decision-support purposes, not as a doctor or a substitute for professional care. It should distinguish general medical information from patient-specific advice, avoid inventing clinical facts, surface missing inputs when needed, and prioritize escalation guidance for emergencies or mental-health crises.