rna-seq-analysis
Skill62 starsChanged 5 months agoMIT-0View on GitHub
Bulk RNA-seq analysis pipeline covering alignment (STAR), quantification (Salmon, featureCounts), and differential expression (DESeq2). Triggers on RNA-seq, STAR, Salmon, DESeq2, differential expression, gene expression, tximport, featureCounts, transcriptomics, "bulk RNA-seq", "STAR alignment", "Salmon quantification", "gene counts", "DESeq2 results", "shrinkage estimator", "volcano plot RNA-seq".
In this repository41 other files it gives its agents.
- aws-genai-ml-architectSkill
- bioinformatics-on-healthomicsSkill
- biomarker-discoverySkill
- cdisc-complianceSkill
- cell-type-annotationSkill
- cheminformaticsSkill
- claims-analyticsSkill
- claims-billing-rulesSkill
- clinical-data-standardsSkill
- coordination-of-benefitsSkill
- dicom-processingSkill
- digital-pathologySkill
- drug-repurposingSkill
- edc-data-validationSkill
- ehr-data-parsingSkill
- genomic-variant-interpretationSkill
- hedis-measure-specificationSkill
- imaging-study-designSkill
- medical-device-software-complianceSkill
- ml-researcherSkill
- molecular-dockingSkill
- multi-omics-integrationSkill
- multi-omics-pipelineSkill
- ngs-quality-controlSkill
- pa-clinical-policySkill
- pa-decision-automationSkill
- pharmacoepidemiologySkill
- protein-structure-analysisSkill
- provider-denial-workupSkill
- quality-measuresSkill
- quantitative-proteomicsSkill
- radiology-preprocessingSkill
- risk-adjustmentSkill
- risk-adjustment-strategySkill
- risk-stratification-indicesSkill
- rwd-cohort-analysisSkill
- scrna-seq-pipelineSkill
- structure-based-drug-designSkill
- trajectory-analysisSkill
- translational-researchSkill
- variant-callingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 50
Verify with: infer_experiment.py (RSeQC) or Salmon's lib_format_counts.json.
- Very specific: line 68
Right: Check with infer_experiment.py or Salmon lib_format_counts.json before running featureCounts
- Distinctive: line 72
Right: Always start from raw integer counts
- Very specific: line 76
Right: Use DESeqDataSetFromTximport(txi, ...) which preserves the length offset
- Very specific: line 80
Right: Put interest last: ~ batch + condition
- Distinctive: line 92
Right: Use column 3 (forward) or column 4 (reverse) matching your kit
- Very specific: line 100
Right: Check table(coldata$batch, coldata$condition) first
- Distinctive: line 101
Why: No statistical model can separate perfectly correlated effects
- Distinctive: line 108
Keep code comments minimal and functional (what, not why-it-exists)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
RNA-seq Analysis — Pipeline Skill (Thin Scaffold)
Overview
Adds decision logic for choosing quantification paths (STAR vs Salmon), strandedness determination, and DESeq2 modeling pitfalls that LLMs routinely get wrong.
Usage
- Activate when choosing between alignment-based (STAR+featureCounts) vs alignment-free (Salmon) quantification
- Activate when setting up DESeq2 from either count source
- Activate when debugging unexpected low counts or weak DE signal
Core Concepts
Decision Logic
Need BAMs? (variant calling, fusions, novel transcripts)
├── YES → STAR two-pass + featureCounts
└── NO → Salmon (faster, lower RAM, bias-corrected)
Salmon output → DESeq2:
└── Use DESeqDataSetFromTximport (preserves length offset)
└── NEVER round txi$counts and pass to DESeqDataSetFromMatrix
Filtering strategy (VQSR equivalent):
├── ≥30 samples → VQSR-like (default DESeq2 shrinkage works well)
└── <30 samples → still works, but pre-filter aggressivelyStrandedness determination (MUST verify before counting):
| Kit | featureCounts -s | Salmon -l |
| TruSeq Stranded / dUTP | 2 | ISR (PE) / SR (SE) |
| Ligation / forward | 1 | ISF / SF |
| Unstranded | 0 | IU / U |
Verify with: infer_experiment.py (RSeQC) or Salmon's lib_format_counts.json.
Critical Parameters
| Parameter | Value | When to change |
--sjdbOverhang | readLength - 1 (default 100) | Non-100bp reads |
--twopassMode Basic | Always for DE | Skip only for speed in QC runs |
Salmon --gcBias --seqBias | Always on | Never skip for Illumina |
Salmon --validateMappings | Always on | Enables selective alignment |
featureCounts -s | Kit-dependent | ALWAYS verify empirically |
| DESeq2 pre-filter | rowSums(counts >= 10) >= smallest_group | Adjust 10 for shallow sequencing |
lfcShrink type | "apeglm" | Use "ashr" for arbitrary contrasts |
| Design formula | ~ batch + condition (interest LAST) | Always put interest term last |
Common Mistakes
- Wrong: Guessing strandedness (
-s) instead of verifying empirically Right: Check withinfer_experiment.pyor Salmonlib_format_counts.jsonbefore running featureCounts Why: Wrong strandedness causes 2–10× lower counts and weak DE signal - Wrong: Passing normalized counts (TPM, FPKM, CPM) to DESeq2 Right: Always start from raw integer counts Why: Normalized values break the negative-binomial model
- Wrong: Rounding
txi$countsand passing toDESeqDataSetFromMatrixRight: UseDESeqDataSetFromTximport(txi, ...)which preserves the length offset Why: Rounding discards per-gene length correction for transcript-length bias - Wrong: Placing variable of interest first in design (
~ condition + batch) Right: Put interest last:~ batch + conditionWhy: DESeq2 tests the last term by default - Wrong: Assuming DESeq2 reorders samples to match
Right: Assert
stopifnot(all(colnames(cts) == rownames(coldata)))before creating DESeq object Why: DESeq2 silently mislabels samples if order doesn't match - Wrong: Skipping pre-filtering of low-count genes
Right: Filter with
rowSums(counts(dds) >= 10) >= smallest_group_sizeWhy: Near-zero genes inflate runtime and dilute multiple-testing correction - Wrong: Using STAR
ReadsPerGene.out.tabcolumn 2 for stranded libraries Right: Use column 3 (forward) or column 4 (reverse) matching your kit Why: Column 2 is unstranded; using it for stranded data halves effective counts - Wrong: Including samples with <10M mapped reads or <70% mapping rate Right: Exclude or flag before fitting Why: Low-quality samples distort size factors and dispersion estimates
- Wrong: Modeling when batch is perfectly confounded with condition
Right: Check
table(coldata$batch, coldata$condition)first Why: No statistical model can separate perfectly correlated effects
Response Format
- Lead with the command or code the user needs — explain after
- Structure as: confirm inputs → working code → key parameters explained → gotchas
- One complete working example per task; do not show every alternative
- Keep code comments minimal and functional (what, not why-it-exists)
- Target: 50-100 lines of code with brief surrounding explanation
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

