tooluniverse-rnaseq-deseq2

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-rnaseq-deseq2
0 commentsdiscussion
summary

Differential expression analysis of RNA-seq count data using PyDESeq2, with enrichment analysis (gseapy) and gene annotation via ToolUniverse.

skill.md

RNA-seq Differential Expression Analysis (DESeq2)

Differential expression analysis of RNA-seq count data using PyDESeq2, with enrichment analysis (gseapy) and gene annotation via ToolUniverse.

BixBench Coverage: Validated on 53 BixBench questions across 15 computational biology projects.

Domain Reasoning

DESeq2 assumes that most genes are NOT differentially expressed — this is its normalization assumption. If this assumption is violated (e.g., global transcriptional shutdown, where the majority of genes genuinely decrease), size factor normalization will inflate expression in the treatment group and produce artifactually upregulated genes. Always check the MA plot: the fold-change cloud should be centered on zero across all expression levels. A systematic upward or downward shift indicates a normalization problem, not biology.

LOOK UP DON'T GUESS

  • Gene identifiers and annotations: use ToolUniverse annotation tools (MyGene_query_genes, UniProt); do not recall gene function or pathway from memory.
  • Enriched pathways: run gseapy or equivalent on the actual DEG list; do not list expected pathways.
  • Design formula factors: inspect metadata.columns and metadata[factor].unique() from the actual data; do not assume metadata structure.
  • DEG thresholds: apply the values specified by the user (padj, log2FC, baseMean); do not substitute defaults without checking the question.

Core Principles

  1. Data-first - Load and validate count data and metadata BEFORE any analysis
  2. Statistical rigor - Proper normalization, dispersion estimation, multiple testing correction
  3. Flexible design - Single-factor, multi-factor, and interaction designs
  4. Threshold awareness - Apply user-specified thresholds exactly (padj, log2FC, baseMean)
  5. Reproducible - Set random seeds, document all parameters
  6. Question-driven - Parse what the user is actually asking; extract the specific answer
  7. Enrichment integration - Chain DESeq2 results into pathway/GO enrichment when requested

When to Use

  • RNA-seq count matrices needing differential expression analysis
  • DESeq2, DEGs, padj, log2FC questions
  • Dispersion estimates or diagnostics
  • GO, KEGG, Reactome enrichment on DEGs
  • Specific gene expression changes between conditions
  • Batch effect correction in RNA-seq

Required Packages

import pandas as pd, numpy as np
from pydeseq2.dds import DeseqDataSet
from pydeseq2.ds import DeseqStats
import gseapy as gp          # enrichment (optional)
from tooluniverse import ToolUniverse  # annotation (optional)

Analysis Workflow

Step 1: Parse the Question

Extract: data files, thresholds (padj/log2FC/baseMean), design factors, contrast, direction, enrichment type, specific genes. See question_parsing.md.

Step 2: Load & Validate Data

Load counts + metadata, ensure samples-as-rows/genes-as-columns, verify integer counts, align sample names, remove zero-count genes. See data_loading.md.

Step 2.5: Inspect Metadata (REQUIRED)

List ALL metadata columns and levels. Categorize as biological interest vs batch/block. Build design formula with covariates first, factor of interest last. See design_formula_guide.md.

Step 3: Run PyDESeq2

Set reference level via pd.Categorical, create DeseqDataSet, call dds.deseq2(), extract DeseqStats with contrast, run Wald test, optionally apply LFC shrinkage. See pydeseq2_workflow.md.

Tool boundaries:

  • Python (PyDESeq2): ALL DESeq2 analysis
  • ToolUniverse: ONLY gene annotation (ID conversion, pathway context)
  • gseapy: Enrichment analysis (GO/KEGG/Reactome)

Step 4: Filter Results

Apply padj, log2FC, baseMean thresholds. Split by direction if needed. See result_filtering.md.

Step 5: Dispersion Analysis (if asked)

Key columns: genewise_dispersions, fitted_dispersions, MAP_dispersions, dispersions. See dispersion_analysis.md.

Step 6: Enrichment (optional)

Use gseapy enrich() with appropriate gene set library. See enrichment_analysis.md.

Step 7: Gene Annotation (optional)

Use ToolUniverse for ID conversion and gene context only. See output_formatting.md.

Common Patterns

Pattern Type Key Operation
1 DEG count len(results[(padj<0.05) & (abs(lfc)>0.5)])
2 Gene value results.loc['GENE', 'log2FoldChange']
3 Direction Filter log2FoldChange > 0 or < 0
4 Set ops degs_A - degs_B for unique DEGs
5 Dispersion (dds.var['genewise_dispersions'] < thr).sum()

See bixbench_examples.md for all 10 patterns with examples.

Error Quick Reference

Error Fix
No matching samples Transpose counts; strip whitespace
Dispersion trend no converge fit_type='mean'
Contrast not found Check metadata['factor'].unique()
Non-integer counts Round to int OR use t-test
NaN in padj Independent filtering removed genes

See troubleshooting.md for full debugging guide.

Interpretation Framework

DESeq2 Result Interpretation

Metric Threshold Interpretation
padj < 0.05 Statistically significant after multiple testing correction
log2FoldChange > 1 or < -1 Biologically meaningful fold change (2x up or down)
baseMean > 10 Gene is expressed at detectable levels
lfcSE < 1.0 Fold change estimate is precise

Evidence Grading for DEGs

Grade Criteria Action
Strong DEG padj < 0.01, LFC
Moderate DEG padj < 0.05, LFC
Weak DEG padj < 0.1 or LFC
Not significant padj >= 0.1 Do not report as differentially expressed

Synthesis Questions

  1. How many DEGs and in which direction? (up vs down ratio indicates biological response type)
  2. What pathways are enriched? (GO/KEGG enrichment of DEGs reveals mechanism)
  3. Are the top DEGs biologically plausible? (known markers for the condition?)
  4. Is the fold change magnitude realistic? (LFC > 5 is unusual; check for outlier-driven effects)
  5. Are there batch effects? (PCA should separate by condition, not by batch)

Known Limitations

  • PyDESeq2 vs R DESeq2: Numerical differences exist for very low dispersion genes (<1e-05). For exact R reproducibility, use rpy2.
  • gseapy vs R clusterProfiler: Results may differ. See r_clusterprofiler_guide.md.

Reference Files

Utility Scripts

how to use tooluniverse-rnaseq-deseq2

How to use tooluniverse-rnaseq-deseq2 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-rnaseq-deseq2
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-rnaseq-deseq2

The skills CLI fetches tooluniverse-rnaseq-deseq2 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-rnaseq-deseq2

Reload or restart Cursor to activate tooluniverse-rnaseq-deseq2. Access the skill through slash commands (e.g., /tooluniverse-rnaseq-deseq2) 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.431 reviews
  • Ren Li· Dec 16, 2024

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

  • Ganesh Mohane· Dec 4, 2024

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

  • Sakshi Patil· Nov 23, 2024

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

  • Amina Abbas· Nov 15, 2024

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

  • Yusuf Khan· Nov 7, 2024

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

  • Ren Mensah· Oct 26, 2024

    I recommend tooluniverse-rnaseq-deseq2 for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Chaitanya Patil· Oct 14, 2024

    tooluniverse-rnaseq-deseq2 fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Amina Verma· Oct 6, 2024

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

  • Yusuf Iyer· Sep 21, 2024

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

  • Layla Johnson· Aug 12, 2024

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

showing 1-10 of 31

1 / 4