Skip to content
Skills Library
Science & research · Analysis

normalizing-proteomics-data

/normalizing-proteomics-data

Evaluate the need for and perform normalization of protein-level proteomics intensity data. Use when (1) assessing whether normalization is needed, (2) selecting normalization methods, (3) applying it. Does NOT cover batch correction or imputation

Licence
Apache-2.0
Last repository change
14.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Evaluate the need for and perform normalization of protein-level proteomics intensity data. Use when (1) assessing whether normalization is needed, (2) selecting normalization methods, (3) applying it. Does NOT cover batch correction or imputation

Original author description

Evaluate the need for and perform normalization of protein-level proteomics intensity data. Use when (1) assessing whether normalization is needed, (2) selecting normalization methods, (3) applying it. Does NOT cover batch correction or imputation

How it works

  1. Checklist
  2. Workflow
Original SKILL.md headings · 66 lines, 484 words
SKILL.md preview
---
name: normalizing-proteomics-data
description: Evaluate the need for and perform normalization of protein-level proteomics intensity data. Use when (1) assessing whether normalization is needed, (2) selecting normalization methods, (3) applying it. Does NOT cover batch correction or imputation
---

# Normalizing Proteomics Data

Normalization makes samples comparable by aligning their overall intensity distributions. It serves three main goals:

- Aligning intensities across samples, which removes technical variation caused by differences in sample loading amounts or instrument behavior.
- Preserving feature ranks within each sample, so the relative ordering of features is not distorted.
- Stabilizing variance (i.e., addressing heteroscedasticity), which most downstream methods require because they assume homoscedastic noise.

After normalization, a feature's intensity should reflect its relative biological abundance within a sample and remain comparable across samples.

Common normalization methods include:

| Priority | Method                  | Input scale |
| --- | --- | --- | --- |
| 1        | Total sum normalization | Simple offset correction; robust baseline                                            | Linear-scale intensities                |
| 2        | Quantile Normalization                | Distributions should be identical across samples                                     | Log-transformed intensities  |
| 3        | Variance Stabilizing Normalization (VSN)                     | Need variance stabilization of low-abundant features; performs well in differential expression benchmarks | Linear-scale intensities              |
| 4        | LOESS/RLR               | Suspect intensity-dependent bias (non-linear or linear)                              | Log-transformed intensities  |

**Recommendation**: Start with log2 only. If PCA shows intensity-driven structure, try total sum normalization, then VSN.

## Checklist

Copy this checklist and track progress:

```
Analysis step progress:
- [ ] Verify log2 transformation
- [ ] Assess Normalization Need
- [ ] Data dependent: Select Additional Normalization
- [ ] Evaluate Normalization Effect
      If Successful: Proceed to "Batch correction"
      If Unsuccessful: Return to Step 3 (Select normalization method 2, 3, etc.)
```

## Workflow

### 1. Apply Log Transformation (Always Recommended)

Handle zeros as missing before log transformation

### 2. Assess Normalization Need

Check if total summed intensity drives variation:

- Visualize PCA colored by total intensity
- Compute correlation between PC1 and log10(total intensity per sample)
- If total intensity correlates strongly with major PCs, perform normalization attempts

### 3. Select Additional Normalization (if necessary)

**When total intensity drives variance**, try the normalization methods from the normalization method table in the order of their priority.

> [!Important] Different normalization methods assume different data distributions. Ensure _a priori_, that the current data distribution meets the assumptions of the normalization method based on the column `Input scale` in the table. If you select a normalization method that assumes linear-scaled intensities, you need to go back to linear-scaled intensities and apply these normalization methods to the raw intensities, then log-transform the normalized data.

### 4. Evaluate Normalization Effect (Required)

It is critical that you assess the performance of the normalization, as benchmarks showed that many normalization methods perform worse than log2 alone on spike-in datasets and LFQ-normalized data (e.g., directLFQ) may not require additional normalization.

**Pooled Median Absolute Deviation (PMAD)** Average median absolute deviation across all features within a biological condition should drop

- **Correlation of principal components with total intensity** should drop.

- **Pearson correlation between technical replicates** should increase or stay stable

Versions

The database has no other skills named normalizing-proteomics-data.

Database snapshot: 13.11.2026 · package version 2a48f8296ef4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100imputing-proteomics-data
    Impute missing values in protein-level proteomics data matrices. Use when (1) preparing proteomics data for downstream analyses requiring complete matrices (PCA, batch correction), (2) evaluating whether imputation is needed, (3) selecting appropriate imputation methods, or (4)…
  • 100performing-proteomics-quality-control
    Perform quality control for protein-level proteomics data. Use when filtering outlier samples or low-evidence features before downstream analysis. Covers PSM artifact removal, sample QC, feature-level filtering. Does NOT cover normalization, batch correction, or imputation.
  • 100analyze-proteomics
    Inspect protein expression matrices with SDRF metadata, select traceable Mokume normalization, imputation, and differential-expression candidates, and evaluate those candidates through the bundled Mokume MCP server. Use for proteomics method selection, spike-in benchmarking, DEA…
  • 100quantitative-proteomics
    Reason about quantitative proteomics experiment design and data analysis strategy. Use when the user asks to choose between LFQ, TMT, and DIA quantification; select an imputation method for missing values; pick a normalization strategy; interpret differential expression results…
  • 90tooluniverse-proteomics-analysis
    Analyze mass spectrometry proteomics data including protein quantification, differential expression, post-translational modifications (PTMs), and protein-protein interactions. Processes MaxQuant, Spectronaut, DIA-NN, and other MS platform outputs. Performs normalization,…
  • 100gene-protein-expression-matrix-normalization
    Use when normalizing bulk gene or protein expression matrices with log2 transform, z-score standardization, or min-max scaling before downstream visualization or exploratory analysis. NOT for count-model normalization such as TPM/DESeq2 size factors, batch correction, or single-cell preprocessing.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.