SkillAgentSearch skills...

omics-analysis-guide

Three-tiered approach to omics data analysis (transcriptomics, proteomics) covering validated pipelines, standard workflows, and custom methods

Install / Use

npx skills add jaechang-hits/SciAgent-Skills --skill omics-analysis-guide

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

91/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of omics-analysis-guide

omics-analysis-guide scores 91/100 on our quality scale, 1091st of 2,771 Automation skills we index (top 40%).

Its SKILL.md is 28 KB long, well organised into 51 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.

It has 367 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so omics-analysis-guide is actively maintained.
  • Our last check on 2026-11-20 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

omics-analysis-guide compared with similar skills

All 4 of these similar skills score higher than omics-analysis-guide; compare them before choosing.

SkillScoreStarsUpdatedFormat
omics-analysis-guide (this skill)by jaechang-hits913673mo agoSKILL.md
Agent-Reachby Panniantong100113.3k12d agoCLAUDE.md
rufloby ruvnet10082.1ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.2k10d agoCLAUDE.md
Scraplingby D4Vinci100104.4k2d agoMCP Server

Frequently asked questions

How do I install omics-analysis-guide?
Run npx skills add jaechang-hits/SciAgent-Skills --skill omics-analysis-guide. The install tabs above show the steps for each supported agent.
Which AI agents does omics-analysis-guide work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is omics-analysis-guide safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is omics-analysis-guide still maintained?
The repository was last updated about 3 months ago, so omics-analysis-guide is actively maintained.

name: omics-analysis-guide description: Three-tiered approach to omics data analysis (transcriptomics, proteomics) covering validated pipelines, standard workflows, and custom methods license: open

Omics Data Analysis Guide: Three-Tiered Approach


Metadata

Short Description: Comprehensive guide for analyzing omics data (transcriptomics, proteomics) using validated pipelines, standard workflows, or custom analysis methods.

Authors: HITS

Version: 1.0

Last Updated: December 2025

License: CC BY 4.0

Commercial Use: Allowed

Citations and Acknowledgments

If you use validated pipelines or tools (Option 1):

  • Citation: Always cite the original publication associated with each tool or pipeline
  • Acknowledgment: Cite the specific tools and methods used in your analysis

If you use standard workflows (Option 2):

  • Acknowledgment Statement: "Analysis performed using standard omics data analysis workflows and best practices"
  • Citation for RNA-seq analysis: Dobin A, et al. STAR: ultrafast universal RNA-seq aligner. Bioinformatics. 2013;29(1):15-21. PMID: 23104886
  • Citation for proteomics: Cox J, Mann M. MaxQuant enables high peptide identification rates, individualized p.p.b.-range mass accuracies and proteome-wide protein quantification. Nat Biotechnol. 2008;26(12):1367-72. PMID: 19029910

Overview

This guide provides a three-tiered approach to omics data analysis, prioritizing validated pipelines and standard workflows before moving to custom analysis. Always start with Option 1 and proceed to subsequent options only if needed.

The guide covers:

  • Transcriptomics: Bulk RNA-seq
  • Proteomics: Pre-quantified protein abundance data (similar to bulk RNA-seq analysis)

Note: This guide focuses on analysis of already-quantified data. For raw data processing (alignment, quantification), refer to specialized tools and pipelines.


Key Concepts

Validated Pipeline vs. Standard Workflow vs. Custom Analysis

A validated pipeline is a specific tool with peer-reviewed benchmarking data demonstrating performance on data like yours (e.g., DESeq2 for RNA-seq counts, MaxQuant for label-free proteomics). A standard workflow is the canonical sequence of QC → normalization → statistical test → multiple-testing correction assembled from accepted community practice but tuned to your specific dataset. Custom analysis is bespoke statistical or computational modeling required when neither prior tier covers the data type or research question. The progression Option 1 → Option 2 → Option 3 trades reproducibility for flexibility — always exhaust earlier tiers first.

Missing Value Mechanisms (MCAR / MAR / MNAR)

Missing data in omics arises from three distinct mechanisms with different correct treatments. MCAR (Missing Completely At Random) means missingness is independent of any value — safe to impute with mean, median, or KNN. MAR (Missing At Random) means missingness depends on observed variables but not the unobserved value — KNN or model-based imputation is appropriate. MNAR (Missing Not At Random) means missingness depends on the missing value itself, typical in proteomics where low-abundance proteins drop below detection — requires left-censored imputation (minprob/QRILC) below the detection limit. Choosing the wrong mechanism systematically biases downstream statistics.

Test Assumptions and Test Selection

Parametric tests (Student's t-test, Welch's t-test) assume approximate normality and (for Student's) equal variances; they have higher power than non-parametric tests when assumptions hold. Non-parametric tests (Mann-Whitney U, permutation) make weaker assumptions and are correct under skewed distributions or small n, at the cost of statistical power. The choice depends on sample size (n < 10 favors non-parametric), normality (Shapiro-Wilk / Anderson-Darling at the feature level), variance homogeneity (Levene's test), and outlier prevalence.

Multiple Testing Correction

Omics analyses test thousands of features simultaneously. Without correction, expected false positives at α=0.05 across 20,000 genes is 1,000. Family-wise error rate (FWER) corrections like Bonferroni control the probability of any false positive but are conservative. False discovery rate (FDR) corrections like Benjamini-Hochberg control the expected proportion of false positives among reported significant features and are the standard for omics. Always report adjusted p-values, never raw p-values, when calling significance.


Decision Framework

Use this tree to choose the right analysis tier for your data:

              Have you searched for a validated
              pipeline matching your data type?
                            │
              ┌─────────────┴─────────────┐
              │                           │
             NO                          YES
              │                           │
              ▼                           ▼
       Run Method 1            Did you find a validated
       (literature) AND        pipeline with benchmarks
       Method 2 (consortia     matching your data type
       workflows) FIRST        and biological question?
                                          │
                                  ┌───────┴───────┐
                                  │               │
                                 YES              NO
                                  │               │
                                  ▼               ▼
                          OPTION 1:        Is your data a
                          Use validated    common type
                          pipeline         (RNA-seq counts,
                          (e.g., DESeq2,   pre-quantified
                          edgeR, MaxQuant) proteomics)?
                                                  │
                                          ┌───────┴───────┐
                                          │               │
                                         YES              NO
                                          │               │
                                          ▼               ▼
                                  OPTION 2:        OPTION 3:
                                  Standard         Custom analysis
                                  workflow         (consult
                                  (QC → norm →     statistician;
                                   test → FDR)     document
                                                   thoroughly)

Decision Table

| Data type | Sample size | Has validated pipeline? | Recommended tier | Specific tool / approach | |-----------|-------------|--------------------------|------------------|--------------------------| | Bulk RNA-seq counts | n ≥ 3/group | Yes (DESeq2, edgeR) | Option 1 | DESeq2 (negative binomial, default FDR < 0.05) | | Pre-quantified proteomics, normal-distributed | n ≥ 5/group | Sometimes | Option 1 if pipeline matches; else Option 2 | limma or t-test + BH-FDR | | Pre-quantified proteomics, MNAR-heavy | n ≥ 5/group | No (mechanism-specific) | Option 2 | minprob imputation → t-test or Mann-Whitney → BH-FDR | | Small-cohort omics (n < 5) | n < 5 | Rarely | Option 2 with caution | Permutation test, report effect sizes; flag results as preliminary | | Multi-omics integration | Variable | Limited | Option 3 | MOFA, DIABLO, or custom Bayesian model | | Novel data type (e.g., spatial multi-omics) | Variable | No | Option 3 | Build from first principles; cross-validate | | Time-series omics | n per timepoint | Sometimes (maSigPro, ImpulseDE2) | Option 1 if available; else Option 3 | maSigPro for transcriptomics; custom for proteomics |


Option 1: Search for Validated Analysis Methods (Recommended First)

1.1 Search for Validated Analysis Pipelines

IMPORTANT: You MUST complete BOTH Method 1 AND Method 2 before proceeding to Option 2. Do not skip Method 2 even if Method 1 finds no results.

Method 1: Literature Search for Best Practices

Search for validated analysis methods using web search tools or literature databases (PubMed, Google Scholar).

Search queries to try (use multiple):

"[DATA_TYPE]" "[ANALYSIS_TYPE]" validated pipeline best practices
"[DATA_TYPE]" analysis workflow "[ORGANISM]" published
"[DATA_TYPE]" "[TOOL_NAME]" validation benchmark comparison

Example for bulk RNA-seq:

"RNA-seq" "differential expression" validated pipeline human
"DESeq2" "edgeR" comparison validation RNA-seq

Example for proteomics:

"proteomics" "differential abundance" analysis validated methods
"proteomics" normalization imputation best practices

What to search for in results:

  • Published papers with validated analysis pipelines
  • Benchmark studies comparing different tools
  • Best practices guides from major consortia (e.g., ENCODE, TCGA)
  • Tool documentation with validation data

IMPORTANT: Spend adequate time searching literature. Look through at least the first 10-15 search results and check supplementary materials of relevant papers.

Method 2: Review Standard Analysis Workflows

Review established workflows from major consortia and publications:

  • ENCODE RNA-seq analysis pipeline
  • TCGA analysis protocols
  • Published benchmark studies

What to Do with Results:

If you find validated pipelines or methods:

  1. Record the pipeline/method name and version
  2. Note the reference: Record the publication DOI/PubMed ID
  3. Record validation details: Benchmark results, recommended parameters, any limitations
  4. Document the workflow: Step-by-step analysis procedure

Example result format:

Data Type: Bulk RNA-seq
Analysis Goal: Differential expression
Pipeline: DESeq2 (v1.40.0)
Reference: Love MI, et al. Moderated estimation of fold change and dispersion for RNA-seq data with DESeq2. Genome Biol. 2014;15(12):550. PMID: 25516281
Validation: Validated in multiple benchmark studies, recommended for count data
Parameters: Default parameters, FDR < 0.05, log2FC > 1

If no validated pipelines found in BOTH Method 1 AND Method 2: Only then proceed to Option 2: Use Standard Workflows


Option 2: Use Standard Analysis Workflows

When to Use This Option?

  • No validated pipelines found for your specific data type
  • Need to build a custom workflow from standard components
  • Working with common data types (RNA-seq, proteomics)
  • Want to follow community best practices

2.1 Overview of Standard Workflows

RNA-seq (Bulk):

  1. Quality control
  2. Normalization and filtering (if count data, use DESeq2/edgeR normalization)
  3. Statistical analysis (differential expression)
  4. Multiple testing correction
  5. Functional enrichment (optional)

Proteomics (Pre-quantified):

  1. Quality control
  2. Missing value assessment and imputation
  3. Normalization
  4. Batch correction (if needed)
  5. Statistical analysis (differential abundance)
  6. Multiple testing correction

2.2 Essential Quality Control Steps

CRITICAL: Quality control must be performed before any statistical analysis. Poor data quality will lead to unreliable results regardless of statistical methods used.

Sample-Level Quality Control

Check for outlier samples:

  • Use PCA + Isolation Forest to detect outlier samples
  • Standardize data, perform PCA, then apply Isolation Forest
  • Remove or investigate samples identified as outliers

Check sample correlation:

  • Calculate correlation matrix between samples
  • Low correlations (< 0.5) may indicate poor quality samples
  • Remove samples with consistently low correlation

Check for batch effects:

  • Use PCA + silhouette score to assess batch separation
  • If silhouette score > 0.3, strong batch effect detected
  • Apply batch correction (ComBat or similar) if needed

Feature-Level Quality Control

Assess missing value patterns:

  • Calculate missing percentage per feature

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars367
CategoryAutomation
Updated2mo ago
Forks36

Languages

Python

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium