plugins/tooluniverse/skills/tooluniverse-pathway-disease-genetics/SKILL.md
Connect GWAS variants to biological pathways and druggable targets. Maps GWAS hits to causal genes (via fine-mapping/eQTL), then to pathways (Reactome, KEGG, WikiPathways), then to existing drugs hitting those pathways. Use for pathway-level disease mechanisms, druggable-pathway prioritization from GWAS, SNP-to-pathway-to-target tracing, and tissue-specific eQTL evidence for drug target hypotheses.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-pathway-disease-geneticsInstall 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.
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.
Connect genome-wide association study (GWAS) variants to biological pathways for mechanistic understanding and drug target discovery.
A gene found in GWAS doesn't tell you which pathway is dysregulated. To connect gene -> pathway -> disease mechanism, ask: what biological process does this gene participate in? Use Reactome/KEGG to find pathways, then ask: which of these pathways is relevant to the disease phenotype?
For example, TCF7L2 is the strongest T2D GWAS gene. It participates in the Wnt signaling pathway. The question is then: how does disrupted Wnt signaling impair beta-cell function or insulin secretion? That reasoning step — from pathway membership to disease mechanism — requires combining pathway data with tissue expression (GTEx) and disease biology.
Non-coding GWAS variants (the majority) rarely affect the nearest gene. They act through regulatory elements that alter expression of genes sometimes hundreds of kilobases away. Always check eQTL evidence before assuming the nearest gene is causal.
Multiple disease genes mapping to the same pathway is stronger evidence than a single gene. If 5 GWAS hits for a disease all map to the NF-kB pathway, that is strong mechanistic evidence — the pathway is likely causal, not just coincidentally hit. If GWAS genes scatter across unrelated pathways, the mechanism is unclear, and you may need to look at upstream regulators or gene network hubs that connect the scattered genes.
When running enrichment (Reactome, KEGG, STRING), prioritize pathways that appear across multiple databases. A pathway enriched in all three is more reliable than one that appears in only one analysis.
A pathway with existing drugs targeting its components is more actionable than a novel pathway. Before proposing a target as novel, check: are any pathway members already drug targets? Use DGIdb and OpenTargets to survey approved and clinical-stage drugs in the pathway.
Priorities: (1) approved drug for a different indication hitting a GWAS-supported target = strong repurposing opportunity; (2) drug in clinical trials hitting a GWAS-supported target = accelerated validation path; (3) druggable gene with no existing drugs + strong GWAS evidence = novel target opportunity.
"Undruggable" by current modalities does not mean permanently undruggable. Flag such genes but do not dismiss them — they may be actionable via gene therapy, RNA therapeutics, or downstream pathway intervention.
Resolve disease name to ontology ID first:
OpenTargets_multi_entity_search_by_query_string(queryString=<disease>) — returns EFO/MONDO IDsCollect GWAS signals:
gwas_search_associations(query=<disease>) — broad searchgwas_get_variants_for_trait(trait=<trait>, p_value_threshold=5e-8) — genome-wide significant hitsgwas_get_snps_for_gene(gene_symbol=<gene>) — gene-centric searchGotcha: gwas_get_associations_for_trait is broken — use gwas_search_associations instead. gwas_get_snps_for_gene uses gene_symbol, not mapped_gene.
Annotate variants:
EnsemblVEP_annotate_rsid(variant_id=<rsid>) — functional consequence, nearest gene{data, metadata}, or {error} — handle all threeQuery eQTL evidence in tissue relevant to the disease (e.g., pancreas for T2D, brain for neurological):
GTEx_query_eqtl(gene_input=<gene>, tissue=<tissue>) — never pass empty gene_inputGTEx_get_expression_summary(gene_input=<gene>) — expression across all tissuesGTEx_get_median_gene_expression(gencode_id=[<versioned_id>], tissue_site_detail_id=[<tissue>]) — use versioned Ensembl IDs (e.g., ENSG00000148737.11) and gtex_v8Run enrichment across multiple databases and cross-validate results:
ReactomeAnalysis_pathway_enrichment(identifiers="P04637 P38398 ...") — space-separated UniProt STRING, not an arrayReactome_map_uniprot_to_pathways(uniprot_id=<id>) — per-gene pathway membershipReactome_get_participants(pathway_id=<R-HSA-XXXXX>) — all genes in a pathwayKEGG_get_gene_pathways(gene_id=<kegg_id>) — KEGG pathways for one genekegg_search_pathway(query=<disease_or_process>) — keyword searchSTRING_functional_enrichment(protein_ids=[<genes>], species=9606) — GO/KEGG/Reactome with FDRPANTHER_enrichment(gene_list="GENE1,GENE2,...", organism=9606, annotation_dataset="GO:0008150") — comma-separated STRING, not arrayMetaCyc note: Currently unavailable (BioCyc requires authentication). Use KEGG or Reactome for metabolic pathways.
DGIdb_get_gene_druggability(genes=[<gene_list>]) — categories: clinically actionable, druggable, etc.DGIdb_get_drug_gene_interactions(genes=[<gene_list>]) — use genes param (array), not gene_nameOpenTargets_get_associated_drugs_by_target_ensemblID(ensemblId=<id>) — approved and clinical drugsOpenTargets_target_disease_evidence(ensemblId=<id>, efoId=<disease_id>) — genetic + other evidence scoreOpenTargets_multi_entity_search_by_query_stringgwas_get_variants_for_trait (p < 5e-8)OpenTargets_target_disease_evidence for additional genetic evidenceEvidence tiers: High = GWAS p < 5e-8 + eQTL colocalization in relevant tissue + coding variant; Medium = GWAS p < 5e-8 + eQTL in any tissue; Low = GWAS p < 5e-8 + positional mapping only.
ReactomeAnalysis_pathway_enrichment and STRING_functional_enrichmentKEGG_get_gene_pathwayshumanbase_ppi_analysis (all 5 params required: gene_list, tissue, max_node, interaction, string_mode)Reactome_get_participants and KEGG_get_pathway_genesDGIdb_get_gene_druggabilityOpenTargets_get_associated_drugs_by_target_ensemblIDFinal ranking: Genetic Evidence x Druggability x Pathway Centrality. Flag novel targets (strong genetic + no existing drugs) and repurposing opportunities (approved drug + genetic support in this disease).
gwas_get_snps_for_gene: use gene_symbol, not mapped_geneOpenTargets_multi_entity_search_by_query_string: use queryString, not queryGTEx_query_eqtl: gene_input must never be emptyGTEx_get_median_gene_expression: use versioned gencode IDs; use gtex_v8ReactomeAnalysis_pathway_enrichment: identifiers is space-separated STRING, not arrayDGIdb_get_drug_gene_interactions: use genes (array), not gene_namePANTHER_enrichment: gene_list is comma-separated STRING, not arrayhumanbase_ppi_analysis: all 5 params requiredEnsemblVEP_annotate_rsid: use variant_id, not rsidkegg_find_genes: include organism="hsa" for human genestools
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.