biobankjapan-phewas-skill

Fetch BioBank Japan PheWAS associations for a single variant via rsID or genomic coordinates.

5.3k|765|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/openai/plugins --skill biobankjapan-phewas-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: biobankjapan-phewas-skill
Source: https://github.com/openai/plugins/tree/main/plugins/life-science-research/skills/biobankjapan-phewas-skill
Command: npx skills add https://github.com/openai/plugins --skill biobankjapan-phewas-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) components.

What problem does it solve?

Looking up phenome-wide association study (PheWAS) results for a genetic variant in BioBank Japan requires resolving identifiers across genome builds and querying the pheweb.jp API manually, which is error-prone and slow.

Core Features & Use Cases

  • Flexible Variant Input: Accepts exactly one of rsID, GRCh37, GRCh38, or generic variant strings and resolves them to the canonical GRCh37 query required by BioBank Japan.
  • Ensembl-Based Resolution: Uses Ensembl REST endpoints to map rsIDs and coordinates between GRCh37 and GRCh38 builds, with warnings for allele mismatches.
  • Compact Summaries with Raw Export: Returns truncated association lists by default and optionally saves the full JSON payload to disk via save_raw.
  • Use Case: A researcher investigating rs7903146 can request its BioBank Japan associations and receive a concise markdown summary of the top phenotypes with effect data.

Quick Start

Ask the assistant to fetch BioBank Japan PheWAS associations for rs7903146 with a maximum of 10 results.

Frequently Asked Questions about biobankjapan-phewas-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I look up PheWAS associations for a variant in BioBank Japan?

Provide one variant identifier as JSON on stdin, such as {"rsid":"rs7903146"} or {"grch37":"10:114758349-C-T"}, and the script queries the pheweb.jp API. It returns a JSON summary with association counts, truncated results, and a variant URL.

What variant input formats does the BioBank Japan PheWAS lookup accept?

It accepts exactly one of rsid, grch37, grch38, or variant keys, with coordinates in chrom-pos-ref-alt form using flexible separators. GRCh38 and rsID inputs are resolved to GRCh37 through Ensembl before querying BioBank Japan.

Can I convert GRCh38 coordinates to GRCh37 for BioBank Japan queries?

Yes, the script resolves GRCh38 input by finding the overlapping rsID via the Ensembl overlap endpoint, then looking up its GRCh37 mapping. If resolution fails, it returns an error with code resolution_failed or not_found.

How do I get the full association results instead of truncated output?

Set save_raw to true in the input JSON, optionally with raw_output_path, and the full API payload is written to disk. The response reports raw_output_path so you can inspect the complete data without large chat output.

Why does the variant lookup return a not_found error?

The not_found error occurs when no rsID exists at the given position in the Ensembl overlap endpoint for that build. A 404 from BioBank Japan instead returns ok=true with zero associations and a warning that the variant is absent from the PheWAS API.