tooluniverse-gwas-snp-interpretation

mims-harvard/tooluniverse · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-gwas-snp-interpretation
0 commentsdiscussion
summary

SNP interpretation: a GWAS hit is a REGION, not a single causal variant. The lead SNP may not be causal — it may be in LD with the causal variant. Always check LD structure and functional annotation before concluding a specific SNP is mechanistically responsible. Fine-mapping (SuSiE, FINEMAP credible sets) narrows the causal set but rarely identifies a single variant with certainty. L2G scores integrate eQTL, chromatin interaction, and distance data to predict the causal gene — a lead SNP mappin

skill.md

GWAS SNP Interpretation Skill

SNP interpretation: a GWAS hit is a REGION, not a single causal variant. The lead SNP may not be causal — it may be in LD with the causal variant. Always check LD structure and functional annotation before concluding a specific SNP is mechanistically responsible. Fine-mapping (SuSiE, FINEMAP credible sets) narrows the causal set but rarely identifies a single variant with certainty. L2G scores integrate eQTL, chromatin interaction, and distance data to predict the causal gene — a lead SNP mapping to gene A may actually regulate gene B 500 kb away via a distal enhancer.

LOOK UP DON'T GUESS: never assume a SNP's functional consequence, mapped gene, or population frequency — always call gwas_get_snp_by_id and OpenTargets_get_variant_info to retrieve current annotations.

Overview

Interpret genetic variants (SNPs) from GWAS studies by aggregating evidence from multiple sources to provide comprehensive clinical and biological context.

Use Cases:

  • "Interpret rs7903146" (TCF7L2 diabetes variant)
  • "What diseases is rs429358 associated with?" (APOE Alzheimer's variant)
  • "Clinical significance of rs1801133" (MTHFR variant)
  • "Is rs12913832 in any fine-mapped loci?" (Eye color variant)

What It Does

The skill provides a comprehensive interpretation of SNPs by:

  1. SNP Annotation: Retrieves basic variant information including genomic coordinates, alleles, functional consequence, and mapped genes
  2. Association Discovery: Finds all GWAS trait/disease associations with statistical significance
  3. Fine-Mapping Evidence: Identifies credible sets the variant belongs to (fine-mapped causal loci)
  4. Gene Mapping: Uses Locus-to-Gene (L2G) predictions to identify likely causal genes
  5. Clinical Summary: Aggregates evidence into actionable clinical significance

Workflow

User Input: rs7903146
[1] SNP Lookup
    → Get location, consequence, MAF
    → gwas_get_snp_by_id
[2] Association Search
    → Find all trait/disease associations
    → gwas_get_associations_for_snp
[3] Fine-Mapping (Optional)
    → Get credible set membership
    → OpenTargets_get_variant_credible_sets
[4] Gene Predictions
    → Extract L2G scores for causal genes
    → (embedded in credible sets)
[5] Clinical Summary
    → Aggregate evidence
    → Identify key traits and genes
Output: Comprehensive Interpretation Report

Data Sources

GWAS Catalog (EMBL-EBI)

  • SNP annotations: Functional consequences, mapped genes, population frequencies
  • Associations: P-values, effect sizes, study metadata
  • Coverage: 350,000+ publications, 670,000+ associations

Open Targets Genetics

  • Fine-mapping: Statistical credible sets from SuSiE, FINEMAP methods
  • L2G predictions: Machine learning-based gene prioritization
  • Colocalization: QTL evidence for causal genes
  • Coverage: UK Biobank, FinnGen, and other large cohorts

Input Parameters

Required

  • rs_id (str): dbSNP rs identifier
    • Format: "rs" + number (e.g., "rs7903146")
    • Must be valid rsID in GWAS Catalog

Optional

  • include_credible_sets (bool, default=True): Query fine-mapping data
    • True: Complete interpretation (slower, ~10-30s)
    • False: Fast associations only (~2-5s)
  • p_threshold (float, default=5e-8): Genome-wide significance threshold
  • max_associations (int, default=100): Maximum associations to retrieve

Output Format

Returns SNPInterpretationReport containing:

1. SNP Basic Info

{
    'rs_id': 'rs7903146',
    'chromosome': '10',
    'position': 112998590,
    'ref_allele': 'C',
    'alt_allele': 'T',
    'consequence': 'intron_variant',
    'mapped_genes': ['TCF7L2'],
    'maf': 0.293
}

2. Trait Associations

[
    {
        'trait': 'Type 2 diabetes',
        'p_value': 1.2e-128,
        'beta': '0.28 unit increase',
        'study_id': 'GCST010555',
        'pubmed_id': '33536258',
        'effect_allele': 'T'
    },
    ...
]

3. Credible Sets (Fine-Mapping)

[
    {
        'study_id': 'GCST90476118',
        'trait': 'Renal failure',
        'finemapping_method': 'SuSiE-inf',
        'p_value': 3.5e-42,
        'predicted_genes': [
            {'gene': 'TCF7L2', 'score': 0.863}
        ],
        'region': '10:112950000-113050000'
    },
    ...
]

4. Clinical Significance

Genome-wide significant associations with 100 traits/diseases:
  - Type 2 diabetes
  - Diabetic retinopathy
  - HbA1c levels
  ...

Identified in 20 fine-mapped loci.
Predicted causal genes: TCF7L2

Example Usage

See QUICK_START.md for platform-specific examples.

Tools Used

GWAS Catalog Tools

  1. gwas_get_snp_by_id: Get SNP annotation
  2. gwas_get_associations_for_snp: Get all trait associations

Open Targets Tools

  1. OpenTargets_get_variant_info: Get variant details with population frequencies
  2. OpenTargets_get_variant_credible_sets: Get fine-mapping credible sets with L2G

Interpretation Guide

P-value Significance Levels

  • p < 5e-8: Genome-wide significant (strong evidence)
  • p < 5e-6: Suggestive (moderate evidence)
  • p < 0.05: Nominal (weak evidence)

L2G Score Interpretation

  • > 0.5: High confidence causal gene
  • 0.1-0.5: Moderate confidence
  • < 0.1: Low confidence

Clinical Actionability

  1. High: Multiple genome-wide significant associations + in credible sets + high L2G scores
  2. Moderate: Genome-wide significant associations but limited fine-mapping
  3. Low: Suggestive associations or limited replication

Limitations

  1. Variant ID Conversion: OpenTargets requires chr_pos_ref_alt format, which may need allele lookup
  2. Population Specificity: Associations may vary by ancestry
  3. Effect Sizes: Beta values are study-dependent (different phenotype scales)
  4. Causality: Associations don't prove causation; fine-mapping improves confidence
  5. Currency: Data reflects published GWAS; latest studies may not be included

Best Practices

  1. Use Full Interpretation: Enable include_credible_sets=True for clinical decisions
  2. Check Multiple Variants: Look at other variants in the same locus
  3. Validate Populations: Consider ancestry-specific effect sizes
  4. Review Publications: Check original studies for context
  5. Integrate Evidence: Combine with functional data, eQTLs, pQTLs

Technical Notes

Performance

  • Fast mode (no credible sets): 2-5 seconds
  • Full mode (with credible sets): 10-30 seconds
  • Bottleneck: OpenTargets GraphQL API rate limits

Error Handling

  • Invalid rs_id: Returns error message
  • No associations: Returns empty list with note
  • API failures: Graceful degradation (returns partial results)

Related Skills

  • Gene Function Analysis: Interpret predicted causal genes
  • Disease Ontology Lookup: Understand trait classifications
  • PubMed Literature Search: Find original GWAS publications
  • Variant Effect Prediction: Functional consequence analysis

References

  1. GWAS Catalog: https://www.ebi.ac.uk/gwas/
  2. Open Targets Genetics: https://genetics.opentargets.org/
  3. GWAS Significance Thresholds: Fadista et al. 2016
  4. L2G Method: Mountjoy et al. 2021 (Nature Genetics)

Version

  • Version: 1.0.0
  • Last Updated: 2026-02-13
  • ToolUniverse Version: >= 1.0.0
  • Tools Required: gwas_get_snp_by_id, gwas_get_associations_for_snp, OpenTargets_get_variant_credible_sets
how to use tooluniverse-gwas-snp-interpretation

How to use tooluniverse-gwas-snp-interpretation on Cursor

AI-first code editor with Composer

1

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-snp-interpretation
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-gwas-snp-interpretation

The skills CLI fetches tooluniverse-gwas-snp-interpretation from GitHub repository mims-harvard/tooluniverse and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/tooluniverse-gwas-snp-interpretation

Reload or restart Cursor to activate tooluniverse-gwas-snp-interpretation. Access the skill through slash commands (e.g., /tooluniverse-gwas-snp-interpretation) 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

GET_STARTED →

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.442 reviews
  • Valentina Diallo· Dec 24, 2024

    tooluniverse-gwas-snp-interpretation has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Soo Patel· Dec 12, 2024

    Solid pick for teams standardizing on skills: tooluniverse-gwas-snp-interpretation is focused, and the summary matches what you get after install.

  • Valentina Khan· Nov 15, 2024

    tooluniverse-gwas-snp-interpretation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ishan Wang· Nov 15, 2024

    Keeps context tight: tooluniverse-gwas-snp-interpretation is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Valentina Haddad· Nov 3, 2024

    We added tooluniverse-gwas-snp-interpretation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Valentina Abbas· Nov 3, 2024

    tooluniverse-gwas-snp-interpretation has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Valentina Farah· Oct 22, 2024

    tooluniverse-gwas-snp-interpretation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Olivia Abbas· Oct 22, 2024

    Solid pick for teams standardizing on skills: tooluniverse-gwas-snp-interpretation is focused, and the summary matches what you get after install.

  • Omar Kapoor· Oct 6, 2024

    We added tooluniverse-gwas-snp-interpretation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Soo Reddy· Oct 6, 2024

    tooluniverse-gwas-snp-interpretation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 42

1 / 5