tooluniverse-gwas-study-explorer▌
mims-harvard/tooluniverse · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Compare GWAS studies, perform meta-analyses, and assess replication across cohorts
GWAS Study Deep Dive & Meta-Analysis
Compare GWAS studies, perform meta-analyses, and assess replication across cohorts
Overview
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.
Key Capabilities
- Study Comparison: Compare all GWAS studies for a trait, assessing sample sizes, ancestries, and platforms
- Meta-Analysis: Aggregate effect sizes across studies and calculate heterogeneity statistics
- Replication Assessment: Identify replicated vs novel findings across discovery and replication cohorts
- Quality Evaluation: Assess statistical power, ancestry diversity, and data availability
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.
Domain Reasoning: Comparing Studies for the Same Trait
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.
Use Cases
1. Comprehensive Trait Analysis
Scenario: "I want to understand all available GWAS data for type 2 diabetes"
Workflow:
- Search for all T2D studies in GWAS Catalog
- Filter by sample size and ancestry
- Extract top associations from each study
- Identify consistently replicated loci
- Assess ancestry-specific effects
Outcome: Complete landscape of T2D genetics with replicated findings and population-specific signals
2. Locus-Specific Meta-Analysis
Scenario: "Is the TCF7L2 association with T2D consistent across all studies?"
Workflow:
- Retrieve all TCF7L2 (rs7903146) associations for T2D
- Calculate combined effect size and p-value
- Assess heterogeneity (I² statistic)
- Generate forest plot data
- Interpret heterogeneity level
Outcome: Quantitative assessment of effect size consistency with heterogeneity interpretation
3. Replication Analysis
Scenario: "Which findings from the discovery cohort replicated in the independent sample?"
Workflow:
- Get top hits from discovery study
- Check for presence and significance in replication study
- Assess direction consistency
- Calculate replication rate
- Identify novel vs failed replication
Outcome: Systematic replication report with success rates and failed findings
4. Multi-Ancestry Comparison
Scenario: "Are T2D loci consistent across European and East Asian populations?"
Workflow:
- Filter studies by ancestry
- Compare top associations between populations
- Identify shared vs population-specific loci
- Assess allele frequency differences
- Evaluate transferability of genetic risk scores
Outcome: Ancestry-specific genetic architecture with transferability assessment
Statistical Methods
Meta-Analysis Approach
This skill implements standard GWAS meta-analysis methods:
Fixed-Effects Model:
- Used when heterogeneity is low (I² < 25%)
- Weights studies by inverse variance
- Assumes true effect size is the same across studies
Random-Effects Model (recommended when I² > 50%):
- Accounts for between-study variation
- More conservative than fixed-effects
- Better for diverse ancestries or methodologies
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:
- I² < 25%: Low heterogeneity → fixed-effects appropriate
- I² = 25-50%: Moderate heterogeneity → investigate sources
- I² = 50-75%: Substantial heterogeneity → random-effects preferred
- I² > 75%: Considerable heterogeneity → meta-analysis may not be appropriate
Sources of Heterogeneity
Common reasons for high I²:
- Ancestry differences: Different allele frequencies and LD structure
- Phenotype heterogeneity: Trait definition varies across studies
- Platform differences: Imputation quality and coverage
- Winner's curse: Discovery studies overestimate effect sizes
- Cohort characteristics: Age, sex, environmental factors
Recommendations:
- Perform subgroup analysis by ancestry
- Use meta-regression to investigate sources
- Consider excluding outlier studies
- Apply genomic control correction
Study Quality Assessment
Quality Metrics
The skill evaluates studies based on:
1. Sample Size:
- Power to detect associations (80% power requires n > 10,000 for OR=1.2)
- Precision of effect size estimates
- Ability to detect modest effects
2. Ancestry Diversity:
- Single-ancestry vs multi-ancestry
- Population stratification control
- Transferability of findings
3. Data Availability:
- Summary statistics available for meta-analysis
- Individual-level data vs summary-level
- Imputation quality scores
4. Genotyping Quality:
- Platform density and coverage
- Imputation reference panel
- Quality control measures
5. Statistical Rigor:
- Genome-wide significance threshold (p < 5×10⁻⁸)
- Multiple testing correction
- Replication in independent cohort
Quality Tiers
Tier 1 (High Quality):
- n ≥ 50,000
- Summary statistics available
- Multi-ancestry or large single-ancestry
- Imputed to high-quality reference
- Independent replication
Tier 2 (Moderate Quality):
- n ≥ 10,000
- Standard GWAS platform
- Adequate power for common variants
- Some data availability
Tier 3 (Limited):
- n < 10,000
- Limited power
- May miss modest effects
- Use with caution
Best Practices
Before Meta-Analysis
- Check phenotype consistency: Ensure studies measure the same trait
- Verify ancestry overlap: High heterogeneity expected if ancestries differ
- Harmonize alleles: Align effect alleles across studies
- Quality control: Exclude low-quality studies or associations
Interpreting Results
- Genome-wide significance: p < 5×10⁻⁸ (Bonferroni for ~1M independent tests)
- Replication threshold: p < 0.05 in independent cohort
- Direction consistency: Effect should be same direction across studies
- Heterogeneity: I² > 50% suggests caution in interpretation
Common Pitfalls
❌ Don't:
- Meta-analyze without checking heterogeneity
- Ignore ancestry differences
- Over-interpret nominal p-values
- Assume replication failure means false positive
✅ Do:
- Always report I² statistic
- Perform sensitivity analyses
- Consider ancestry-stratified analysis
- Account for winner's curse in discovery studies
Limitations & Caveats
Data Limitations
- Incomplete Overlap: Studies may analyze different SNPs
- Cohort Overlap: Some cohorts participate in multiple studies (inflates significance)
- Publication Bias: Significant findings more likely to be published
- Winner's Curse: Discovery studies overestimate effect sizes
- Imputation Quality: Varies across studies and populations
Statistical Limitations
- Heterogeneity: High I² may preclude meaningful meta-analysis
- Sample Size Differences: Large studies dominate fixed-effects models
- Allele Frequency Differences: Same variant has different effects across ancestries
- Linkage Disequilibrium: Fine-mapping needed to identify causal variants
- Gene-Environment Interactions: Not captured in standard meta-analysis
Interpretation Guidelines
When I² > 75%:
- Meta-analysis results should be interpreted with extreme caution
- Investigate sources of heterogeneity systematically
- Consider ancestry-specific or subgroup analyses
- Descriptive comparison may be more appropriate than meta-analysis
When Studies Conflict:
- Check for methodological differences
- Verify phenotype definitions match
- Investigate population stratification
- Consider conditional analysis
Tools Used
GWAS Catalog API
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 trait
Open Targets Genetics GraphQL API
OpenTargets_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 frequencies
Glossary
Credible 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)
How to use tooluniverse-gwas-study-explorer 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-gwas-study-explorer
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches tooluniverse-gwas-study-explorer 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-gwas-study-explorer. Access the skill through slash commands (e.g., /tooluniverse-gwas-study-explorer) 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.7★★★★★39 reviews- ★★★★★Amina Dixit· Dec 28, 2024
Solid pick for teams standardizing on skills: tooluniverse-gwas-study-explorer is focused, and the summary matches what you get after install.
- ★★★★★Ganesh Mohane· Dec 20, 2024
tooluniverse-gwas-study-explorer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Liam Ghosh· Dec 8, 2024
tooluniverse-gwas-study-explorer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kaira Thomas· Dec 8, 2024
Useful defaults in tooluniverse-gwas-study-explorer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ira Farah· Dec 4, 2024
We added tooluniverse-gwas-study-explorer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Amina Jain· Nov 27, 2024
I recommend tooluniverse-gwas-study-explorer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kofi White· Nov 23, 2024
tooluniverse-gwas-study-explorer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yash Thakker· Nov 19, 2024
Solid pick for teams standardizing on skills: tooluniverse-gwas-study-explorer is focused, and the summary matches what you get after install.
- ★★★★★Sakshi Patil· Nov 11, 2024
tooluniverse-gwas-study-explorer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Amina Harris· Oct 18, 2024
Keeps context tight: tooluniverse-gwas-study-explorer is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 39