skills/tooluniverse-mendelian-randomization/SKILL.md
Mendelian randomization (MR) causal inference — does an exposure, risk factor, or biomarker CAUSALLY affect a disease/outcome, using genetic variants as instrumental variables (IEU OpenGWAS / EpiGraphDB MR-EvE). Use this whenever the user asks if X causes Y, whether an observational association is actually causal or just correlation, if a biomarker/trait is a causal risk factor, wants to triangulate epidemiology against genetic evidence, or mentions Mendelian randomization, instrumental-variable analysis, two-sample MR, or genetic causal evidence — even if they never say "MR" (e.g. "is LDL cholesterol actually causal for heart disease?", "does BMI cause type 2 diabetes or just correlate?", "is CRP a causal driver of stroke?"). Covers trait-label resolution, MR effect direction/magnitude, instrument quality (MOE score), method agreement (IVW vs MR-Egger vs weighted median), bidirectional MR for reverse causation, and distinguishing causation from genetic correlation. Not for plain GWAS association lookups (use the GWAS skills) or fitting your own instruments from raw summary statistics.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-mendelian-randomizationInstall 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.
MR estimates the CAUSAL effect of an exposure on an outcome using genetic variants as instrumental variables. Because alleles are randomized at conception, MR is largely robust to the confounding and reverse causation that bias observational associations. It is not a free lunch: the causal claim rests on three assumptions, and violating them (especially horizontal pleiotropy) silently biases the estimate.
LOOK UP, DON'T GUESS: never assert a causal MR estimate from memory. Genetic-instrument results are updated as new GWAS are published — always retrieve current evidence with EpiGraphDB_get_mendelian_randomization. Do not invent beta/p-values.
Correlation ≠ causation, and genetic correlation ≠ causation. A high genetic correlation (rg) means two traits share heritability — it does NOT establish a causal direction. Only MR (with valid instruments) speaks to causality. Report them as different kinds of evidence.
| Assumption | Statement | How it fails | Check | |---|---|---|---| | Relevance | Instrument is robustly associated with the exposure | Weak instruments (low F-stat) → bias toward the confounded observational estimate | MOE score; instruments selected at GWAS significance | | Independence | Instrument shares no common cause with the outcome | Population stratification, assortative mating | Ancestry-matched GWAS; report population | | Exclusion restriction | Instrument affects the outcome ONLY through the exposure | Horizontal pleiotropy — the variant influences the outcome via another path | MR-Egger intercept ≈ 0; agreement across methods |
If you cannot speak to these, your causal claim is provisional. Say so.
This skill wraps the IEU OpenGWAS / EpiGraphDB MR-EvE ("MR Everything-vs-Everything") resource: a large matrix of pre-computed two-sample MR results between GWAS traits. It does not run a bespoke two-sample MR from raw summary statistics with your own instrument set — see Limitations.
| Tool | Purpose |
|---|---|
| EpiGraphDB_search_opengwas | Resolve a free-text trait to exact OpenGWAS study IDs + labels (DO THIS FIRST) |
| EpiGraphDB_get_mendelian_randomization | Pre-computed MR estimate(s) for an exposure→outcome trait pair (curated pairs; start here) |
| OpenGWAS_get_mr_instruments | Custom two-sample MR: fetch the exposure's clumped instruments + their harmonized outcome effects for any GWAS pair (needs a free OPENGWAS_JWT). Use when the pair isn't in MR-EvE |
| EpiGraphDB_get_genetic_correlations | rg between a trait and others (shared etiology, NOT causation). Sparse — see Step 4 caveat |
| EpiGraphDB_get_drugs_for_trait | Drugs targeting genes associated with a risk-factor trait (causal-target follow-up) |
| gwas_search_associations | GWAS Catalog associations, to inspect the instruments behind a trait |
EpiGraphDB matches GWAS trait labels exactly and case-sensitively. Always resolve free text first:
EpiGraphDB_search_opengwas {"query": "coronary heart disease"}
# → returns ids like 'ieu-a-7' and the exact label 'Coronary heart disease'
Use the returned exact label (or a sentence-case form) in the MR call. The MR tool now retries sentence-case variants and returns a metadata.note when it falls back or finds nothing — read that note; an empty mr_results with a note means "labels didn't match", NOT "no causal effect".
EpiGraphDB_get_mendelian_randomization {
"exposure_trait": "LDL cholesterol",
"outcome_trait": "Coronary heart disease",
"pval_threshold": 1e-5
}
Each row carries beta (causal effect estimate), se, pval, method, moescore, and the exposure/outcome IDs.
Direction, magnitude, instrument quality, and method agreement.
EpiGraphDB_get_genetic_correlations on the exposure. ⚠️ The /genetic-cor graph is sparse: it stores only strong edges (|rg| > 0.8), matches exact, case-sensitive labels distinct from OpenGWAS search labels, and ignores the pval_threshold argument. Common traits (e.g. 'Body mass index') return empty — that is a graph gap, not "no shared genetics." Read metadata.note; if empty, do NOT conclude absence — fall back to bidirectional MR. When it does return, high rg + significant MR = causal; high rg + null MR = shared etiology without a detectable causal path.EpiGraphDB_get_drugs_for_trait surfaces drugs whose target genes drive a causal risk factor — a genetics-anchored repurposing hypothesis.
beta)| Observation | Meaning |
|---|---|
| beta > 0, pval significant | Higher exposure causally increases the outcome (on the GWAS scale — often log-odds for a binary outcome) |
| beta < 0, pval significant | Higher exposure causally decreases the outcome |
| pval not significant | No detectable causal effect at the available instrument strength — absence of evidence, not evidence of absence |
| Effect on a binary outcome | beta is typically a log-odds-ratio; report exp(beta) as an odds ratio per SD/unit of exposure |
moescore, "Mixture of Experts")| MOE | Confidence | |---|---| | > 0.9 | High-quality instrument selection — trust the estimate most | | 0.6–0.9 | Moderate — corroborate with another exposure GWAS or method | | < 0.6 | Weak — treat as hypothesis-generating only |
method)| Method | Note | |---|---| | IVW (inverse-variance weighted) | Primary estimate; assumes no pleiotropy | | MR-Egger | Allows directional pleiotropy; intercept ≠ 0 flags pleiotropy; lower power | | Weighted median | Valid if ≥50% of instrument weight is from valid variants | | Disagreement across methods | A red flag for pleiotropy — downgrade confidence |
EpiGraphDB_get_mendelian_randomization returns pre-computed MR-EvE estimates for curated trait pairs — fast, but limited to pairs IEU already ran. For a pair that isn't covered, or for custom instruments (your own p-value/clumping thresholds), use OpenGWAS_get_mr_instruments (needs a free OPENGWAS_JWT) to assemble harmonized exposure+outcome SNP data, then compute the IVW/MR-Egger estimate yourself (e.g. IVW = Σ(βx·βy/σy²)/Σ(βx²/σy²)) or hand the mr_input to the TwoSampleMR R package. Advanced sensitivity analyses (MR-PRESSO, Steiger, leave-one-out) still need TwoSampleMR.OpenGWAS_get_mr_instruments; review or drop ambiguous ones before trusting the estimate.Causal question: Does [exposure] affect [outcome]? MR estimate: beta = X (se Y, p = Z), method IVW, MOE score → [direction + magnitude, OR if binary]. Triangulation: bidirectional MR [reverse effect?]; genetic correlation rg = [value]; method agreement [yes/no]. Assumptions/caveats: instrument quality [MOE], pleiotropy [Egger intercept / method agreement], ancestry [population]. Verdict: [supported / not supported / inconclusive] causal effect, with the above caveats.
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.