tooluniverse-rare-disease-diagnosis

6
1
Source

Provide differential diagnosis for patients with suspected rare diseases based on phenotype and genetic data. Matches symptoms to HPO terms, identifies candidate diseases from Orphanet/OMIM, prioritizes genes for testing, interprets variants of uncertain significance. Use when clinician asks about rare disease diagnosis, unexplained phenotypes, or genetic testing interpretation.

Install

mkdir -p .claude/skills/tooluniverse-rare-disease-diagnosis && curl -L -o skill.zip "https://mcp.directory/api/skills/download/3104" && unzip -o skill.zip -d .claude/skills/tooluniverse-rare-disease-diagnosis && rm skill.zip

Installs to .claude/skills/tooluniverse-rare-disease-diagnosis

About this skill

Rare Disease Diagnosis Advisor

Systematic diagnosis support for rare diseases using phenotype matching, gene panel prioritization, and variant interpretation across Orphanet, OMIM, HPO, ClinVar, and structure-based analysis.

KEY PRINCIPLES:

  1. Report-first approach - Create report file FIRST, update progressively
  2. Phenotype-driven - Convert symptoms to HPO terms before searching
  3. Multi-database triangulation - Cross-reference Orphanet, OMIM, OpenTargets
  4. Evidence grading - Grade diagnoses by supporting evidence strength
  5. Actionable output - Prioritized differential diagnosis with next steps
  6. Genetic counseling aware - Consider inheritance patterns and family history
  7. English-first queries - Always use English terms in tool calls (phenotype descriptions, gene names, disease names), even if the user writes in another language. Only try original-language terms as a fallback. Respond in the user's language

When to Use

Apply when user asks:

  • "Patient has [symptoms], what rare disease could this be?"
  • "Unexplained developmental delay with [features]"
  • "WES found VUS in [gene], is this pathogenic?"
  • "What genes should we test for [phenotype]?"
  • "Differential diagnosis for [rare symptom combination]"

Report-First Approach (MANDATORY)

  1. Create the report file FIRST: [PATIENT_ID]_rare_disease_report.md with all section headers and [Researching...] placeholders
  2. Progressively update as you gather data
  3. Output separate data files:
    • [PATIENT_ID]_gene_panel.csv - Prioritized genes for testing
    • [PATIENT_ID]_variant_interpretation.csv - If variants provided

Every finding MUST include source citation (ORPHA code, OMIM number, tool name).

See REPORT_TEMPLATE.md for the full template and example outputs for each phase.


Tool Parameter Corrections

ToolWRONG ParameterCORRECT Parameter
OpenTargets_get_associated_diseases_by_target_ensemblIdensemblIDensemblId
ClinVar_get_variant_by_idvariant_idid
MyGene_query_genesgeneq
gnomAD_get_variant_frequenciesvariantvariant_id

Workflow Overview

Phase 1: Phenotype Standardization
  Convert symptoms to HPO terms, identify core vs. variable features, note onset/inheritance
      |
Phase 2: Disease Matching
  Search Orphanet, cross-reference OMIM, query DisGeNET -> Ranked differential diagnosis
      |
Phase 3: Gene Panel Identification
  Extract genes from top diseases, validate with ClinGen, check expression (GTEx)
      |
Phase 3.5: Expression & Tissue Context
  CELLxGENE cell-type expression, ChIPAtlas regulatory context
      |
Phase 3.6: Pathway Analysis
  KEGG pathways, Reactome processes, IntAct protein interactions
      |
Phase 4: Variant Interpretation (if provided)
  ClinVar lookup, gnomAD frequency, computational predictions (CADD, AlphaMissense, EVE, SpliceAI)
      |
Phase 5: Structure Analysis (for VUS)
  AlphaFold2 prediction, domain impact assessment (InterPro)
      |
Phase 6: Literature Evidence
  PubMed studies, BioRxiv/MedRxiv preprints, OpenAlex citation analysis
      |
Phase 7: Report Synthesis
  Prioritized differential, recommended testing, next steps

For detailed code examples and algorithms for each phase, see DIAGNOSTIC_WORKFLOW.md.


Phase Summaries

Phase 1: Phenotype Standardization

  • Use HPO_search_terms(query=symptom) to convert each clinical description to HPO terms
  • Classify features as Core (always present), Variable (>50%), Occasional (<50%), or Age-specific
  • Record age of onset and family history for inheritance pattern hints

Phase 2: Disease Matching

  • Orphanet: Orphanet_search_diseases(operation="search_diseases", query=keyword) then Orphanet_get_genes(operation="get_genes", orpha_code=code) for each hit
  • OMIM: OMIM_search(operation="search", query=gene) then OMIM_get_entry and OMIM_get_clinical_synopsis for details
  • DisGeNET: DisGeNET_search_gene(operation="search_gene", gene=symbol) for gene-disease association scores
  • Score phenotype overlap: Excellent (>80%), Good (60-80%), Possible (40-60%), Unlikely (<40%)

Phase 3: Gene Panel Identification

  • Extract genes from top candidate diseases
  • ClinGen validation (critical): ClinGen_search_gene_validity, ClinGen_search_dosage_sensitivity, ClinGen_search_actionability
  • ClinGen classification determines panel inclusion:
    • Definitive/Strong/Moderate: Include in panel
    • Limited: Include but flag
    • Disputed/Refuted: Exclude
  • Expression: Use MyGene_query_genes for Ensembl ID, then GTEx_get_median_gene_expression to confirm tissue expression
  • Prioritization scoring: Tier 1 (top disease gene +5), Tier 2 (multi-disease +3), Tier 3 (ClinGen Definitive +3), Tier 4 (tissue expression +2), Tier 5 (pLI >0.9 +1)

Phase 3.5: Expression & Tissue Context

  • CELLxGENE: CELLxGENE_get_expression_data and CELLxGENE_get_cell_metadata for cell-type specific expression
  • ChIPAtlas: ChIPAtlas_enrichment_analysis and ChIPAtlas_get_peak_data for regulatory context (TF binding)
  • Confirms candidate genes are expressed in disease-relevant tissues/cells

Phase 3.6: Pathway Analysis

  • KEGG: kegg_find_genes(query="hsa:{gene}") then kegg_get_gene_info for pathway membership
  • IntAct: intact_search_interactions(query=gene, species="human") for protein-protein interactions
  • Identify convergent pathways across candidate genes (strengthens candidacy)

Phase 4: Variant Interpretation (if provided)

  • ClinVar: ClinVar_search_variants(query=hgvs) for existing classifications
  • gnomAD: gnomAD_get_variant_frequencies(variant_id=id) for population frequency
    • Ultra-rare (<0.00001), Rare (<0.0001), Low frequency (<0.01), Common (likely benign)
  • Computational predictions (for VUS):
    • CADD: CADD_get_variant_score - PHRED >=20 supports PP3
    • AlphaMissense: AlphaMissense_get_variant_score - pathogenic classification = strong PP3
    • EVE: EVE_get_variant_score - score >0.5 supports PP3
    • SpliceAI: SpliceAI_predict_splice - delta score >=0.5 indicates splice impact
  • ACMG criteria: PVS1 (null variant), PS1 (same AA change), PM2 (absent from pop), PP3 (computational), BA1 (>5% AF)
  • Consensus from 2+ concordant predictors strengthens PP3 evidence

Phase 5: Structure Analysis (for VUS)

  • Perform when: VUS, missense in critical domain, novel variant, or additional evidence needed
  • AlphaFold2: NvidiaNIM_alphafold2(sequence=seq, algorithm="mmseqs2") for structure prediction
  • Domain impact: InterPro_get_protein_domains(accession=uniprot_id) to check functional domains
  • Assess pLDDT confidence at variant position, domain location, structural role

Phase 6: Literature Evidence

  • PubMed: PubMed_search_articles(query="disease AND genetics") for published studies
  • Preprints: BioRxiv_search_preprints, ArXiv_search_papers(category="q-bio") for latest findings
  • Citations: openalex_search_works for citation analysis of key papers
  • Note: preprints are not peer-reviewed; flag accordingly

Phase 7: Report Synthesis

  • Compile all phases into final report with evidence grading
  • Provide prioritized differential diagnosis with next steps
  • Include specialist referral suggestions and family screening recommendations

Evidence Grading

TierCriteriaExample
T1 (High)Phenotype match >80% + gene matchMarfan with FBN1 mutation
T2 (Medium-High)Phenotype match 60-80% OR likely pathogenic variantGood phenotype fit
T3 (Medium)Phenotype match 40-60% OR VUS in candidate genePossible diagnosis
T4 (Low)Phenotype <40% OR uncertain geneLow probability

Completeness Checklist

Phase 1 (Phenotype): All symptoms as HPO terms, core vs. variable distinguished, onset documented, family history noted

Phase 2 (Disease Matching): >=5 candidates (or all matching), overlap % calculated, inheritance patterns, ORPHA + OMIM IDs

Phase 3 (Gene Panel): >=5 genes prioritized, ClinGen evidence level per gene, expression validated, testing strategy recommended

Phase 4 (Variants): ClinVar classification, gnomAD frequency, ACMG criteria applied, classification justified

Phase 5 (Structure): Structure predicted (if VUS), pLDDT reported, domain impact assessed, structural evidence summarized

Phase 6 (Recommendations): >=3 next steps, specialist referrals, family screening addressed

See CHECKLIST.md for the full interactive checklist.


Fallback Chains

Primary ToolFallback 1Fallback 2
Orphanet_search_by_hpoOMIM_searchPubMed phenotype search
ClinVar_get_variantgnomAD_get_variantVEP annotation
NvidiaNIM_alphafold2alphafold_get_predictionUniProt features
GTEx_expressionHPA_expressionTissue-specific literature
gnomAD_get_variantExAC_frequencies1000 Genomes

Reference Files

tooluniverse-precision-oncology

mims-harvard

Provide actionable treatment recommendations for cancer patients based on molecular profile. Interprets tumor mutations, identifies FDA-approved therapies, finds resistance mechanisms, matches clinical trials. Use when oncologist asks about treatment options for specific mutations (EGFR, KRAS, BRAF, etc.), therapy resistance, or clinical trial eligibility.

203

tooluniverse-drug-research

mims-harvard

Generates comprehensive drug research reports with compound disambiguation, evidence grading, and mandatory completeness sections. Covers identity, chemistry, pharmacology, targets, clinical trials, safety, pharmacogenomics, and ADMET properties. Use when users ask about drugs, medications, therapeutics, or need drug profiling, safety assessment, or clinical development research.

213

tooluniverse-pharmacovigilance

mims-harvard

Analyze drug safety signals from FDA adverse event reports, label warnings, and pharmacogenomic data. Calculates disproportionality measures (PRR, ROR), identifies serious adverse events, assesses pharmacogenomic risk variants. Use when asked about drug safety, adverse events, post-market surveillance, or risk-benefit assessment.

202

drug-repurposing

mims-harvard

Identify drug repurposing candidates using ToolUniverse for target-based, compound-based, and disease-driven strategies. Searches existing drugs for new therapeutic indications by analyzing targets, bioactivity, safety profiles, and literature evidence. Use when exploring drug repurposing opportunities, finding new indications for approved drugs, or when users mention drug repositioning, off-label uses, or therapeutic alternatives.

202

tooluniverse-expression-data-retrieval

mims-harvard

Retrieves gene expression and omics datasets from ArrayExpress and BioStudies with gene disambiguation, experiment quality assessment, and structured reports. Creates comprehensive dataset profiles with metadata, sample information, and download links. Use when users need expression data, omics datasets, or mention ArrayExpress (E-MTAB, E-GEOD) or BioStudies (S-BSST) accessions.

172

tooluniverse-target-research

mims-harvard

Gather comprehensive biological target intelligence from 9 parallel research paths covering protein info, structure, interactions, pathways, expression, variants, drug interactions, and literature. Features collision-aware searches, evidence grading (T1-T4), explicit Open Targets coverage, and mandatory completeness auditing. Use when users ask about drug targets, proteins, genes, or need target validation, druggability assessment, or comprehensive target profiling.

52

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,5651,368

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

1,1101,184

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

1,4141,106

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

1,192746

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

1,148683

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

1,304608

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.