plugin/skills/tooluniverse-multiomic-disease-characterization/SKILL.md
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.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-multiomic-disease-characterizationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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:
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.
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.
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.
Apply when users:
NOT for (use other skills instead):
tooluniverse-drug-target-validationtooluniverse-adverse-event-detectiontooluniverse-disease-researchtooluniverse-variant-interpretationtooluniverse-gwas-* skillstooluniverse-systems-biology| 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 |
The pipeline runs 9 phases sequentially. Each phase uses specific tools documented in detail in tool-reference.md.
Resolve disease to standard identifiers (MONDO/EFO) for all downstream queries.
OpenTargets_get_disease_id_description_by_nameMONDO_0004975), NOT colonIdentify genetic variants, GWAS associations, and genetically implicated genes.
gwas_search_associations (use efo_id for precision, not free-text disease_trait), gwas_get_snps_for_gene, ClinVar, OpenTargets associated targetsgnomad_get_gene_constraints — gene constraint metrics (pLI, oe_lof) to interpret whether LoF variants are tolerated vs. haploinsufficientIdentify differentially expressed genes, tissue-specific expression, and expression-based biomarkers.
GTEx_get_expression_summary — baseline expression across 54 tissues (accepts gene_symbol directly)Map protein-protein interactions, identify hub genes, and characterize interaction networks.
UniProt_get_function_by_accession — protein function narrative (essential for mechanistic context)STRING_get_network (param: identifiers, species=9606), intact_get_interactions, HumanBaseIdentify enriched biological pathways and cross-pathway connections.
ReactomeAnalysis_pathway_enrichment — identifiers are newline-separated (\n), NOT space-separatedenrichr_gene_enrichment_analysis — param: gene_list (array), libs (array). NOTE: data field is a JSON string that needs parsingkegg_search_pathway — pathway keyword searchCharacterize biological processes, molecular functions, and cellular components.
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.EFO_0000384 for Crohn's, not MONDO — MONDO IDs may return null for drug queries)search_clinical_trials — query_term is REQUIREDIntegrate findings across all layers. See integration-scoring.md for full details.
Write executive summary, calculate confidence score, verify completeness.
integration-scoring.md for quality checklist and scoring formulaThese are the most common parameter pitfalls:
OpenTargets disease IDs: underscore format (MONDO_0004975), NOT colonSTRING protein_ids: must be array (['APOE']), not stringenrichr 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 REQUIREDsearch_clinical_trials: query_term is REQUIRED even if condition is providedFor full tool parameters and per-phase workflows, see tool-reference.md.
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 |
tools
Generate the success criteria for a task or question, then review work against them. Given a task, goal, or open-ended question, decompose it into scenarios, evaluation perspectives, and fine-grained weighted YES/NO criteria using the Recursive Expansion Tree (RET) method; if work is supplied, score it criterion-by-criterion and surface what is missing or could be better. Use when asked to self-review or check your own work, judge whether a task is done well or completely, build a definition-of-done or completeness checklist, create an evaluation rubric or grading criteria, score or grade answers to a question, set up an LLM-as-judge rubric, or when the user mentions self-review, completeness check, success criteria, evaluation criteria, scoring rubric, Qworld, or the RET algorithm.
tools
Find the real protein target(s) of a peptide from its sequence — peptide target deorphanization / off-target identification, for ANY target class (GPCR, ion channel, protease, cytokine/growth-factor receptor, enzyme, integrin), not only GPCRs. Use when a peptide has a phenotype but does not bind its hypothesized target, when a peptide binds a target in one species or assay but not another, or to screen candidate targets for an orphan peptide. A target-class router steers a multi-route keyless pipeline (PROSITE/ELM motif, BLAST homology, HGNC/InterPro/GPCRdb/GtoPdb target-family enumeration, OpenTargets phenotype anchor, EnsemblCompara/Alliance cross-species reconciliation) plus optional NVIDIA-NIM co-folding (Boltz2, AlphaFold2-Multimer, OpenFold3) for structural confirmation.
tools
Install or update ToolUniverse in Claude Science — create the conda env, install the tooluniverse pip package, and (re)build the tooluniverse-research skill by fetching the current workflow library from GitHub. Use for first-time setup, upgrading the ToolUniverse version, refreshing the bundled workflows after an upstream release, or reinstalling on a new machine.
tools
Install, set up, verify, update, pin, uninstall, or troubleshoot the ToolUniverse plugin on OpenAI Codex. ALWAYS consult this skill for any of those — don't answer from memory, because the exact marketplace name (mims-harvard/ToolUniverse), the "codex plugin marketplace add" then "codex plugin add -m tooluniverse" flow, Codex's startup auto-upgrade behavior, the uvx tooluniverse MCP server, and the API-key env vars are easy to get wrong. Use it whenever someone wants to get ToolUniverse (or "the 1000+ scientific tools" / "the harvard tools") working on Codex, says the Codex plugin or its tools/skills won't load, hits a uvx or MCP-server startup error, asks how Codex updates it, wants to pin or remove it, or finds it running an old tool version — even if they never say the word "plugin". Not for the Claude Code plugin (use tooluniverse-claude-code-plugin), for running research with the tools, or for authoring new tools or skills.