plugin/skills/tooluniverse-gwas-study-explorer/SKILL.md
Compare GWAS studies, perform meta-analyses across cohorts, and assess signal replication. Uses GWAS Catalog metadata, study-level statistics, and cross-cohort comparison. Use for evaluating GWAS reproducibility for a trait, meta-analysis sample size and effect-size aggregation, and detecting study heterogeneity (population, design, ancestry).
npx skillsauth add mims-harvard/tooluniverse tooluniverse-gwas-study-explorerInstall 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.
Compare GWAS studies, perform meta-analyses, and assess replication across cohorts
The GWAS Study Deep Dive & Meta-Analysis skill enables comprehensive comparison of genome-wide association studies (GWAS) for the same trait, meta-analysis of genetic loci across studies, and systematic assessment of replication and study quality. It integrates data from the NHGRI-EBI GWAS Catalog and Open Targets Genetics to provide a complete picture of the genetic architecture of complex traits.
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 comparing GWAS studies for the same trait, ask: do they replicate? The same lead SNPs appearing in independent studies is strong evidence of a true association. Different lead SNPs at the same locus may reflect LD differences between populations — they may tag the same causal variant. Different loci entirely may reflect different study designs, phenotype definitions, or population ancestry. Before concluding that a finding failed to replicate, check whether the SNP was even genotyped or imputed in the replication cohort.
LOOK UP DON'T GUESS: effect sizes, p-values, allele frequencies, and LD structure for specific loci. Do not assume a SNP present in one study is present in another — use gwas_get_associations_for_snp to retrieve cross-study data. Do not infer LD blocks from genomic proximity; use credible sets from Open Targets for fine-mapping results.
Scenario: "I want to understand all available GWAS data for type 2 diabetes"
Workflow:
Outcome: Complete landscape of T2D genetics with replicated findings and population-specific signals
Scenario: "Is the TCF7L2 association with T2D consistent across all studies?"
Workflow:
Outcome: Quantitative assessment of effect size consistency with heterogeneity interpretation
Honesty rule (important): A real inverse-variance meta-analysis needs each study's beta + 95% CI.
python_implementation.pyparses these from the GWAS Catalogbeta/or_value+rangefields and only then pools effect sizes and computes Cochran's-Q I². When the matched associations don't report usable effect sizes (common), it returnsmethod="descriptive",combined_beta=None,heterogeneity_i2=None, andcombined_p_value= the smallest reported p (not a pooled p) — do NOT present a descriptive result as a formal meta-analysis or invent an I².
Scenario: "Which findings from the discovery cohort replicated in the independent sample?"
Workflow:
Outcome: Systematic replication report with success rates and failed findings
Scenario: "Are T2D loci consistent across European and East Asian populations?"
Workflow:
Outcome: Ancestry-specific genetic architecture with transferability assessment
This skill implements standard GWAS meta-analysis methods:
Fixed-Effects Model:
Random-Effects Model (recommended when I² > 50%):
Heterogeneity Assessment:
The I² statistic measures the percentage of variance due to between-study heterogeneity:
I² = [(Q - df) / Q] × 100%
where Q = Cochran's Q statistic
df = degrees of freedom (n_studies - 1)
Interpretation Guidelines:
Common reasons for high I²:
Recommendations:
The skill evaluates studies based on:
1. Sample Size:
2. Ancestry Diversity:
3. Data Availability:
4. Genotyping Quality:
5. Statistical Rigor:
Tier 1 (High Quality):
Tier 2 (Moderate Quality):
Tier 3 (Limited):
❌ Don't:
✅ Do:
When I² > 75%:
When Studies Conflict:
gwas_search_studies: Find studies by traitgwas_get_study_by_id: Get detailed study metadatagwas_get_associations_for_study: Retrieve study associationsgwas_get_associations_for_snp: Get SNP associations across studiesgwas_search_associations: Search associations by traitOpenTargets_search_gwas_studies_by_disease: Disease-based study searchOpenTargets_get_gwas_study: Detailed study information with LD populationsOpenTargets_get_variant_credible_sets: Fine-mapped loci for variantOpenTargets_get_study_credible_sets: All credible sets for studyOpenTargets_get_variant_info: Variant annotation and allele frequenciesCredible Set: Set of variants likely to contain the causal variant (from fine-mapping)
L2G (Locus-to-Gene): Score predicting which gene is affected by a GWAS locus License: Open source (MIT)
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.