Agent skill

featurecounts-rna-counting

Counts RNA-seq reads overlapping GTF gene features. Takes sorted STAR BAMs plus GTF; outputs a per-gene tab-delimited matrix across samples. Handles strandedness (0/1/2), paired-end, multi-sample batch counting in one command, and outputs assignment statistics. Use Salmon for alignment-free quantification; use featureCounts when STAR BAMs already exist.

BioTender-maxgithub.com/BioTender-maxGitHub ↗
claude-codeNOASSERTION
Install
npx skills add BioTender-max/awesome-bio-agent-skills --skill featurecounts-rna-counting --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Path: skills/sciagent/featurecounts-rna-counting/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 144
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# featureCounts — RNA-seq Read Counting ## Overview featureCounts (part of the Subread package) assigns sequencing reads in BAM files to genomic features defined in a GTF/GFF annotation. It counts how many reads overlap each gene (or exon, intron, or custom feature), producing a gene × sample count matrix suitable for differential expression analysis with DESeq2 or edgeR. featureCounts processes multiple BAM files in a single command, reporting read assignment statistics (assigned, unassigned by category) alongside the count matrix. It is the standard counting step after STAR alignment in RNA-seq pipelines. ## When to Use - Generating gene-level count matrices from STAR-aligned BAM files for DESeq2 or edgeR - Counting reads from multiple samples simultaneously in a single featureCounts command - Handling stranded RNA-seq libraries where sense/antisense assignment matters - Producing exon-level or custom-feature counts (e.g., for splicing analysis with DEXSeq) - Verifying strandedness of an RNA-seq library when protocol documentation is unavailable - Use **Salmon** instead when no BAM file exists and fast pseudoalignment is preferred - Use **HTSeq-count** as an alternative with slow

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. Prerequisites
  4. Quick Start
  5. Workflow
  6. Step 1: Prepare BAM Files and GTF
  7. Step 2: Determine Library Strandedness
  8. Step 3: Count Unstranded Paired-End RNA-seq
  9. Step 4: Count Stranded Libraries
  10. Step 5: Load Count Matrix into Python for DESeq2
  11. Step 6: Run DESeq2 with featureCounts Matrix
  12. Key Parameters
  13. Common Recipes
  14. Recipe 1: Count with Subread Package via Python subprocess
Commands it runs
Install with conda (recommended)
conda install -c bioconda subread
Verify
featureCounts -v
featureCounts v2.0.6
sudo apt-get install subread
Count reads for multiple samples (unstranded paired-end RNA-seq)
featureCounts \
results/sample1/Aligned.sortedByCoord.out.bam \
results/sample2/Aligned.sortedByCoord.out.bam
More from awesome-bio-agent-skills
All skills →
About this skill
What does the featurecounts-rna-counting skill do?

Counts RNA-seq reads overlapping GTF gene features. Takes sorted STAR BAMs plus GTF; outputs a per-gene tab-delimited matrix across samples. Handles strandedness (0/1/2), paired-end, multi-sample batch counting in one command, and outputs assignment statistics. Use Salmon for alignment-free quantification; use featureCounts when STAR BAMs already exist.

How do I install it?

Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill featurecounts-rna-counting --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BioTender-max/awesome-bio-agent-skills, a repository with 144 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going