Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Proteomics Pro

ASecurity

Mass-spectrometry proteomics — experimental design, data processing, quantification, and functional interpretation.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsrustgobashreactexpresstestingdatabase

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill proteomics-pro --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Proteomics Pro?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Proteomics Pro
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-proteomics-pro/badge)](https://www.skillsdirectory.com/skills/aicodedecode-proteomics-pro)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: proteomics-pro
description: Mass-spectrometry proteomics — experimental design, data processing, quantification, and functional interpretation.
category: scientific
---

## Overview

proteomics-pro covers mass-spectrometry-based proteomics from experimental design to biological
interpretation: sample preparation, LC-MS/MS acquisition strategies (DDA, DIA, targeted), database
searching, quantification (label-free, TMT/iTRAQ, SILAC), and downstream analysis including
differential expression, PTM analysis, and pathway enrichment.

Proteomics data is noisier and more incomplete than transcriptomics — missing values are the norm,
dynamic range spans orders of magnitude, and peptide-to-protein inference is genuinely ambiguous.
This skill emphasizes designs and statistics that are robust to those realities.

## When to use

- Designing a proteomics experiment: DDA vs DIA vs targeted (PRM/MRM), labeling strategy,
  replication, and randomization of run order.
- Processing raw MS data: database search (MaxQuant, FragPipe/MSFragger, Proteome Discoverer),
  FDR control, protein inference.
- Quantification: label-free (LFQ), isobaric tags (TMT), or metabolic labeling (SILAC) — trade-offs
  and analysis per method.
- Differential analysis: which proteins change, with proper missing-value and multiple-testing
  handling.
- PTM analysis: phosphorylation, ubiquitination, acetylation enrichment and site localization.
- Interpreting results: enrichment, networks, integration with transcriptomics.
- Troubleshooting: low IDs, high missingness, batch effects across MS runs.

## Core concepts

- **Acquisition modes.** DDA (data-dependent): stochastic, deep, but missing values across runs.
  DIA (data-independent): systematic, reproducible quantification, needs spectral libraries or
  library-free tools (DIA-NN). Targeted (PRM/MRM): maximum sensitivity for a predefined panel.
  DIA is now the default for discovery; DDA for library building; targeted for validation.
- **FDR at three levels.** PSM, peptide, and protein FDR (target-decoy, typically 1%). Protein
  FDR is what matters for the final list — 1% PSM FDR does not imply 1% protein FDR.
- **Protein inference problem.** Shared peptides map to multiple proteins; parsimony groups them.
  Report protein groups, not "proteins," and beware single-peptide identifications.
- **Quantification methods.** Label-free: simple, unlimited samples, needs careful normalization
  and suffers run-to-run missingness. TMT: multiplexed (up to 18-plex), great throughput, but
  ratio compression underestimates fold changes. SILAC: accurate, but limited to culturable cells
  and few conditions.
- **Missing values are structural.** In DDA, missingness correlates with low abundance (MNAR) —
  imputing with zeros or means biases results. Use methods that model censoring, or switch to DIA.
  Always report missingness rates per condition before any test.
- **Normalization.** Median centering, variance stabilization (vsn), or TMM-like approaches on
  log-intensities. Check MA plots and PCA — MS batch effects (column changes, instrument drift)
  are common and strong.
- **PTM analysis.** Enrichment (TiO2/IMAC for phospho, antibodies for ubiquitin remnant motifs)
  is mandatory — unenriched runs see almost no modified peptides. Site localization probability
  (e.g. >0.75) separates confident sites from ambiguous ones.
- **Dynamic range.** Plasma spans ~10 orders of magnitude; without depletion or fractionation you
  will measure albumin and ~200 friends. Match the sample prep to the question.

## Practical workflow

1. **Design.** ≥3 biological replicates per condition (more for clinical cohorts); randomize run
   order; include pool QCs every ~10 runs; decide DDA/DIA/targeted and labeling upfront.
2. **Sample prep.** Consistent lysis, reduction/alkylation, digestion (trypsin, check missed
   cleavages), desalting. Document everything — prep variation dominates technical variation.
3. **Acquisition.** DDA for libraries, DIA for quantification. Record instrument, gradient length,
   and method files. Run pool QCs to monitor drift.
4. **Search.** MSFragger/FragPipe or MaxQuant against the right proteome (UniProt, correct
   species + isoforms), 1% PSM/peptide/protein FDR, fixed carbamidomethylation, variable
   oxidation/acetylation. Check ID counts and missed-cleavage rates.
5. **QC.** PCA, correlation heatmaps, missingness per sample, intensity distributions. Remove or
   flag failed runs before statistics — never after seeing which removal "helps."
6. **Statistics.** Log-transform, normalize, then limma-style moderated tests or MSstats with FDR
   control. Report log2 fold changes with adjusted p-values; validate top hits by targeted MS or
   orthogonal assays.
7. **Interpretation.** Enrichment (GO/KEGG/Reactome via clusterProfiler), network analysis
   (STRING), PTM motif analysis. Integrate with RNA-seq where available — correlation is modest,
   and the discordance is often the interesting part.

Example command sketch:
```bash
fragpipe --headless --config phospho.config    # MSFragger search + Philosopher
# then in R:
library(MSstats); library(limma)
fit <- lmFit(log2(exprs), design); fit <- eBayes(fit)
topTable(fit, adjust = "BH", number = Inf)
```

## Common pitfalls

- Too few replicates (n=2 per group cannot support a t-test worth trusting).
- Running samples in group order — instrument drift becomes a "biological" difference.
- Imputing DDA missing values with zeros, creating fake significant hits.
- Reporting single-peptide protein identifications as confident.
- TMT ratio compression interpreted as small biological effect.
- Wrong database (wrong species, outdated UniProt) silently losing identifications.
- Over-interpreting GO enrichment from a biased background (use the detected proteome, not the
  whole genome, as background).

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →