Compare GWAS studies, perform meta-analyses, and assess replication across cohorts
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontooluniverse-gwas-study-explorerExecute the skills CLI command in your project's root directory to begin installation:
Fetches tooluniverse-gwas-study-explorer from mims-harvard/tooluniverse and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate tooluniverse-gwas-study-explorer. Access via /tooluniverse-gwas-study-explorer in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
1.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.2K
stars
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
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)
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Solid pick for teams standardizing on skills: tooluniverse-gwas-study-explorer is focused, and the summary matches what you get after install.
tooluniverse-gwas-study-explorer has been reliable in day-to-day use. Documentation quality is above average for community skills.
tooluniverse-gwas-study-explorer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in tooluniverse-gwas-study-explorer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added tooluniverse-gwas-study-explorer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend tooluniverse-gwas-study-explorer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
tooluniverse-gwas-study-explorer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: tooluniverse-gwas-study-explorer is focused, and the summary matches what you get after install.
tooluniverse-gwas-study-explorer reduced setup friction for our internal harness; good balance of opinion and flexibility.
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