tooluniverse-precision-oncology

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-precision-oncology
0 commentsdiscussion
summary

Provide actionable treatment recommendations for cancer patients based on their molecular profile using CIViC, ClinVar, OpenTargets, ClinicalTrials.gov, and structure-based analysis.

skill.md

Precision Oncology Treatment Advisor

Provide actionable treatment recommendations for cancer patients based on their molecular profile using CIViC, ClinVar, OpenTargets, ClinicalTrials.gov, and structure-based analysis.

Domain Reasoning

Treatment selection follows a strict evidence hierarchy: FDA-approved for this specific mutation in this cancer type ranks highest, followed by approval for this mutation in any cancer (tumor-agnostic), then active clinical trials, and finally off-label use. Skipping this hierarchy to recommend off-label therapies when an approved option exists is a clinical error. Always check current NCCN guidelines and recent literature, as approvals change rapidly — a drug that was investigational last year may now be first-line.

When looking up treatment for a specific mutation, search CIViC and OncoKB FIRST, not PubMed. These databases have curated evidence levels. PubMed is for when curated databases don't have the answer.

Treatment Selection Reasoning

Biomarker-to-drug logic — When a biomarker is identified, the first-line targeted therapy follows established mappings. Always verify current approval status via OncoKB/CIViC, but use this as a starting framework:

  • NSCLC: EGFR exon 19 del / L858R → osimertinib (1L); ALK fusion → alectinib/lorlatinib; ROS1 fusion → crizotinib/entrectinib; KRAS G12C → sotorasib/adagrasib; MET exon 14 skip → capmatinib/tepotinib; RET fusion → selpercatinib; BRAF V600E → dabrafenib+trametinib; NTRK fusion → larotrectinib/entrectinib (tumor-agnostic)
  • Breast: HER2+ → trastuzumab+pertuzumab (1L), T-DXd (2L); HR+/HER2- → CDK4/6i (palbociclib/ribociclib) + AI; BRCA1/2 mut → olaparib/talazoparib; PIK3CA mut → alpelisib+fulvestrant
  • Colorectal: BRAF V600E → encorafenib+cetuximab; MSI-H/dMMR → pembrolizumab (tumor-agnostic); KRAS/NRAS wild-type → cetuximab/panitumumab (anti-EGFR)
  • Melanoma: BRAF V600E/K → dabrafenib+trametinib or encorafenib+binimetinib; wild-type → immunotherapy (nivolumab+ipilimumab)
  • Tumor-agnostic: MSI-H/dMMR → pembrolizumab; NTRK fusion → larotrectinib; TMB-H (>=10 mut/Mb) → pembrolizumab; RET fusion → selpercatinib

Resistance mechanism reasoning — When a patient progresses on targeted therapy, distinguish primary resistance (never responded — check if the mutation was truly the driver, or if co-mutations like TP53/RB1 abrogate response) from acquired resistance (responded then progressed — on-target mutations or bypass activation). Common patterns:

  • EGFR TKIs: 1st/2nd-gen resistance → T790M (50-60%); osimertinib resistance → C797S (10-25%), MET amp (15-20%), HER2 amp, histologic transformation (SCLC ~5%)
  • ALK TKIs: crizotinib resistance → ALK secondary mutations (L1196M, G1269A); alectinib resistance → G1202R (solvent front); lorlatinib resistance → compound mutations
  • BRAF inhibitors: MAPK reactivation (MEK mutations, BRAF amplification, NRAS mutations), PI3K/AKT bypass
  • Anti-HER2: HER2 truncation (p95HER2), PIK3CA activation, HER3 upregulation
  • Immunotherapy (anti-PD1): B2M loss (MHC-I loss), JAK1/2 loss-of-function (IFN-gamma signaling escape), WNT/beta-catenin activation (T-cell exclusion) For resistance workup: query civic_search_evidence_items with the drug name + "resistance", then PubMed_search_articles for recent mechanisms.

LOOK UP DON'T GUESS

  • FDA approval status for a mutation-drug pair: query OncoKB_annotate_variant and civic_search_variants; never assume approval status from memory.
  • Active clinical trials: search search_clinical_trials with the specific condition and mutation; do not cite trials from memory.
  • Resistance mechanisms for specific drugs: query civic_search_evidence_items and PubMed_search_articles; do not assume resistance pathways.
  • Variant frequency in TCGA: retrieve from GDC_get_mutation_frequency or cBioPortal_get_mutations; do not estimate prevalence.

KEY PRINCIPLES:

  1. Report-first - Create report file FIRST, update progressively
  2. Evidence-graded - Every recommendation has evidence level
  3. Actionable output - Prioritized treatment options, not data dumps
  4. Clinical focus - Answer "what should we do?" not "what exists?"
  5. English-first queries - Always use English terms in tool calls (mutations, drug names, cancer types), even if the user writes in another language. Only try original-language terms as a fallback. Respond in the user's language

When to Use

  • "Patient has [cancer] with [mutation] - what treatments?"
  • "What are options for EGFR-mutant lung cancer?"
  • "Patient failed [drug], what's next?"
  • "Clinical trials for KRAS G12C?"
  • "Why isn't [drug] working anymore?"

Phase 0: Tool Verification

Tool WRONG CORRECT
civic_get_variant variant_name variant_id (numeric, e.g., 4170)
civic_get_evidence_item variant_id id (numeric)
OpenTargets_* ensemblID ensemblId (camelCase)
search_clinical_trials disease condition

Workflow Overview

Input: Cancer type + Molecular profile (mutations, fusions, amplifications)

Phase 1: Profile Validation -> Resolve gene IDs (Ensembl, UniProt, ChEMBL)
Phase 2: Variant Interpretation -> CIViC, ClinVar, COSMIC, GDC/TCGA, DepMap, OncoKB, cBioPortal, HPA
Phase 2.5: Tumor Expression -> CELLxGENE cell-type expression, ChIPAtlas regulatory context
Phase 3: Treatment Options -> OpenTargets + DailyMed (approved), ChEMBL (off-label)
Phase 3.5: Pathway & Network -> KEGG/Reactome pathways, IntAct interactions
Phase 4: Resistance Analysis -> CIViC + PubMed + NvidiaNIM structure analysis
Phase 5: Clinical Trials -> ClinicalTrials.gov search + eligibility
Phase 5.5: Literature -> PubMed, BioRxiv/MedRxiv preprints, OpenAlex citations
Phase 6: Report Synthesis -> Executive summary + prioritized recommendations

Key Tools by Phase

Phase 1: Profile Validation

  • MyGene_query_genes - Resolve gene to Ensembl ID
  • UniProt_search - Get UniProt accession
  • ChEMBL_search_targets - Get ChEMBL target ID

Phase 2: Variant Interpretation

  • civic_search_variants / civic_get_variant - CIViC evidence
  • COSMIC_get_mutations_by_gene / COSMIC_search_mutations - Somatic mutations
  • GDC_get_mutation_frequency / GDC_get_ssm_by_gene - TCGA patient data
  • GDC_get_gene_expression / GDC_get_cnv_data - Expression and CNV
  • GDC_get_survival - Kaplan-Meier survival data by project and optional gene mutation filter
  • GDC_get_clinical_data - TCGA clinical metadata (stage, vital status, treatment, demographics)
  • Progenetix_cnv_search - Copy number variation biosamples by genomic region and cancer type (NCIt code)
  • DepMap_get_gene_dependencies / PharmacoDB_get_experiments - Target essentiality
  • OncoKB_annotate_variant / OncoKB_get_gene_info - Actionability
  • cBioPortal_get_mutations / cBioPortal_get_cancer_studies - Cross-study data
  • HPA_search_genes_by_query / HPA_get_comparative_expression_by_gene_and_cellline - Expression

Phase 2.5: Tumor Expression

  • CELLxGENE_get_expression_data / CELLxGENE_get_cell_metadata - Cell-type expression

Phase 3: Treatment Options

  • OpenTargets_get_associated_drugs_by_target_ensemblID - Approved drugs (param: ensemblId, camelCase)
  • DGIdb_get_drug_gene_interactions - Drug-gene interactions (param: genes as array, e.g., ["EGFR"]). Comprehensive; covers inhibitors, antibodies, and investigational agents.
  • DailyMed_search_spls - FDA label details
  • ChEMBL_get_drug_mechanisms - Drug mechanism

Phase 3.5: Pathway & Network

  • kegg_find_genes / kegg_get_gene_info - KEGG pathways
  • reactome_disease_target_score - Reactome disease relevance
  • intact_get_interaction_network - Protein interactions

Phase 4: Resistance Analysis

  • civic_search_evidence_items - Search by known resistance mutations individually (e.g., molecular_profile="EGFR C797S", molecular_profile="MET Amplification"). The significance field in results indicates Resistance/Sensitivity — filter on it after retrieval.
  • PubMed_search_articles - Resistance literature (e.g., "osimertinib resistance C797S combination therapy")
  • alphafold_get_prediction / get_diffdock_info - Structure-based analysis (AlphaFold for structure, DiffDock for docking)

Phase 5: Clinical Trials

  • search_clinical_trials - Find trials (param: condition, NOT disease)
  • get_clinical_trial_eligibility_criteria - Eligibility details

Phase 5.5: Safety & Pharmacogenomics

  • FAERS_search_adverse_event_reports - Real-world adverse events (param: medicinalproduct). Check for serious AEs, death rates, common toxicities.
  • FAERS_count_death_related_by_drug - Mortality signal for a drug
  • FDA_get_warnings_and_cautions_by_drug_name - FDA label safety info
  • CPIC_list_guidelines - Check for relevant PGx guidelines (e.g., DPYD for fluoropyrimidines in chemo regimens, UGT1A1 for irinotecan). No CPIC guidelines exist for EGFR TKIs.
  • fda_pharmacogenomic_biomarkers - FDA-labeled PGx biomarkers for the drug

OncoKB demo mode: Without ONCOKB_API_TOKEN env var, OncoKB only covers BRAF, TP53, ROS1. For other genes (EGFR, KRAS, ALK, etc.), set the API key or use CIViC as the primary evidence source.

Phase 6: Literature

  • PubMed_search_articles - Published evidence (use limit, mindate, maxdate for date filtering)
  • BioRxiv_list_recent_preprints / MedRxiv_get_preprint - Preprints (flag as NOT peer-reviewed)
  • openalex_search_works - Citation analysis

Cross-Skill References

For CYP interaction with cancer drugs, run: python3 skills/tooluniverse-drug-drug-interaction/scripts/pharmacology_ref.py --type cyp_substrate --drug drugname


References

how to use tooluniverse-precision-oncology

How to use tooluniverse-precision-oncology 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-precision-oncology
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-precision-oncology

The skills CLI fetches tooluniverse-precision-oncology 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-precision-oncology

Reload or restart Cursor to activate tooluniverse-precision-oncology. Access the skill through slash commands (e.g., /tooluniverse-precision-oncology) 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.741 reviews
  • Shikha Mishra· Dec 20, 2024

    tooluniverse-precision-oncology is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Chen Abbas· Dec 20, 2024

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

  • Henry Jackson· Dec 16, 2024

    Useful defaults in tooluniverse-precision-oncology — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Henry White· Dec 8, 2024

    tooluniverse-precision-oncology reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Emma Gonzalez· Dec 4, 2024

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

  • Chen Agarwal· Nov 27, 2024

    Registry listing for tooluniverse-precision-oncology matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Yash Thakker· Nov 11, 2024

    Useful defaults in tooluniverse-precision-oncology — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Henry Sanchez· Nov 7, 2024

    tooluniverse-precision-oncology is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Luis Mehta· Oct 26, 2024

    tooluniverse-precision-oncology reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Charlotte Haddad· Oct 18, 2024

    Useful defaults in tooluniverse-precision-oncology — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 41

1 / 5