Multi-Omics Disease Characterization Pipeline
Characterize diseases across multiple molecular layers (genomics, transcriptomics, proteomics, pathways) to provide systems-level understanding of disease mechanisms, identify therapeutic opportunities, and discover biomarker candidates.
KEY PRINCIPLES:
- Report-first approach - Create report file FIRST, then populate progressively
- Disease disambiguation FIRST - Resolve all identifiers before omics analysis
- Layer-by-layer analysis - Systematically cover all omics layers
- Cross-layer integration - Identify genes/targets appearing in multiple layers
- Evidence grading - Grade all evidence as T1 (human/clinical) to T4 (computational)
- Tissue context - Emphasize disease-relevant tissues/organs
- Quantitative scoring - Multi-Omics Confidence Score (0-100)
- Druggable focus - Prioritize targets with therapeutic potential
- Biomarker identification - Highlight diagnostic/prognostic markers
- Mechanistic synthesis - Generate testable hypotheses
- Source references - Every statement must cite tool/database
- Completeness checklist - Mandatory section showing analysis coverage
- English-first queries - Always use English terms in tool calls. Respond in user's language
Multi-omics disease characterization asks: what molecular layers are dysregulated? Genomic mutations → transcriptomic changes → proteomic effects → metabolomic consequences. Concordance across layers strengthens the finding. Discordance reveals regulatory complexity.
LOOK UP, DON'T GUESS
When uncertain about any scientific fact, SEARCH databases first rather than reasoning from memory. A database-verified answer is always more reliable than a guess.
COMPUTE, DON'T DESCRIBE
When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.
When to Use This Skill
Apply when users:
- Ask about disease mechanisms across omics layers
- Need multi-omics characterization of a disease
- Want to understand disease at the systems biology level
- Ask "What pathways/genes/proteins are involved in [disease]?"
- Need biomarker discovery for a disease
- Want to identify druggable targets from disease profiling
- Ask for integrated genomics + transcriptomics + proteomics analysis
- Need cross-layer concordance analysis
- Ask about disease network biology / hub genes
NOT for (use other skills instead):
- Single gene/target validation -> Use
tooluniverse-drug-target-validation
- Drug safety profiling -> Use
tooluniverse-adverse-event-detection
- General disease overview -> Use
tooluniverse-disease-research
- Variant interpretation -> Use
tooluniverse-variant-interpretation
- GWAS-specific analysis -> Use
tooluniverse-gwas-* skills
- Pathway-only analysis -> Use
tooluniverse-systems-biology
Input Parameters
| Parameter |
Required |
Description |
Example |
| disease |
Yes |
Disease name, OMIM ID, EFO ID, or MONDO ID |
Alzheimer disease, MONDO_0004975 |
| tissue |
No |
Tissue/organ of interest |
brain, liver, blood |
| focus_layers |
No |
Specific omics layers to emphasize |
genomics, transcriptomics, pathways |
Pipeline Overview
The pipeline runs 9 phases sequentially. Each phase uses specific tools documented in detail in tool-reference.md.
Phase 0: Disease Disambiguation (ALWAYS FIRST)
Resolve disease to standard identifiers (MONDO/EFO) for all downstream queries.
- Primary tool:
OpenTargets_get_disease_id_description_by_name
- Get description, synonyms, therapeutic areas, disease hierarchy, cross-references
- CRITICAL: Disease IDs use underscore format (e.g.,
MONDO_0004975), NOT colon
- If ambiguous, present top 3-5 options and ask user to select
Phase 1: Genomics Layer
Identify genetic variants, GWAS associations, and genetically implicated genes.
- Tools:
gwas_search_associations (use efo_id for precision, not free-text disease_trait), gwas_get_snps_for_gene, ClinVar, OpenTargets associated targets
gnomad_get_gene_constraints — gene constraint metrics (pLI, oe_lof) to interpret whether LoF variants are tolerated vs. haploinsufficient
- Get top 10-15 genes with genetic evidence scores; track Ensembl IDs for downstream phases
Phase 2: Transcriptomics Layer
Identify differentially expressed genes, tissue-specific expression, and expression-based biomarkers.
GTEx_get_expression_summary — baseline expression across 54 tissues (accepts gene_symbol directly)
- Tools: Expression Atlas, HPA (tissue expression), EuropePMC scores
- Check expression in disease-relevant tissues for top genes from Phase 1
Phase 3: Proteomics & Interaction Layer
Map protein-protein interactions, identify hub genes, and characterize interaction networks.
UniProt_get_function_by_accession — protein function narrative (essential for mechanistic context)
- Tools:
STRING_get_network (param: identifiers, species=9606), intact_get_interactions, HumanBase
- Build PPI network from top 15-20 genes; identify hub genes by degree centrality
Phase 4: Pathway & Network Layer
Identify enriched biological pathways and cross-pathway connections.
ReactomeAnalysis_pathway_enrichment — identifiers are newline-separated (\n), NOT space-separated
enrichr_gene_enrichment_analysis — param: gene_list (array), libs (array). NOTE: data field is a JSON string that needs parsing
kegg_search_pathway — pathway keyword search
Phase 5: Gene Ontology & Functional Annotation
Characterize biological processes, molecular functions, and cellular components.
- Tools: Enrichr (GO libraries), QuickGO, GO annotations, OpenTargets GO
- Run GO enrichment for all 3 aspects (BP, MF, CC)
Phase 6: Therapeutic Landscape
Map approved drugs, druggable targets, repurposing opportunities, and clinical trials.
DGIdb_get_drug_gene_interactions — drug interactions by gene (param: genes as array). Often more comprehensive than OpenTargets for drug-gene data.
- OpenTargets drugs/tractability (use EFO IDs like
EFO_0000384 for Crohn's, not MONDO — MONDO IDs may return null for drug queries)
search_clinical_trials — query_term is REQUIRED
Phase 7: Multi-Omics Integration
Integrate findings across all layers. See integration-scoring.md for full details.
- Cross-layer gene concordance: count layers per gene, score multi-layer hub genes
- Direction concordance: genetics + expression agreement
- Biomarker identification: diagnostic, prognostic, predictive
- Mechanistic hypothesis generation
Phase 8: Report Finalization
Write executive summary, calculate confidence score, verify completeness.
- See
integration-scoring.md for quality checklist and scoring formula
Key Tool Parameter Notes
These are the most common parameter pitfalls:
OpenTargets disease IDs: underscore format (MONDO_0004975), NOT colon
STRING protein_ids: must be array (['APOE']), not string
enrichr libs: must be array (['KEGG_2021_Human'])
HPA_get_rna_expression_by_source: ALL 3 params required (gene_name, source_type, source_name)
humanbase_ppi_analysis: ALL params required (gene_list, tissue, max_node, interaction, string_mode)
expression_atlas_disease_target_score: pageSize is REQUIRED
search_clinical_trials: query_term is REQUIRED even if condition is provided
For full tool parameters and per-phase workflows, see tool-reference.md.
Reference Files
All detailed content is in reference files in this directory:
| File |
Contents |
tool-reference.md |
Full tool parameters, inputs/outputs, per-phase workflows, quick reference table |
report-template.md |
Complete report markdown template with all sections and checklists |
integration-scoring.md |
Confidence score formula (0-100), evidence grading (T1-T4), integration procedures, quality checklist |
response-formats.md |
Verified JSON response structures for key tools |
use-patterns.md |
Common use patterns, edge case handling, fallback strategies |
1---
2name: tooluniverse-multiomic-disease-characterization
3description: Comprehensive disease characterization across genomics, transcriptomics, proteomics, and pathways for systems-level understanding. Identifies therapeutic opportunities and biomarker candidates by integrating multi-layer molecular data. Use for full-omics disease deep-dive reports, mechanism mapping, and biomarker-and-target identification from multi-omics data.
4disable-model-invocation: true
5---
6
7# Multi-Omics Disease Characterization Pipeline
8
9Characterize diseases across multiple molecular layers (genomics, transcriptomics, proteomics, pathways) to provide systems-level understanding of disease mechanisms, identify therapeutic opportunities, and discover biomarker candidates.
10
11**KEY PRINCIPLES**:
121. **Report-first approach** - Create report file FIRST, then populate progressively
132. **Disease disambiguation FIRST** - Resolve all identifiers before omics analysis
143. **Layer-by-layer analysis** - Systematically cover all omics layers
154. **Cross-layer integration** - Identify genes/targets appearing in multiple layers
165. **Evidence grading** - Grade all evidence as T1 (human/clinical) to T4 (computational)
176. **Tissue context** - Emphasize disease-relevant tissues/organs
187. **Quantitative scoring** - Multi-Omics Confidence Score (0-100)
198. **Druggable focus** - Prioritize targets with therapeutic potential
209. **Biomarker identification** - Highlight diagnostic/prognostic markers
2110. **Mechanistic synthesis** - Generate testable hypotheses
2211. **Source references** - Every statement must cite tool/database
2312. **Completeness checklist** - Mandatory section showing analysis coverage
2413. **English-first queries** - Always use English terms in tool calls. Respond in user's language
25
26Multi-omics disease characterization asks: what molecular layers are dysregulated? Genomic mutations → transcriptomic changes → proteomic effects → metabolomic consequences. Concordance across layers strengthens the finding. Discordance reveals regulatory complexity.
27
28## LOOK UP, DON'T GUESS
29When uncertain about any scientific fact, SEARCH databases first rather than reasoning from memory. A database-verified answer is always more reliable than a guess.
30
31---
32
33## COMPUTE, DON'T DESCRIBE
34When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.
35
36## When to Use This Skill
37
38Apply when users:
39- Ask about disease mechanisms across omics layers
40- Need multi-omics characterization of a disease
41- Want to understand disease at the systems biology level
42- Ask "What pathways/genes/proteins are involved in [disease]?"
43- Need biomarker discovery for a disease
44- Want to identify druggable targets from disease profiling
45- Ask for integrated genomics + transcriptomics + proteomics analysis
46- Need cross-layer concordance analysis
47- Ask about disease network biology / hub genes
48
49**NOT for** (use other skills instead):
50- Single gene/target validation -> Use `tooluniverse-drug-target-validation`
51- Drug safety profiling -> Use `tooluniverse-adverse-event-detection`
52- General disease overview -> Use `tooluniverse-disease-research`
53- Variant interpretation -> Use `tooluniverse-variant-interpretation`
54- GWAS-specific analysis -> Use `tooluniverse-gwas-*` skills
55- Pathway-only analysis -> Use `tooluniverse-systems-biology`
56
57---
58
59## Input Parameters
60
61| Parameter | Required | Description | Example |
62|-----------|----------|-------------|---------|
63| **disease** | Yes | Disease name, OMIM ID, EFO ID, or MONDO ID | `Alzheimer disease`, `MONDO_0004975` |
64| **tissue** | No | Tissue/organ of interest | `brain`, `liver`, `blood` |
65| **focus_layers** | No | Specific omics layers to emphasize | `genomics`, `transcriptomics`, `pathways` |
66
67---
68
69## Pipeline Overview
70
71The pipeline runs 9 phases sequentially. Each phase uses specific tools documented in detail in `tool-reference.md`.
72
73### Phase 0: Disease Disambiguation (ALWAYS FIRST)
74Resolve disease to standard identifiers (MONDO/EFO) for all downstream queries.
75- Primary tool: `OpenTargets_get_disease_id_description_by_name`
76- Get description, synonyms, therapeutic areas, disease hierarchy, cross-references
77- **CRITICAL**: Disease IDs use underscore format (e.g., `MONDO_0004975`), NOT colon
78- If ambiguous, present top 3-5 options and ask user to select
79
80### Phase 1: Genomics Layer
81Identify genetic variants, GWAS associations, and genetically implicated genes.
82- Tools: `gwas_search_associations` (use `efo_id` for precision, not free-text `disease_trait`), `gwas_get_snps_for_gene`, ClinVar, OpenTargets associated targets
83- `gnomad_get_gene_constraints` — gene constraint metrics (pLI, oe_lof) to interpret whether LoF variants are tolerated vs. haploinsufficient
84- Get top 10-15 genes with genetic evidence scores; track Ensembl IDs for downstream phases
85
86### Phase 2: Transcriptomics Layer
87Identify differentially expressed genes, tissue-specific expression, and expression-based biomarkers.
88- `GTEx_get_expression_summary` — baseline expression across 54 tissues (accepts `gene_symbol` directly)
89- Tools: Expression Atlas, HPA (tissue expression), EuropePMC scores
90- Check expression in disease-relevant tissues for top genes from Phase 1
91
92### Phase 3: Proteomics & Interaction Layer
93Map protein-protein interactions, identify hub genes, and characterize interaction networks.
94- `UniProt_get_function_by_accession` — protein function narrative (essential for mechanistic context)
95- Tools: `STRING_get_network` (param: `identifiers`, `species`=9606), `intact_get_interactions`, HumanBase
96- Build PPI network from top 15-20 genes; identify hub genes by degree centrality
97
98### Phase 4: Pathway & Network Layer
99Identify enriched biological pathways and cross-pathway connections.
100- `ReactomeAnalysis_pathway_enrichment` — identifiers are **newline-separated** (`\n`), NOT space-separated
101- `enrichr_gene_enrichment_analysis` — param: `gene_list` (array), `libs` (array). NOTE: `data` field is a JSON string that needs parsing
102- `kegg_search_pathway` — pathway keyword search
103
104### Phase 5: Gene Ontology & Functional Annotation
105Characterize biological processes, molecular functions, and cellular components.
106- Tools: Enrichr (GO libraries), QuickGO, GO annotations, OpenTargets GO
107- Run GO enrichment for all 3 aspects (BP, MF, CC)
108
109### Phase 6: Therapeutic Landscape
110Map approved drugs, druggable targets, repurposing opportunities, and clinical trials.
111- `DGIdb_get_drug_gene_interactions` — drug interactions by gene (param: `genes` as array). Often more comprehensive than OpenTargets for drug-gene data.
112- OpenTargets drugs/tractability (use **EFO IDs** like `EFO_0000384` for Crohn's, not MONDO — MONDO IDs may return null for drug queries)
113- `search_clinical_trials` — `query_term` is REQUIRED
114
115### Phase 7: Multi-Omics Integration
116Integrate findings across all layers. See `integration-scoring.md` for full details.
117- Cross-layer gene concordance: count layers per gene, score multi-layer hub genes
118- Direction concordance: genetics + expression agreement
119- Biomarker identification: diagnostic, prognostic, predictive
120- Mechanistic hypothesis generation
121
122### Phase 8: Report Finalization
123Write executive summary, calculate confidence score, verify completeness.
124- See `integration-scoring.md` for quality checklist and scoring formula
125
126---
127
128## Key Tool Parameter Notes
129
130These are the most common parameter pitfalls:
131- `OpenTargets` disease IDs: underscore format (`MONDO_0004975`), NOT colon
132- `STRING` `protein_ids`: must be **array** (`['APOE']`), not string
133- `enrichr` `libs`: must be **array** (`['KEGG_2021_Human']`)
134- `HPA_get_rna_expression_by_source`: ALL 3 params required (`gene_name`, `source_type`, `source_name`)
135- `humanbase_ppi_analysis`: ALL params required (`gene_list`, `tissue`, `max_node`, `interaction`, `string_mode`)
136- `expression_atlas_disease_target_score`: `pageSize` is REQUIRED
137- `search_clinical_trials`: `query_term` is REQUIRED even if `condition` is provided
138
139For full tool parameters and per-phase workflows, see `tool-reference.md`.
140
141---
142
143## Reference Files
144
145All detailed content is in reference files in this directory:
146
147| File | Contents |
148|------|----------|
149| `tool-reference.md` | Full tool parameters, inputs/outputs, per-phase workflows, quick reference table |
150| `report-template.md` | Complete report markdown template with all sections and checklists |
151| `integration-scoring.md` | Confidence score formula (0-100), evidence grading (T1-T4), integration procedures, quality checklist |
152| `response-formats.md` | Verified JSON response structures for key tools |
153| `use-patterns.md` | Common use patterns, edge case handling, fallback strategies |