tooluniverse-multiomic-disease-characterization▌
mims-harvard/tooluniverse · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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(useefo_idfor precision, not free-textdisease_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 (acceptsgene_symboldirectly)- 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-separatedenrichr_gene_enrichment_analysis— param:gene_list(array),libs(array). NOTE:datafield is a JSON string that needs parsingkegg_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:genesas array). Often more comprehensive than OpenTargets for drug-gene data.- OpenTargets drugs/tractability (use EFO IDs like
EFO_0000384for Crohn's, not MONDO — MONDO IDs may return null for drug queries) search_clinical_trials—query_termis 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.mdfor quality checklist and scoring formula
Key Tool Parameter Notes
These are the most common parameter pitfalls:
OpenTargetsdisease IDs: underscore format (MONDO_0004975), NOT colonSTRINGprotein_ids: must be array (['APOE']), not stringenrichrlibs: 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:pageSizeis REQUIREDsearch_clinical_trials:query_termis REQUIRED even ifconditionis 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 |
How to use tooluniverse-multiomic-disease-characterization on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add tooluniverse-multiomic-disease-characterization
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches tooluniverse-multiomic-disease-characterization from GitHub repository mims-harvard/tooluniverse and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate tooluniverse-multiomic-disease-characterization. Access the skill through slash commands (e.g., /tooluniverse-multiomic-disease-characterization) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★37 reviews- ★★★★★Michael Smith· Dec 24, 2024
Keeps context tight: tooluniverse-multiomic-disease-characterization is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chinedu Ramirez· Dec 20, 2024
tooluniverse-multiomic-disease-characterization reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Naina Ghosh· Dec 16, 2024
tooluniverse-multiomic-disease-characterization has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Dhruvi Jain· Dec 8, 2024
I recommend tooluniverse-multiomic-disease-characterization for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· Nov 27, 2024
tooluniverse-multiomic-disease-characterization fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ren Sethi· Nov 11, 2024
Registry listing for tooluniverse-multiomic-disease-characterization matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Evelyn Mehta· Nov 7, 2024
Solid pick for teams standardizing on skills: tooluniverse-multiomic-disease-characterization is focused, and the summary matches what you get after install.
- ★★★★★Evelyn Singh· Oct 26, 2024
I recommend tooluniverse-multiomic-disease-characterization for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ganesh Mohane· Oct 18, 2024
tooluniverse-multiomic-disease-characterization has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chinedu Abbas· Oct 2, 2024
Useful defaults in tooluniverse-multiomic-disease-characterization — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 37