plugin/skills/tooluniverse-precision-medicine-stratification/SKILL.md
Patient stratification for precision medicine — integrate genomic, clinical, and therapeutic data to split patients into responder/non-responder groups, risk tiers, or treatment-decision groups. Use for stratification-by-biomarker, treatment-selection logic, and personalized therapeutic strategy reports per patient subgroup.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-precision-medicine-stratificationInstall 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.
Transform patient genomic and clinical profiles into actionable risk stratification, treatment recommendations, and personalized therapeutic strategies.
Stratification means splitting patients into groups that respond differently to a treatment or have different prognoses. Ask these questions before running any tools:
Route to the correct Phase 3 path BEFORE running Phase 2 tools — cancer, metabolic, CVD, rare disease, and autoimmune pipelines require different stratifiers.
LOOK UP DON'T GUESS: Never assume a variant is pathogenic, never assume a gene is relevant to a disease, never assign metabolizer status without PharmGKB or CPIC evidence.
KEY PRINCIPLES:
Reference files (same directory):
TOOLS_REFERENCE.md - Tool parameters, response formats, phase-by-phase tool listsSCORING_REFERENCE.md - Scoring matrices, risk tiers, pathogenicity tables, PGx tablesREPORT_TEMPLATE.md - Output report template, treatment algorithms, completeness requirementsEXAMPLES.md - Six worked examples (cancer, metabolic, NSCLC, CVD, rare, neuro)QUICK_START.md - Sample prompts and output summaryWhen 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.
Apply when user asks about patient risk stratification, treatment selection, prognosis prediction, or personalized therapeutic strategy for any disease with genomic/clinical data.
NOT for (use other skills instead):
tooluniverse-variant-interpretationtooluniverse-immunotherapy-response-predictiontooluniverse-adverse-event-detectiontooluniverse-drug-target-validationtooluniverse-clinical-trial-matchingtooluniverse-drug-drug-interactiontooluniverse-polygenic-risk-scoreClassify into one category (determines Phase 3 routing):
| Category | Examples | |----------|----------| | CANCER | Breast, lung, colorectal, melanoma | | METABOLIC | Type 2 diabetes, obesity, NAFLD | | CARDIOVASCULAR | CAD, heart failure, AF | | NEUROLOGICAL | Alzheimer, Parkinson, epilepsy | | RARE/MONOGENIC | Marfan, CF, sickle cell, Huntington | | AUTOIMMUNE | RA, lupus, MS, Crohn's |
See TOOLS_REFERENCE.md for full details. Key gotchas:
query (NOT q)variant_id (NOT rsid)species='homo_sapiens'query, case_sensitive, exact_match, limitgene_list is a STRING (space-separated), not array{articles: [...]}limit=1000 for all results{data: {entity: {field: ...}}} structurePhase 1: Disease Disambiguation & Profile Standardization
Phase 2: Genetic Risk Assessment
Phase 3: Disease-Specific Molecular Stratification (routes by disease type)
Phase 4: Pharmacogenomic Profiling
Phase 5: Comorbidity & Drug Interaction Risk
Phase 6: Molecular Pathway Analysis
Phase 7: Clinical Evidence & Guidelines
Phase 8: Clinical Trial Matching
Phase 9: Integrated Scoring & Recommendations
OpenTargets_get_disease_id_description_by_nameMyGene_query_genes to get Ensembl/Entrez IDsClinVar_search_variants, EnsemblVEP_annotate_rsid/_hgvsOpenTargets_target_disease_evidencegwas_get_associations_for_trait, OpenTargets_search_gwas_studies_by_diseasegnomad_get_variantgnomad_get_gene_constraints (pLI, LOEUF scores)Scoring: See SCORING_REFERENCE.md for genetic risk score component (0-35 points).
cBioPortal_get_mutations, HPA_get_cancer_prognostics_by_genefda_pharmacogenomic_biomarkers for FDA cutoffsGWAS_search_associations_by_gene, OpenTargets_target_disease_evidenceClinVar_search_variants for LDLR, APOB, PCSK9PharmGKB_get_clinical_annotations for SLCO1B1ClinVar_search_variantsUniProt_get_disease_variants_by_accessionScoring: See SCORING_REFERENCE.md for disease-specific tables.
PharmGKB_get_clinical_annotations, PharmGKB_get_dosing_guidelinesfda_pharmacogenomic_biomarkers (use limit=1000)PharmGKB_get_drug_detailsScoring: See SCORING_REFERENCE.md for PGx risk score (0-10 points).
OpenTargets_get_associated_targets_by_disease_efoIddrugbank_get_drug_interactions_by_drug_name_or_id, FDA_get_drug_interactions_by_drug_nameenrichr_gene_enrichment_analysis (libs: KEGG_2021_Human, Reactome_2022, GO_Biological_Process_2023)ReactomeAnalysis_pathway_enrichment, Reactome_map_uniprot_to_pathwaysSTRING_get_interaction_partners, STRING_functional_enrichmentOpenTargets_get_target_tractability_by_ensemblIDPubMed_Guidelines_Search (fallback: PubMed_search_articles)OpenTargets_get_associated_drugs_by_disease_efoId, FDA_get_indications_by_drug_namecivic_search_evidence_items, civic_search_assertionssearch_clinical_trials with condition + interventionsearch_clinical_trials for basket/umbrella trials| Score | Tier | Management | |-------|------|------------| | 75-100 | VERY HIGH | Intensive treatment, subspecialty referral, clinical trial | | 50-74 | HIGH | Aggressive treatment, close monitoring | | 25-49 | INTERMEDIATE | Standard guideline-based care, PGx-guided dosing | | 0-24 | LOW | Surveillance, prevention, risk factor modification |
Generate report per REPORT_TEMPLATE.md. See SCORING_REFERENCE.md for detailed scoring matrices.
See EXAMPLES.md for six detailed worked examples:
tools
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.