tooluniverse-pathway-disease-genetics
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.
What this skill does
## 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.
# Pathway-Disease Genetics: GWAS to Drug Targets via Pathways
Connect genome-wide association study (GWAS) variants to biological pathways for mechanistic understanding and drug target discovery.
## When to Use
- "What pathways are disrupted in [disease] based on GWAS?"
- "Which GWAS genes for [trait] are in druggable pathways?"
- "Map [SNP/variant] to its causal gene and pathway"
- "Find drug targets from GWAS data for [disease]"
- "What is the eQTL evidence for [gene] in [tissue]?"
---
## Core Reasoning Principles
### Gene-to-Pathway Reasoning
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.
### Pathway Convergence
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.
### Druggability Reasoning
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.
---
## Tool Selection Guide
### Phase 1: Disease Resolution and GWAS Collection
Resolve disease name to ontology ID first:
- `OpenTargets_multi_entity_search_by_query_string(queryString=<disease>)` — returns EFO/MONDO IDs
Collect GWAS signals:
- `gwas_search_associations(query=<disease>)` — broad search
- `gwas_get_variants_for_trait(trait=<trait>, p_value_threshold=5e-8)` — genome-wide significant hits
- `gwas_get_snps_for_gene(gene_symbol=<gene>)` — gene-centric search
**Gotcha:** `gwas_get_associations_for_trait` is broken — use `gwas_search_associations` instead. `gwas_get_snps_for_gene` uses `gene_symbol`, not `mapped_gene`.
### Phase 2: Variant Annotation and eQTL Evidence
Annotate variants:
- `EnsemblVEP_annotate_rsid(variant_id=<rsid>)` — functional consequence, nearest gene
- Response format is variable: list, `{data, metadata}`, or `{error}` — handle all three
Query 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_input`
- `GTEx_get_expression_summary(gene_input=<gene>)` — expression across all tissues
- `GTEx_get_median_gene_expression(gencode_id=[<versioned_id>], tissue_site_detail_id=[<tissue>])` — use versioned Ensembl IDs (e.g., `ENSG00000148737.11`) and `gtex_v8`
### Phase 3: Pathway Enrichment
Run enrichment across multiple databases and cross-validate results:
- `ReactomeAnalysis_pathway_enrichment(identifiers="P04637 P38398 ...")` — space-separated UniProt STRING, not an array
- `Reactome_map_uniprot_to_pathways(uniprot_id=<id>)` — per-gene pathway membership
- `Reactome_get_participants(pathway_id=<R-HSA-XXXXX>)` — all genes in a pathway
- `KEGG_get_gene_pathways(gene_id=<kegg_id>)` — KEGG pathways for one gene
- `kegg_search_pathway(query=<disease_or_process>)` — keyword search
- `STRING_functional_enrichment(protein_ids=[<genes>], species=9606)` — GO/KEGG/Reactome with FDR
- `PANTHER_enrichment(gene_list="GENE1,GENE2,...", organism=9606, annotation_dataset="GO:0008150")` — comma-separated STRING, not array
**MetaCyc note:** Currently unavailable (BioCyc requires authentication). Use KEGG or Reactome for metabolic pathways.
### Phase 4: Druggability and Drug Landscape
- `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_name`
- `OpenTargets_get_associated_drugs_by_target_ensemblID(ensemblId=<id>)` — approved and clinical drugs
- `OpenTargets_target_disease_evidence(ensemblId=<id>, efoId=<disease_id>)` — genetic + other evidence score
---
## Three-Step Workflow
### Step 1: GWAS to Causal Gene
1. Resolve disease ID via `OpenTargets_multi_entity_search_by_query_string`
2. Pull GWAS hits with `gwas_get_variants_for_trait` (p < 5e-8)
3. Annotate each lead SNP with VEP — is it coding or non-coding?
4. For non-coding variants, check eQTL via GTEx in the disease-relevant tissue
5. Prioritize genes where: GWAS SNP is also a significant eQTL AND the tissue is biologically relevant to the disease
6. Cross-check with `OpenTargets_target_disease_evidence` for additional genetic evidence
Evidence 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.
### Step 2: Gene Set to Pathway Enrichment
1. Collect prioritized gene list from Step 1
2. Run `ReactomeAnalysis_pathway_enrichment` and `STRING_functional_enrichment`
3. Map each gene to KEGG pathways via `KEGG_get_gene_pathways`
4. Identify pathways appearing across multiple databases (convergence = stronger evidence)
5. For metabolic diseases, add tissue-specific network context via `humanbase_ppi_analysis` (all 5 params required: `gene_list`, `tissue`, `max_node`, `interaction`, `string_mode`)
6. Rank pathways by enrichment FDR x number of GWAS genes x biological plausibility
### Step 3: Pathway to Drug Target
1. From enriched pathways, extract all member genes via `Reactome_get_participants` and `KEGG_get_pathway_genes`
2. Assess druggability via `DGIdb_get_gene_druggability`
3. Look up existing drugs via `OpenTargets_get_associated_drugs_by_target_ensemblID`
4. Cross-reference pathway genes with GWAS genes: overlap = top candidate
5. Classify each candidate: repurposing opportunity / novel target / undruggable (for now)
Final 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).
---
## Key Parameter Gotchas
- `gwas_Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.