Quantitative Proteomics logo

Quantitative Proteomics

Organization
awslabs
quantitative-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 from proteomics data; evaluate ratio compression; or design a proteomics study for biomarker discovery or validation. Triggers include "LFQ vs TMT", "DIA quantification", "proteomics normalization", "missing value imputation", "MNAR", "MinProb", "QRILC", "kNN imputation", "VSN normalization", "median centering", "quantile normalization", "limma proteomics", "ratio compression", "proteomics study design", "label-free quantification", "tandem mass tag", "data-independent acquisition", "DIA-NN", "Spectronaut", "MaxQuant LFQ", "proteomics differential expression", "empirical Bayes proteomics", "proteinGroups.txt", "MSFragger output", "TMT normalization code", "LFQ analysis", "proteomics pipeline R", "MaxQuant output".

Overview

Publisherawslabs
Repositoryhcls-agent-skills
Skill namequantitative-proteomics
Stars
71
Forks
14
Bundled files
Instructions only
LicenseMIT-0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by awslabs on GitHub. Read the source before you install it.

Installation

Install the Quantitative Proteomics AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/awslabs/hcls-agent-skills/tree/main/skills/quantitative-proteomics
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/awslabs/hcls-agent-skills.git /tmp/hcls-agent-skills
mkdir -p .claude/skills
cp -r /tmp/hcls-agent-skills/skills/quantitative-proteomics .claude/skills/quantitative-proteomics
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Quantitative Proteomics in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Quantitative Proteomics on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Quantitative Proteomics is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Quantitative Proteomics — Reasoning Skill

Overview

You are an expert in quantitative proteomics experimental design and statistical analysis. When the user asks about quantification strategy, imputation, normalization, or differential expression for proteomics data, apply the decision frameworks below.

Usage

  • Choose between LFQ, TMT, and DIA quantification strategies for a given study design
  • Select imputation and normalization methods based on missingness patterns and data properties

Core Concepts


Response Format

  • Lead with the direct recommendation or classification (≤3 sentences)
  • Structure as: recommendation → justification (citing specific criteria/thresholds) → caveats
  • Use tables for comparisons; bullet points for criteria lists
  • Omit background the user already knows — they asked the question
  • Target: 200-400 words unless the user requests exhaustive detail The decision trees and frameworks in this skill are for internal reasoning only. Apply them to reach your conclusion, but do not reproduce them in your response. Present only the final recommendation with supporting evidence.

1. Quantification Strategy Selection

1.1 Decision Tree

Is the goal discovery or targeted validation?
├─ Discovery (maximize coverage)
│  ├─ Sample count ≤ 20 → LFQ (label-free quantification)
│  ├─ Sample count 20–100 → TMT (multiplexed, up to 18-plex)
│  └─ Sample count any, need comprehensive coverage → DIA
├─ Targeted validation
│  └─ Use PRM (parallel reaction monitoring) or SRM/MRM
└─ Large clinical cohort (>100 samples)
   ├─ Budget allows multiplexing → TMT with fractionation
   └─ Budget constrained → DIA (single-shot)

1.2 Key Rules

  1. Never mix quantification strategies within a single study unless you have a rigorous batch-correction plan.
  2. LFQ requires match-between-runs (MBR) to reduce missingness — but MBR can introduce false transfers (~5% false positive rate at default settings).
  3. DIA library-free mode (DIA-NN ≥1.8) is simpler; library-based gives ~10% more IDs.
  4. Biological replicates matter more than technical replicates. Minimum 3 per condition; 5+ for clinical studies.
  5. TMT ratio compression: Expect 30–50% underestimation at MS2 level. True FC ≈ observed FC × 1.5–2.0. SPS-MS3 reduces compression to <10% but costs ~30% fewer IDs. Do not apply arbitrary correction without spike-in ground truth.

2. Missing Value Assessment and Imputation

2.1 Imputation Decision Tree

Assess missingness pattern:
├─ >50% missing across ALL groups → Exclude protein (unreliable)
├─ Missing predominantly in one condition
│  └─ Likely MNAR → Use left-censored methods (MinProb, QRILC)
├─ Missing scattered across conditions
│  └─ Likely MAR → Use kNN, MLE, or BPCA
└─ Mixed pattern
   └─ Hybrid: classify each protein's missingness, apply appropriate method

2.2 Imputation Methods and Pitfalls

MethodMechanismWhen to UsePitfall
MinProbMNARLow-abundance below LODUnderestimates variance
QRILCMNARLeft-censored distributionsAssumes normality
kNN (k=10)MARScattered missingnessFails if too many missing
MLE (EM)MARWell-behaved MAR dataAssumes multivariate normality
BPCAMARHigh-dimensional dataComputationally expensive

2.3 Imputation Rules

  1. Always visualize missingness first. Plot heatmap and density plots before choosing method.
  2. Filter before imputing. Remove proteins with >50% missing and contaminants.
  3. MNAR parameters: downshift = 1.8 SD, width = 0.3 SD from the observed distribution.
  4. Never impute then filter. Filtering after imputation biases the dataset.
  5. Sensitivity analysis: Run DE with and without imputation to confirm key hits are robust.

3. Normalization Strategy

3.1 Decision Tree

What is the expected biological variation?
├─ Most proteins unchanged between conditions (typical)
│  ├─ Default → Median centering (simple, robust)
│  ├─ Strong batch effects → Quantile normalization
│  └─ Variance depends on intensity → VSN
├─ Global shift expected (e.g., drug treatment affecting many proteins)
│  └─ Use spike-in standards, NOT data-driven methods
└─ TMT data
   └─ Sample loading normalization → then median centering within plex
└─ DIA data
   └─ Median centering on precursor quantities BEFORE protein roll-up

3.2 Rules

  1. Log2-transform intensities before normalization (except VSN, which includes transformation).
  2. Do NOT quantile-normalize if >30% of proteome is affected. It will mask real biology.
  3. TMT requires two-step normalization: sample loading normalization, then internal reference scaling.
  4. Batch correction (ComBat) is separate from normalization. Normalize first, then correct.
  5. Check with box plots and MA plots. Post-normalization medians should align.

4. Differential Expression Interpretation

4.1 FC Thresholds and Rules

  1. FC thresholds depend on biology. Secreted biomarkers: |log2FC| > 0.5. Intracellular: |log2FC| > 1.0.
  2. DEqMS is preferred over limma because it models variance as a function of peptide count.
  3. Always use adjusted p-values. Unadjusted p < 0.05 yields hundreds of false positives.
  4. Check for confounders. Include batch, sex, age as covariates in the linear model.

4.2 Common Mistakes

  • Wrong: Using a standard t-test for differential expression in proteomics Right: Use limma (empirical Bayes moderated t-test) or DEqMS (variance modeled by peptide count) Why: Standard t-tests have insufficient power with small sample sizes; moderated statistics borrow strength across proteins

  • Wrong: Filtering differentially expressed proteins on p-value alone without a fold-change threshold Right: Require both adjusted p-value < 0.05 and a minimum |log2FC| threshold (≥0.5 for secreted, ≥1.0 for intracellular) Why: Statistically significant but biologically trivial changes (tiny FC) are not actionable and clutter results

  • Wrong: Interpreting TMT fold changes at face value without accounting for ratio compression Right: Use SPS-MS3 quantification or apply a compression correction factor (true FC ≈ observed × 1.5–2.0) Why: MS2-level TMT systematically underestimates fold changes by 30–50% due to co-isolation interference

  • Wrong: Including contaminant and reverse-hit proteins in the analysis Right: Filter out all entries with CON__ and REV__ prefixes before normalization and statistical testing Why: Contaminants distort normalization and inflate protein counts; reverse hits are decoy sequences

  • Wrong: Imputing missing values after normalization Right: Log2-transform first, then impute, then normalize Why: Imputing on normalized data uses shifted distributions as reference, introducing systematic bias in imputed values

  • Wrong: Including proteins identified by only a single peptide in quantitative analysis Right: Require ≥2 unique peptides per protein for confident identification and quantification Why: Single-peptide IDs have high false-discovery rates and unreliable quantification


5. Study Design and QC

5.1 Sample Size Guidelines

Study TypeMinimumRecommended
Discovery3 per group5–6 per group
Biomarker validation10 per group20+ per group
Clinical proteomics20 per group50+ per group

5.2 Batch Design Rules

  1. Randomize samples across batches. Never all cases in one batch, all controls in another.
  2. Include a bridge sample in every TMT plex for cross-plex normalization.
  3. Block confounders: Balance age and sex across batches.

5.3 QC Checkpoints

CheckpointAcceptable Range
Protein IDs per run>4,000 (LFQ), >6,000 (DIA), >8,000 (TMT)
CV of intensities<20% for technical replicates
Missingness rate<30% (LFQ), <10% (TMT), <15% (DIA)
Replicate correlationPearson r >0.95 (technical), >0.85 (biological)
PCA clusteringReplicates cluster together

6. Critical Thresholds Quick Reference

  • CV > 20% across replicates → flag run for investigation
  • Proteins >50% missing in ALL groups → exclude before imputation
  • TMT ratio compression correction: true FC ≈ observed FC × 1.5–2.0 (MS2 level)
  • Quantile normalization forbidden if >30% of proteome differentially expressed
  • Phosphoproteomics: require site localization probability >0.75; normalize phospho to total protein
  • Proteomics-transcriptomics correlation is typically r = 0.4–0.6 — discordance is biologically informative (post-translational regulation)

7. Quick-Reference Decision Summary

Quantification:  Small discovery → LFQ
                 Large cohort → TMT (with SPS-MS3)
                 Comprehensive → DIA

Imputation:      Low-abundance missing → MinProb / QRILC (MNAR)
                 Random missing → kNN / MLE (MAR)
                 Mixed → Hybrid approach

Normalization:   Default → Median centering
                 Batch effects → Quantile
                 Heteroscedastic → VSN
                 Global shift → Spike-in standards

DE Testing:      Default → limma (empirical Bayes)
                 Proteomics-aware → DEqMS
                 Threshold → adj.p < 0.05, |log2FC| > 1.0

Pipeline Reference

Input Formats

SourceFileKey Columns
MaxQuantproteinGroups.txtProtein IDs, Gene names, LFQ intensity *, iBAQ, Reverse, Potential contaminant
MSFraggercombined_protein.tsvProtein, Gene, Intensity, Spectral Count
Proteome DiscovererProteins.txtAccession, Description, Abundance *
DIA-NNreport.pg_matrix.tsvProtein.Group, sample columns with quantities

TMT Sample Loading Normalization + Internal Reference Scaling

r
# TMT: Sample Loading Normalization + Internal Reference Scaling
col_sums <- colSums(mat, na.rm = TRUE)
scaling_factors <- median(col_sums) / col_sums
mat_sln <- sweep(mat, 2, scaling_factors, "*")

# IRS using bridge channel (e.g., pooled reference in 131C)
bridge <- mat_sln[, grep("131C", colnames(mat_sln))]
irs_factors <- apply(bridge, 1, median, na.rm = TRUE)
mat_irs <- mat_sln / irs_factors  # row-wise scaling across plexes

When limma Fails

ScenarioProblemUse Instead
<3 replicates per groupVariance estimation unreliableRankProd (rank-based, no variance estimate needed)
Unbalanced design (e.g., 3 vs 8)Pooled variance biased toward larger groupMixed models: lme4 + lmerTest
Repeated measures / longitudinalCorrelated samples violate independencelimma::duplicateCorrelation() or dream() from variancePartition
>2 groupsPairwise t-tests inflate FDRlimma::contrasts.fit() with proper contrast matrix
Paired samples (e.g., tumor vs adjacent normal)Must account for patient effectInclude patient as blocking factor in design matrix

Parameter Reference

ParameterDefaultRangeNotes
MinProb quantile (q)0.010.001–0.05Lower = more conservative imputation
MinProb downshift (σ)1.81.4–2.0Standard deviations below mean
MinProb width0.30.2–0.5Fraction of observed σ for imputed spread
kNN k105–15Higher k = smoother but slower
kNN rowmax0.50.3–0.7Max fraction missing per row allowed
Missingness filter70% in ≥1 group50–100%Stricter = fewer proteins, less noise
log2FC threshold1.00.5–2.0Adjust to biological context
adj.p threshold0.050.01–0.10.01 for stringent discovery
Unique peptides min21–3≥2 required for confident ID

When NOT to Use This Skill

  • Validating biomarker candidates for clinical assay development (needs assay chemist)
  • When sample prep issues dominate variance (pre-analytical problem, not analytical)
  • Absolute quantification requiring isotope-labeled standards

When to Escalate to a Human Expert

  • When missing data exceeds 50% and imputation assumptions are untestable
  • Before publishing quantitative claims from single-batch experiments
  • When results require mass spectrometry method development expertise

8. Troubleshooting Common Issues

SymptomLikely CauseSolution
Very few protein IDs (<2,000)Poor sample prep or instrument issueCheck TIC, re-run QC standard
All samples cluster by batch in PCABatch effect dominates biologyApply ComBat or limma removeBatchEffect
No significant DE proteinsUnderpowered study or wrong testCheck sample size, use DEqMS, relax FC threshold
Too many significant hits (>50%)Normalization failure or global shiftCheck box plots, consider spike-in normalization
Imputation creates artificial clustersMNAR imputation too aggressiveReduce downshift, try kNN, or filter more stringently
TMT fold changes smaller than expectedRatio compressionUse SPS-MS3 or apply compression correction
High CV between replicates (>30%)Sample prep variabilityReview digestion protocol, add QC samples

Frequently asked questions

What does the Quantitative Proteomics AI skill do?

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 from proteomics data; evaluate ratio compression; or design a proteomics study for biomarker discovery or validation. Triggers include "LFQ vs TMT", "DIA quantification", "proteomics normalization", "missing value imputation", "MNAR", "MinProb", "QRILC", "kNN imputation", "VSN normalization", "median centering", "qua...

Why use Quantitative Proteomics on TypingMind?

Because you install it once and use it with any model. Quantitative Proteomics is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Quantitative Proteomics in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/awslabs/hcls-agent-skills/tree/main/skills/quantitative-proteomics. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Quantitative Proteomics?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Quantitative Proteomics?

As many as you like. As long as a model supports skills, you can use Quantitative Proteomics with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Quantitative Proteomics AI skill free?

Yes. It is published on GitHub by awslabs under the MIT-0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇