tooluniverse-immunotherapy-response-prediction▌
mims-harvard/tooluniverse · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Predict patient response to immune checkpoint inhibitors (ICIs) using multi-biomarker integration. Transforms a patient tumor profile (cancer type + mutations + biomarkers) into a quantitative ICI Response Score with drug-specific recommendations, resistance risk assessment, and monitoring plan.
Immunotherapy Response Prediction
Predict patient response to immune checkpoint inhibitors (ICIs) using multi-biomarker integration. Transforms a patient tumor profile (cancer type + mutations + biomarkers) into a quantitative ICI Response Score with drug-specific recommendations, resistance risk assessment, and monitoring plan.
Reasoning Before Searching
Not all tumors respond to checkpoint inhibitors. Reason through the biology before running tools:
- TMB (tumor mutational burden): More somatic mutations produce more neoantigens, which are recognized by T cells. High TMB (>=10 mut/Mb, FDA-approved threshold for pembrolizumab) generally predicts better response — but this varies by cancer type (e.g., RCC responds despite low TMB).
- MSI-H (microsatellite instability-high): Caused by defective DNA mismatch repair (MMR). MSI-H tumors have very high TMB and are pan-cancer approved for pembrolizumab. Check MLH1, MSH2, MSH6, PMS2 mutations.
- PD-L1 expression: The direct target of pembrolizumab/atezolizumab. High PD-L1 (TPS >=50% or CPS >=10 depending on cancer) predicts response in some cancers (NSCLC) but not all (melanoma, where TMB is more predictive).
- Resistance factors are equally important: STK11, KEAP1, JAK1/2 loss, B2M mutations can render an otherwise TMB-high tumor non-responsive.
Before calling any tool, determine which biomarkers are available for this patient and which are unknown. This determines which phases can be scored with data vs. must use cancer-type priors. Do not default to "moderate" for unknowns — flag them explicitly as missing.
LOOK UP DON'T GUESS: Never assume FDA approval for a biomarker-ICI combination — always verify with fda_pharmacogenomic_biomarkers or FDA_get_indications_by_drug_name. Cancer-specific thresholds differ from pan-cancer approvals.
KEY PRINCIPLES:
- Report-first approach - Create report file FIRST, then populate progressively
- Evidence-graded - Every finding has an evidence tier (T1-T4)
- Quantitative output - ICI Response Score (0-100) with transparent component breakdown
- Cancer-specific - All thresholds and predictions are cancer-type adjusted
- Multi-biomarker - Integrate TMB + MSI + PD-L1 + neoantigen + mutations
- Resistance-aware - Always check for known resistance mutations (STK11, PTEN, JAK1/2, B2M)
- Drug-specific - Recommend specific ICI agents with evidence
- Source-referenced - Every statement cites the tool/database source
- English-first queries - Always use English terms in tool calls
COMPUTE, DON'T DESCRIBE
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.
When to Use
Apply when user asks:
- "Will this patient respond to immunotherapy?"
- "Should I give pembrolizumab to this melanoma patient?"
- "Patient has NSCLC with TMB 25, PD-L1 80% - predict ICI response"
- "MSI-high colorectal cancer - which checkpoint inhibitor?"
- "Patient has BRAF V600E melanoma, TMB 15 - immunotherapy or targeted?"
- "Compare pembrolizumab vs nivolumab for this patient profile"
Input Parsing
Required: Cancer type + at least one of: mutation list OR TMB value Optional: PD-L1 expression, MSI status, immune infiltration data, HLA type, prior treatments, intended ICI
See INPUT_REFERENCE.md for input format examples, cancer type normalization, and gene symbol normalization tables.
Workflow Overview
Input: Cancer type + Mutations/TMB + Optional biomarkers (PD-L1, MSI, etc.)
Phase 1: Input Standardization & Cancer Context
Phase 2: TMB Analysis
Phase 3: Neoantigen Analysis
Phase 4: MSI/MMR Status Assessment
Phase 5: PD-L1 Expression Analysis
Phase 6: Immune Microenvironment Profiling
Phase 7: Mutation-Based Predictors
Phase 8: Clinical Evidence & ICI Options
Phase 9: Resistance Risk Assessment
Phase 10: Multi-Biomarker Score Integration
Phase 11: Clinical Recommendations
Phase 1: Input Standardization & Cancer Context
- Resolve cancer type to EFO ID via
OpenTargets_get_disease_id_description_by_name - Parse mutations into structured format:
{gene, variant, type} - Resolve gene IDs via
MyGene_query_genes - Look up cancer-specific ICI baseline ORR from the cancer context table (see SCORING_TABLES.md)
Phase 2: TMB Analysis
- Classify TMB: Very-Low (<5), Low (5-9.9), Intermediate (10-19.9), High (>=20)
- Check FDA TMB-H biomarker via
fda_pharmacogenomic_biomarkers(drug_name='pembrolizumab') - Apply cancer-specific TMB thresholds (see SCORING_TABLES.md)
- Note: RCC responds to ICIs despite low TMB; TMB is less predictive in some cancers
Phase 3: Neoantigen Analysis
- Estimate neoantigen burden: missense_count * 0.3 + frameshift_count * 1.5
- Check mutation impact via
UniProt_get_function_by_accession - Query known epitopes via
iedb_search_epitopes - POLE/POLD1 mutations indicate ultra-high neoantigen load
Phase 4: MSI/MMR Status Assessment
- Integrate MSI status if provided (MSI-H = 25 pts, MSS = 5 pts)
- Check mutations in MMR genes: MLH1, MSH2, MSH6, PMS2, EPCAM
- Check FDA MSI-H approvals via
fda_pharmacogenomic_biomarkers(biomarker='Microsatellite Instability')
Phase 5: PD-L1 Expression Analysis
- Classify PD-L1: High (>=50%), Positive (1-49%), Negative (<1%)
- Apply cancer-specific PD-L1 thresholds and scoring methods (TPS vs CPS)
- Get baseline expression via
HPA_get_cancer_prognostics_by_gene(gene_name='CD274')
Phase 6: Immune Microenvironment Profiling
- Query immune checkpoint gene expression for: CD274, PDCD1, CTLA4, LAG3, HAVCR2, TIGIT, CD8A, CD8B, GZMA, GZMB, PRF1, IFNG
- Classify tumor: Hot (T cell inflamed), Cold (immune desert), Immune excluded, Immune suppressed
- Run immune pathway enrichment via
enrichr_gene_enrichment_analysis
Phase 7: Mutation-Based Predictors
- Resistance mutations (apply PENALTIES): STK11 (-10), PTEN (-5), JAK1/2 (-10 each), B2M (-15), KEAP1 (-5), MDM2/4 (-5), EGFR (-5)
- Sensitivity mutations (apply BONUSES): POLE (+10), POLD1 (+5), BRCA1/2 (+3), ARID1A (+3), PBRM1 (+5 RCC only)
- Check CIViC and OpenTargets for driver mutation ICI context
- Check DDR pathway genes: ATM, ATR, CHEK1/2, BRCA1/2, PALB2, RAD50, MRE11
Phase 8: Clinical Evidence & ICI Options
- Query FDA indications for ICI drugs via
FDA_get_indications_by_drug_name - Search clinical trials via
search_clinical_trials(params:condition,intervention,query_term) - Search PubMed for biomarker-specific response data
- Get drug mechanisms via
OpenTargets_get_drug_mechanisms_of_action_by_chemblId
See SCORING_TABLES.md for ICI drug profiles and ChEMBL IDs.
Phase 9: Resistance Risk Assessment
- Check CIViC for resistance evidence via
civic_search_evidence_items - Assess pathway-level resistance: IFN-g signaling, antigen presentation, WNT/b-catenin, MAPK, PI3K/AKT/mTOR
- Summarize risk: Low / Moderate / High
Phase 10: Multi-Biomarker Score Integration
TOTAL SCORE = TMB_score + MSI_score + PDL1_score + Neoantigen_score + Mutation_bonus + Resistance_penalty
TMB_score: 5-30 points MSI_score: 5-25 points
PDL1_score: 5-20 points Neoantigen_score: 5-15 points
Mutation_bonus: 0-10 points Resistance_penalty: -20 to 0 points
Floor: 0, Cap: 100
Response Likelihood Tiers:
- 70-100 HIGH (50-80% ORR): Strong ICI candidate
- 40-69 MODERATE (20-50% ORR): Consider ICI, combo preferred
- 0-39 LOW (<20% ORR): ICI alone unlikely effective
Confidence: HIGH (all 4 biomarkers), MODERATE-HIGH (3/4), MODERATE (2/4), LOW (1), VERY LOW (cancer only)
Phase 11: Clinical Recommendations
- ICI drug selection using cancer-specific algorithm (see SCORING_TABLES.md)
- Monitoring plan: CT/MRI q8-12wk, ctDNA at 4-6wk, thyroid/liver function, irAEs
- Alternative strategies if LOW response: targeted therapy, chemotherapy, ICI+chemo combo, ICI+anti-angiogenic, ICI+CTLA-4 combo, clinical trials
Output Report
Save as immunotherapy_response_prediction_{cancer_type}.md. See REPORT_TEMPLATE.md for the full report structure.
Tool Parameter Reference
BEFORE calling ANY tool, verify parameters. See TOOLS_REFERENCE.md for verified tool parameters table.
Key reminders:
MyGene_query_genes: usequery(NOTq)EnsemblVEP_annotate_rsid: usevariant_id(NOTrsid)drugbank_*tools: ALL 4 params required (query,case_sensitive,exact_match,limit)cBioPortal_get_mutations:gene_listis a STRING not arrayensembl_lookup_gene: REQUIRESspecies='homo_sapiens'
Evidence Tiers
| Tier | Description | Source Examples |
|---|---|---|
| T1 | FDA-approved biomarker/indication | FDA labels, NCCN guidelines |
| T2 | Phase 2-3 clinical trial evidence | Published trial data, PubMed |
| T3 | Preclinical/computational evidence | Pathway analysis, in vitro data |
| T4 | Expert opinion/case reports | Case series, reviews |
References
- OpenTargets: https://platform.opentargets.org
- CIViC: https://civicdb.org
- FDA Drug Labels: https://dailymed.nlm.nih.gov
- DrugBank: https://go.drugbank.com
- PubMed: https://pubmed.ncbi.nlm.nih.gov
- IEDB: https://www.iedb.org
- HPA: https://www.proteinatlas.org
- cBioPortal: https://www.cbioportal.org
How to use tooluniverse-immunotherapy-response-prediction on Cursor
AI-first code editor with Composer
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-immunotherapy-response-prediction
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches tooluniverse-immunotherapy-response-prediction from GitHub repository mims-harvard/tooluniverse and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate tooluniverse-immunotherapy-response-prediction. Access the skill through slash commands (e.g., /tooluniverse-immunotherapy-response-prediction) 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
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★54 reviews- ★★★★★Hassan Mehta· Dec 24, 2024
Solid pick for teams standardizing on skills: tooluniverse-immunotherapy-response-prediction is focused, and the summary matches what you get after install.
- ★★★★★Dhruvi Jain· Dec 20, 2024
Keeps context tight: tooluniverse-immunotherapy-response-prediction is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Nikhil Choi· Dec 12, 2024
Registry listing for tooluniverse-immunotherapy-response-prediction matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ava Yang· Dec 4, 2024
Registry listing for tooluniverse-immunotherapy-response-prediction matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ava Abebe· Nov 23, 2024
Useful defaults in tooluniverse-immunotherapy-response-prediction — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kaira Garcia· Nov 15, 2024
tooluniverse-immunotherapy-response-prediction is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Oshnikdeep· Nov 11, 2024
tooluniverse-immunotherapy-response-prediction has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zara Abebe· Nov 3, 2024
Useful defaults in tooluniverse-immunotherapy-response-prediction — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Isabella Bhatia· Oct 22, 2024
I recommend tooluniverse-immunotherapy-response-prediction for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Zaid Harris· Oct 14, 2024
I recommend tooluniverse-immunotherapy-response-prediction for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 54