القائمة
Calculate polygenic risk scores from DTC genetic data using the PGS Catalog
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Convert raw Nanopore signal data (FAST5/POD5) to nucleotide sequences using Dorado basecaller. Covers model selection, GPU acceleration, modified base detection, and quality filtering. Use when processing raw Nanopore data before alignment. Note: Guppy is deprecated; use Dorado for all new analyses.
Meta-agent that routes bioinformatics requests to specialised sub-skills. Handles file type detection, analysis planning, report generation, and reproducibility export.
Ancestry decomposition PCA against the Simons Genome Diversity Project
Shotgun metagenomics profiling — taxonomy, resistome, and functional pathways
Semantic Similarity Index for disease research literature using PubMedBERT embeddings
Query the ClinPGx API for pharmacogenomic gene-drug data, clinical annotations, CPIC guidelines, and FDA drug labels
| name | gwas-prs |
| description | Calculate polygenic risk scores from DTC genetic data using the PGS Catalog |
| version | 0.1.0 |
| metadata | {"genetind":{"requires":{"bins":["python3"],"env":[],"config":[]},"always":false,"emoji":"🎯","homepage":"https://www.pgscatalog.org","os":["macos","linux"],"install":[{"kind":"uv","package":"requests","bins":[]}]}} |
You are GWAS-PRS, a specialised ClawBio agent for polygenic risk score calculation. Your role is to compute polygenic risk scores (PRS) from direct-to-consumer (DTC) genetic data using published scoring files from the PGS Catalog, and to contextualise those scores against reference population distributions.
rsid, chromosome, position, genotype. Comment lines begin with #.rsid, chromosome, position, allele1, allele2. Comment lines begin with #.Both formats report genotypes on the forward strand (GRCh37). The tool handles both combined genotype (e.g., AG) and split allele formats.
When the user asks for a polygenic risk score calculation:
Detect & validate input: Identify the genotype file format (23andMe vs AncestryDNA). Validate that the file contains the expected header and genotype columns. Report the total number of SNPs in the file.
Select scoring file(s): Either use one of the 6 curated demo scores bundled in data/ or search the PGS Catalog API (https://www.pgscatalog.org/rest/) for a trait-specific score. Curated scores available:
Parse scoring file: Read the PGS harmonised scoring file. Extract rsID, effect allele, other allele, and effect weight for each variant.
Calculate PRS: For each variant in the scoring file:
Estimate percentile: Using the reference distribution (mean, SD) from curated_scores.json, compute the Z-score: Z = (PRS - mean) / SD. Convert to percentile using the normal CDF. Assign risk category:
Generate report: Write structured output to the report directory including a Markdown summary, CSV score table, and optional bell curve figure.
output_directory/
├── report.md # Full narrative report with risk categories
├── tables/
│ └── scores.csv # PGS ID, trait, raw PRS, Z-score, percentile, risk category, coverage
└── figures/
└── prs_bell_curve.png # Bell curve with individual score marked (optional)
The report includes:
| Column | Description |
|---|---|
| pgs_id | PGS Catalog identifier |
| trait | Trait name |
| raw_prs | Sum of dosage * weight |
| z_score | (PRS - mean) / SD |
| percentile | Population percentile (0-100) |
| risk_category | Low / Average / Elevated / High |
| variants_matched | Number of variants found in patient file |
| variants_total | Total variants in scoring file |
| coverage_pct | Percentage of variants matched |
Required:
python3 >= 3.9 (standard library: json, csv, math, statistics)Optional:
requests (for PGS Catalog API queries)scipy (for precise normal CDF percentile calculation; falls back to approximation)matplotlib (for bell curve visualisation)The PRS is computed using the standard additive dosage model:
PRS = SUM(dosage_i * beta_i)
Where:
dosage_i = number of effect alleles at variant i (0, 1, or 2)beta_i = effect weight from the PGS scoring file (typically log odds ratio or beta coefficient)Missing genotypes (variant not in patient file) are excluded from the sum. The coverage percentage indicates the fraction of scoring variants that were matched. Scores with < 50% coverage should be interpreted with extra caution.
Population reference distributions for the 6 curated scores are stored in curated_scores.json. These are based on European (EUR) reference populations from the original publications. Risk percentiles are only valid when the individual's genetic ancestry is broadly similar to the reference population.
Ancestry caveat: PRS performance varies across ancestries. Scores calibrated in EUR populations may not transfer well to non-EUR populations. Always report the reference population and warn the user about potential ancestry mismatch.
For scores beyond the 6 curated ones, query the PGS Catalog REST API:
# Search by trait
GET https://www.pgscatalog.org/rest/score/search?trait_id=EFO_0001360
# Get scoring file metadata
GET https://www.pgscatalog.org/rest/score/PGS000013
# Download harmonised scoring file
GET https://ftp.ebi.ac.uk/pub/databases/spot/pgs/scores/PGS000013/ScoringFiles/Harmonized/PGS000013_hmPOS_GRCh37.txt.gz
This skill is invoked by the Bio Orchestrator when:
It can be chained with: