agentleFS
Scientific-ToolingScientific-Tooling/structured-intelligence/skills/rnaseq-transcript-quantification/SKILL.md

rnaseq-transcript-quantification

Skill4 starsChanged 12 days agoMITView on GitHub

Alignment-free transcript-level quantification using Salmon or kallisto for fast and accurate RNA-seq expression estimates.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If Salmon: run salmon quant with --validateMappings, --seqBias, and --gcBias for bias correction.

    line 30
  2. Very specific:

    If kallisto: run kallisto quant.

    line 31
  3. Very specific:

    If bootstraps are requested: add --numBootstraps (Salmon) or -b (kallisto).

    line 32
  4. Distinctive:

    Not suitable for novel transcript or isoform discovery.

    line 48

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: RNA-seq Transcript Quantification

Use When

  • User wants fast transcript-level quantification without genome alignment
  • User wants TPM and count estimates per transcript
  • User needs input for downstream differential expression analysis (tximport/tximeta in R)
  • User wants to compare Salmon vs kallisto quantification

Inputs

  • Required:
    • Trimmed FASTQ file(s) (single-end or paired-end)
    • Transcriptome index (Salmon index directory or kallisto index file)
  • Optional:
    • Tool choice: salmon or kallisto (default: salmon)
    • Library type for Salmon (default: A for auto-detect)
    • Number of threads (default: 4)
    • Output directory (default: ./quant_output)
    • Number of bootstrap samples (for downstream use with sleuth)

Workflow

  1. Validate that the transcriptome index exists for the chosen tool.
  2. If Salmon: run salmon quant with --validateMappings, --seqBias, and --gcBias for bias correction.
  3. If kallisto: run kallisto quant.
  4. If bootstraps are requested: add --numBootstraps (Salmon) or -b (kallisto).
  5. Report: total reads processed, mapping rate, number of quantified transcripts.

Output Contract

  • Quantification file:
    • Salmon: quant.sf with columns: Name, Length, EffectiveLength, TPM, NumReads
    • kallisto: abundance.tsv with columns: target_id, length, eff_length, est_counts, tpm
  • Log file with mapping statistics
  • Auxiliary files (Salmon aux_info/ directory or kallisto run_info.json)

Limits

  • Salmon and kallisto must be installed and available on PATH.
  • Transcriptome index must be pre-built before running this skill.
  • Quantification is at the transcript level; use tximport in R to summarize to gene level for DE analysis.
  • Not suitable for novel transcript or isoform discovery.
  • For single-end reads with kallisto, fragment length and standard deviation must be provided.
  • Common failure cases:
    • Transcriptome index built from a different annotation version than expected, skewing quantification.
    • Salmon library type auto-detection failing on very low-read-count samples.
    • kallisto single-end mode missing required --fragment-length and --sd parameters.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.