plugins/tooluniverse/skills/tooluniverse-functional-genomics-screens/SKILL.md
Interpret hits from CRISPR-KO/CRISPRi/shRNA screens by integrating DepMap essentiality, gnomAD constraint scores, pathway context (Reactome, STRING), druggability (DGIdb), and clinical evidence (CIViC, COSMIC). Use for screen-hit prioritization, essentiality ranking, and turning a list of screen hits into a prioritized target shortlist.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-functional-genomics-screensInstall 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.
Pipeline for validating and prioritizing hits from genetic screens (CRISPR-KO, CRISPRi, shRNA) by integrating essentiality (DepMap), constraint (gnomAD), pathways (Reactome, STRING), druggability (DGIdb), and clinical evidence (CIViC, COSMIC).
Guiding principles:
When uncertain about any scientific fact, SEARCH databases first.
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.
Phase 0: Input Processing → gene list, screen type, cell line, disease context
Phase 1: Hit Validation → DepMap dependency, gnomAD constraint, UniProt function
Phase 2: Pathway & Network → Reactome enrichment, STRING network, functional clusters
Phase 3: Druggability → DGIdb interactions, druggable categories, PharmacoDB
Phase 4: Clinical Evidence → CIViC, COSMIC mutations
Phase 5: Literature → PubMed for key hits
Phase 6: Prioritized Report → ranked target list with multi-dimensional scoring
Tools:
DepMap_get_gene_dependencies(gene_symbol=...) -- returns gene metadata only (NOT per-cell-line scores)DepMap_search_cell_lines(query=...) -- cell line metadatagnomad_get_gene_constraints(gene_symbol=...) -- pLI, LOEUF (may return "Service overloaded")UniProt_get_function_by_accession(accession=...) -- function summaryClassification: Pan-essential (>90% lines), Selectively essential (specific lineages), Context-specific (screen model only). Chronos < -0.5 = likely essential, < -1.0 = strongly essential.
DepMap per-cell-line Chronos scores: DepMap_get_gene_dependencies returns metadata only. For the actual per-cell-line scores, use the bundled script in the cell-line-profiling skill — tooluniverse-cell-line-profiling/scripts/depmap_gene_dependency.py (downloads the current DepMap Public CRISPRGeneEffect.csv once, cached; queries by gene or cell-line):
python depmap_gene_dependency.py gene KRAS --lineage Lung --top 20 # most-dependent lines
python depmap_gene_dependency.py cell-line A375 --top 25 # genes the line needs
Chronos < -0.5 ≈ dependency, < -1.0 strongly essential. Fallback if you can't run it: gnomAD constraint + PubMed_search_articles(query="[gene] CRISPR screen [cancer]").
ReactomeAnalysis_pathway_enrichment(identifiers="TP53 BRCA1 EGFR") -- space-separated stringSTRING_get_network(identifiers="GENE1\rGENE2\rGENE3", species=9606) -- carriage-return separatedSTRING_functional_enrichment(identifiers=..., species=9606) -- GO/KEGG enrichmentDGIdb_get_drug_gene_interactions(genes=["EGFR","BRAF"]) -- drug-gene interactionsDGIdb_get_gene_druggability(genes=[...]) -- categories (kinase, GPCR, etc.)search_clinical_trials and PubMed for novel inhibitors not yet in DGIdb.civic_search_evidence_items(molecular_profile=gene) -- NOT queryCOSMIC_get_mutations_by_gene(gene_name=...) -- somatic mutation frequencyScoring (0-18):
| Criterion | Score 3 | Score 0 | |-----------|---------|---------| | Selective essentiality | <-0.5 in disease AND >-0.2 elsewhere | >-0.2 (not essential) | | Pathway convergence | 3+ hits same pathway | Isolated hit | | Druggability | Approved drug exists | Not druggable | | Clinical evidence | CIViC therapeutic | No clinical data | | Constraint | pLI >0.9 | No data | | Literature | Multiple validation studies | No publications |
Tiers: T1 (15-18) high-confidence, T2 (10-14) promising, T3 (5-9) speculative, T4 (<5) likely false positive.
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.