skills/tooluniverse-structural-variant-analysis/SKILL.md
Structural variant (SV) clinical interpretation: deletions, duplications, inversions, translocations, complex rearrangements. Applies ACMG-adapted criteria with ClinGen HI/TS dosage scores, gnomAD frequencies, and ClinVar evidence. Produces 5-tier classification with explicit per-criterion evidence. Use for clinical genomics SV review, dosage-sensitivity assessment, breakpoint analysis, and CNV pathogenicity calls. Gene-dosage-driven reasoning.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-structural-variant-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Systematic analysis of structural variants (deletions, duplications, inversions, translocations, complex rearrangements) for clinical genomics interpretation using ACMG-adapted criteria.
LOOK UP DON'T GUESS - Always retrieve ClinGen HI/TS scores, gnomAD frequencies, and ClinVar evidence from tools. Do not infer dosage sensitivity from gene function alone.
KEY PRINCIPLES:
Use this skill when users:
Before any tool call, apply this reasoning to frame the analysis:
SV pathogenicity depends on what the SV disrupts. A deletion removing an entire gene is likely pathogenic if the gene is haploinsufficient. A duplication is pathogenic if the gene is dosage-sensitive. An inversion is pathogenic only if it disrupts a coding region or regulatory element at the breakpoint.
Work through these questions in order:
1. What type is the SV, and what disruption mechanism does it cause?
2. Is the disrupted gene dosage-sensitive?
3. Does the population frequency contextualize the SV?
=1% frequency in gnomAD SV = BA1 (likely benign unless phenotype is extreme)
4. Is there clinical precedent?
Document this reasoning before computing the final score.
Phase 1: SV IDENTITY & CLASSIFICATION
Normalize coordinates (hg19/hg38), determine type (DEL/DUP/INV/TRA/CPX),
calculate size, assess breakpoint precision
Phase 2: GENE CONTENT ANALYSIS
Identify fully contained genes, partially disrupted genes (breakpoint within),
flanking genes (within 1 Mb), annotate function and disease associations
Phase 3: DOSAGE SENSITIVITY ASSESSMENT
ClinGen HI/TS scores, pLI scores, OMIM inheritance patterns,
gene-disease validity levels
Phase 4: POPULATION FREQUENCY CONTEXT
gnomAD SV database, ClinVar known SVs, DECIPHER patient cases,
reciprocal overlap calculation (>=70% = same SV)
Phase 5: PATHOGENICITY SCORING
Quantitative 0-10 scale: gene content (40%), dosage sensitivity (30%),
population frequency (20%), clinical evidence (10%)
Phase 6: LITERATURE & CLINICAL EVIDENCE
PubMed searches, DECIPHER cohort analysis, functional evidence
Phase 7: ACMG-ADAPTED CLASSIFICATION
Apply SV-specific evidence codes, calculate final classification,
generate clinical recommendations
Goal: Standardize SV notation and classify type.
Capture: chromosome(s), coordinates (start/end in hg19/hg38), SV size, SV type (DEL/DUP/INV/TRA/CPX), breakpoint precision, inheritance pattern (de novo/inherited/unknown).
For SV type definitions, scoring tables, and ACMG code details, see CLASSIFICATION_GUIDE.md.
Goal: Annotate all genes affected by the SV.
Tools:
ensembl_lookup_gene - gene structure, coordinates, exonsNCBIGene_search - official symbol, aliases, descriptionGO_get_term_details - biological process, molecular functionOMIM_search, OMIM_get_entry - disease associations, inheritanceDisGeNET_search_gene - gene-disease association scoresClassify genes as: fully contained (entire gene in SV), partially disrupted (breakpoint within gene), or flanking (within 1 Mb of breakpoints).
For implementation pseudocode, see ANALYSIS_PROCEDURES.md Phase 2.
Goal: Determine if affected genes are dosage-sensitive.
Tools:
ClinGen_search_dosage_sensitivity - HI/TS scores (0-3, gold standard)ClinGen_search_gene_validity - gene-disease validity levelgnomad_search_variants - pLI scores for LoF intoleranceOMIM_get_entry - inheritance pattern (AD suggests dosage sensitivity)Interpret scores using the reasoning above. ClinGen HI/TS score 3 = definitive; score 2 = likely; score 1 = little evidence; score 0 = no evidence. Do not equate AD inheritance with haploinsufficiency without ClinGen support.
Goal: Determine if SV is common (likely benign) or rare (supports pathogenicity).
Tools:
gnomad_search_variants - population SV frequenciesClinVar_search_variants - known pathogenic/benign SVsClinGen_search_dosage_sensitivity - patient SVs with phenotypesUse >=70% reciprocal overlap to define "same" SV for comparison. A frequency >=1% triggers BA1 unless there is very strong clinical evidence to override.
Goal: Quantitative pathogenicity assessment on 0-10 scale.
Four components weighted: gene content (40%), dosage sensitivity (30%), population frequency (20%), clinical evidence (10%).
Score mapping: 9-10 = Pathogenic, 7-8 = Likely Pathogenic, 4-6 = VUS, 2-3 = Likely Benign, 0-1 = Benign.
For detailed scoring breakdowns and implementation, see CLASSIFICATION_GUIDE.md and ANALYSIS_PROCEDURES.md Phase 5.
Goal: Find case reports, functional studies, and clinical validation.
Tools:
PubMed_search_articles - peer-reviewed literatureEuropePMC_search_articles - additional coverageClinGen_search_dosage_sensitivity - patient case databaseSearch strategies: gene-specific dosage sensitivity papers, SV-specific case reports, phenotype-gene associations. See ANALYSIS_PROCEDURES.md Phase 6.
Goal: Apply ACMG/ClinGen criteria adapted for SVs and generate a final classification with explicit evidence summary.
The LLM knows the ACMG criteria codes and combination rules. Apply them to the evidence gathered in Phases 1-6. Key points to verify with tool data:
For complete evidence code tables and classification algorithm, see CLASSIFICATION_GUIDE.md.
Create report using the template in REPORT_TEMPLATE.md. Name files as:
SV_analysis_[TYPE]_chr[CHR]_[START]_[END]_[GENES].md
ClinGen_search_dosage_sensitivity - HI/TS scores (required for all deletions/duplications)ClinGen_search_gene_validity - gene-disease validity (required)ClinVar_search_variants - known pathogenic/benign SVs (required)ensembl_lookup_gene - gene coordinates, structure (required)OMIM_search, OMIM_get_entry - gene-disease associations (required)gnomad_search_variants - population frequency and pLI (required)DisGeNET_search_gene - additional disease associations (recommended)PubMed_search_articles - literature evidence (recommended)GO_get_term_details - gene function (supporting)tooluniverse-variant-interpretationUse this skill for structural variants >=50 bp requiring dosage sensitivity assessment and ACMG-adapted classification.
EXAMPLES.md - Sample SV interpretations with worked examplesCLASSIFICATION_GUIDE.md - ACMG criteria, scoring system, evidence codes, special scenarios, clinical recommendationsREPORT_TEMPLATE.md - Full report template with section structure and file namingANALYSIS_PROCEDURES.md - Detailed implementation pseudocode for each phasetooluniverse-variant-interpretation - For SNVs and small indelstools
Generate the success criteria for a task or question, then review work against them. Given a task, goal, or open-ended question, decompose it into scenarios, evaluation perspectives, and fine-grained weighted YES/NO criteria using the Recursive Expansion Tree (RET) method; if work is supplied, score it criterion-by-criterion and surface what is missing or could be better. Use when asked to self-review or check your own work, judge whether a task is done well or completely, build a definition-of-done or completeness checklist, create an evaluation rubric or grading criteria, score or grade answers to a question, set up an LLM-as-judge rubric, or when the user mentions self-review, completeness check, success criteria, evaluation criteria, scoring rubric, Qworld, or the RET algorithm.
tools
Find the real protein target(s) of a peptide from its sequence — peptide target deorphanization / off-target identification, for ANY target class (GPCR, ion channel, protease, cytokine/growth-factor receptor, enzyme, integrin), not only GPCRs. Use when a peptide has a phenotype but does not bind its hypothesized target, when a peptide binds a target in one species or assay but not another, or to screen candidate targets for an orphan peptide. A target-class router steers a multi-route keyless pipeline (PROSITE/ELM motif, BLAST homology, HGNC/InterPro/GPCRdb/GtoPdb target-family enumeration, OpenTargets phenotype anchor, EnsemblCompara/Alliance cross-species reconciliation) plus optional NVIDIA-NIM co-folding (Boltz2, AlphaFold2-Multimer, OpenFold3) for structural confirmation.
tools
Install or update ToolUniverse in Claude Science — create the conda env, install the tooluniverse pip package, and (re)build the tooluniverse-research skill by fetching the current workflow library from GitHub. Use for first-time setup, upgrading the ToolUniverse version, refreshing the bundled workflows after an upstream release, or reinstalling on a new machine.
tools
Install, set up, verify, update, pin, uninstall, or troubleshoot the ToolUniverse plugin on OpenAI Codex. ALWAYS consult this skill for any of those — don't answer from memory, because the exact marketplace name (mims-harvard/ToolUniverse), the "codex plugin marketplace add" then "codex plugin add -m tooluniverse" flow, Codex's startup auto-upgrade behavior, the uvx tooluniverse MCP server, and the API-key env vars are easy to get wrong. Use it whenever someone wants to get ToolUniverse (or "the 1000+ scientific tools" / "the harvard tools") working on Codex, says the Codex plugin or its tools/skills won't load, hits a uvx or MCP-server startup error, asks how Codex updates it, wants to pin or remove it, or finds it running an old tool version — even if they never say the word "plugin". Not for the Claude Code plugin (use tooluniverse-claude-code-plugin), for running research with the tools, or for authoring new tools or skills.