tooluniverse-crispr-screen-analysis

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-crispr-screen-analysis
0 commentsdiscussion
summary

Comprehensive skill for analyzing CRISPR-Cas9 genetic screens to identify essential genes, synthetic lethal interactions, and therapeutic targets through robust statistical analysis and pathway enrichment.

skill.md

ToolUniverse CRISPR Screen Analysis

Comprehensive skill for analyzing CRISPR-Cas9 genetic screens to identify essential genes, synthetic lethal interactions, and therapeutic targets through robust statistical analysis and pathway enrichment.

Overview

CRISPR screens enable genome-wide functional genomics by systematically perturbing genes and measuring fitness effects. This skill provides an 8-phase workflow for:

  • Processing sgRNA count matrices
  • Quality control and normalization
  • Gene-level essentiality scoring (MAGeCK-like and BAGEL-like approaches)
  • Synthetic lethality detection
  • Pathway enrichment analysis
  • Drug target prioritization with DepMap integration
  • Integration with expression and mutation data

Core Workflow

Phase 1: Data Import & sgRNA Count Processing

Load sgRNA count matrix (MAGeCK format or generic TSV). Expected columns: sgRNA, Gene, plus sample columns. Create experimental design table linking samples to conditions (baseline/treatment) with replicate assignments.

Phase 2: Quality Control & Filtering

Assess sgRNA distribution quality:

  • Library sizes per sample (total reads)
  • Zero-count sgRNAs: Count across samples
  • Low-count filtering: Remove sgRNAs below threshold (default: <30 reads in >N-2 samples)
  • Gini coefficient: Assess distribution skewness per sample
  • Report filtering recommendations

Phase 3: Normalization

Normalize sgRNA counts to account for library size differences:

  • Median ratio (DESeq2-like): Calculate geometric mean reference, compute size factors as median of ratios
  • Total count (CPM-like): Divide by library size in millions

Calculate log2 fold changes (LFC) between treatment and control conditions with pseudocount.

Phase 4: Gene-Level Scoring

Two scoring approaches:

  • MAGeCK-like (RRA): Rank all sgRNAs by LFC, compute mean rank per gene. Lower mean rank = more essential. Includes sgRNA count and mean LFC per gene.
  • BAGEL-like (Bayes Factor): Use reference essential/non-essential gene sets to estimate LFC distributions. Calculate likelihood ratio (Bayes Factor) for each gene. Higher BF = more likely essential.

Phase 5: Synthetic Lethality Detection

Compare essentiality scores between wildtype and mutant cell lines:

  • Merge gene scores, calculate delta LFC and delta rank
  • Filter for genes essential in mutant (LFC < threshold) but not wildtype (LFC > -0.5) with large rank change
  • Sort by differential essentiality

Query DepMap/literature for known dependencies using PubMed search.

Phase 6: Pathway Enrichment Analysis

Submit top essential genes to Enrichr for pathway enrichment:

  • KEGG pathways
  • GO Biological Process
  • Retrieve enriched terms with p-values and gene lists

Phase 7: Drug Target Prioritization

Composite scoring combining:

  • Essentiality (50% weight): Normalized mean LFC from CRISPR screen
  • Expression (30% weight): Log2 fold change from RNA-seq (if available)
  • Druggability (20% weight): Number of drug interactions from DGIdb

Query DGIdb for each candidate gene to find existing drugs, interaction types, and sources.

Phase 8: Report Generation

Generate markdown report with:

  • Summary statistics (total genes, essential genes, non-essential genes)
  • Top 20 essential genes table (rank, gene, mean LFC, sgRNAs, score)
  • Pathway enrichment results (top 10 terms per database)
  • Drug target candidates (rank, gene, essentiality, expression FC, druggability, priority score)
  • Methods section

ToolUniverse Tool Integration

Key Tools Used:

  • PubMed_search_articles - Literature search for gene essentiality and drug resistance
  • ReactomeAnalysis_pathway_enrichment - Pathway enrichment (param: identifiers newline-separated, page_size)
  • enrichr_gene_enrichment_analysis - Enrichr enrichment (param: gene_list array, libs array)
  • DGIdb_get_drug_gene_interactions - Drug-gene interactions (param: genes as array)
  • DGIdb_get_gene_druggability - Druggability categories
  • STRING_get_network - Protein interaction networks
  • kegg_search_pathway - Pathway search by keyword
  • kegg_get_pathway_info - Pathway details by ID

Cancer Context (essential for drug resistance screens):

  • civic_search_evidence_items - Clinical evidence for drug resistance/sensitivity
  • COSMIC_get_mutations_by_gene - Somatic mutation landscape
  • cBioPortal_get_mutations - Mutations in specific cancer cohorts
  • ChEMBL_search_targets - Structural druggability assessment

Expression & Variant Integration:

  • GEO_search_rnaseq_datasets / geo_search_datasets - Expression datasets
  • ClinVar_search_variants - Known pathogenic variants
  • gnomad_get_gene_constraints - Gene constraint metrics (pLI, oe_lof)
  • UniProt_get_function_by_accession - Protein function for hit validation

Quick Start

import pandas as pd
from tooluniverse import ToolUniverse

# 1. Load data
counts, meta = load_sgrna_counts("sgrna_counts.txt")
design = create_design_matrix(['T0_1', 'T0_2', 'T14_1', 'T14_2'],
                               ['baseline', 'baseline', 'treatment', 'treatment'])

# 2. Process
filtered_counts, filtered_mapping = filter_low_count_sgrnas(counts, meta['sgrna_to_gene'])
norm_counts, _ = normalize_counts(filtered_counts)
lfc, _, _ = calculate_lfc(norm_counts, design)

# 3. Score genes
gene_scores = mageck_gene_scoring(lfc, filtered_mapping)

# 4. Enrich pathways
enrichment = enrich_essential_genes(gene_scores, top_n=100)

# 5. Find drug targets
drug_targets = prioritize_drug_targets(gene_scores)

# 6. Generate report
report = generate_crispr_report(gene_scores, enrichment, drug_targets)

Domain Reasoning: Hits Are Statistical, Not Biological

Screen hits are statistical findings, not direct readouts of biological relevance. A gene scoring as essential might be essential for cell growth in general (housekeeping) or essential specifically for the phenotype you are screening for (interesting). Always compare your screen hits to public essentiality data — use DepMap pan-cancer dependency scores to filter genes that are broadly essential across all cell lines. A gene essential only in your specific context, but not pan-essential in DepMap, is a better candidate for follow-up than one that scores in every screen.

LOOK UP DON'T GUESS: DepMap dependency scores, known core essential gene sets (Hart et al., Blomen et al.), and DGIdb druggability data for your top hits. Do not assume a hit is context-specific without checking public essentiality databases.

Interpretation Framework

Evidence Grade Criteria Validation Priority
A -- Strong hit MAGeCK RRA p < 0.001, BAGEL BF > 5, >=3 sgRNAs with concordant LFC Immediate validation (individual KO, growth assay)
B -- Moderate hit MAGeCK RRA p < 0.01, BAGEL BF 2-5, >=2 concordant sgRNAs Secondary validation pool
C -- Weak/ambiguous p > 0.01, BF < 2, or discordant sgRNA effects Deprioritize; check for copy-number bias or seed effects

Interpreting screen results:

  • A gene with mean LFC < -1.0 across replicates and >=3 concordant sgRNAs is a robust essentiality hit; single-sgRNA effects are more likely off-target and should be flagged.
  • Essential gene thresholds are context-dependent: core fitness genes (e.g., ribosomal, spliceosomal) should deplete in any screen and serve as positive controls -- their absence from the hit list indicates a QC problem.
  • Synthetic lethal hits (depleted in mutant but not wildtype) require delta-LFC > 1.5 and confirmation in an independent cell line before therapeutic target nomination.

Synthesis questions to address in the report:

  1. Do the top hits cluster in known pathways (Reactome/KEGG), or are they scattered -- suggesting technical noise?
  2. Are known essential genes (Hart et al. reference set) correctly identified, confirming screen quality?
  3. For drug target candidates: does DGIdb show existing compounds, and does DepMap confirm the dependency across multiple cell lines?

References

  • Li W, et al. (2014) MAGeCK enables robust identification of essential genes from genome-scale CRISPR/Cas9 knockout screens. Genome Biology
  • Hart T, et al. (2015) High-Resolution CRISPR Screens Reveal Fitness Genes and Genotype-Specific Cancer Liabilities. Cell
  • Meyers RM, et al. (2017) Computational correction of copy number effect improves specificity of CRISPR-Cas9 essentiality screens. Nature Genetics
  • Tsherniak A, et al. (2017) Defining a Cancer Dependency Map. Cell (DepMap)

See Also

  • ANALYSIS_DETAILS.md - Detailed code snippets for all 8 phases
  • USE_CASES.md - Complete use cases (essentiality screen, synthetic lethality, drug target discovery, expression integration) and best practices
  • EXAMPLES.md - Example usage and quick reference
  • QUICK_START.md - Quick start guide
  • FALLBACK_PATCH.md - Fallback patterns for API issues
how to use tooluniverse-crispr-screen-analysis

How to use tooluniverse-crispr-screen-analysis 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-crispr-screen-analysis
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-crispr-screen-analysis

The skills CLI fetches tooluniverse-crispr-screen-analysis 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-crispr-screen-analysis

Reload or restart Cursor to activate tooluniverse-crispr-screen-analysis. Access the skill through slash commands (e.g., /tooluniverse-crispr-screen-analysis) 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.847 reviews
  • Chaitanya Patil· Dec 20, 2024

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

  • Harper Mensah· Dec 20, 2024

    Solid pick for teams standardizing on skills: tooluniverse-crispr-screen-analysis is focused, and the summary matches what you get after install.

  • Anaya Ghosh· Dec 8, 2024

    tooluniverse-crispr-screen-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Advait Smith· Nov 27, 2024

    Solid pick for teams standardizing on skills: tooluniverse-crispr-screen-analysis is focused, and the summary matches what you get after install.

  • Piyush G· Nov 11, 2024

    tooluniverse-crispr-screen-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Carlos Iyer· Nov 11, 2024

    tooluniverse-crispr-screen-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Advait Singh· Oct 18, 2024

    tooluniverse-crispr-screen-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Shikha Mishra· Oct 2, 2024

    Solid pick for teams standardizing on skills: tooluniverse-crispr-screen-analysis is focused, and the summary matches what you get after install.

  • Carlos Taylor· Oct 2, 2024

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

  • Rahul Santra· Sep 21, 2024

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

showing 1-10 of 47

1 / 5