tooluniverse-proteomics-analysis▌
mims-harvard/tooluniverse · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Comprehensive analysis of mass spectrometry-based proteomics data from protein identification through quantification, differential expression, post-translational modifications, and systems-level interpretation.
Proteomics Analysis
Comprehensive analysis of mass spectrometry-based proteomics data from protein identification through quantification, differential expression, post-translational modifications, and systems-level interpretation.
When to Use This Skill
Triggers: User has proteomics MS output files, asks about protein abundance/expression, differential protein expression, PTM analysis, protein-RNA correlation, multi-omics integration involving proteomics, protein complex/interaction analysis, or proteomics biomarker discovery.
COMPUTE, DON'T DESCRIBE
When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.
Core Capabilities
- Data Import: MaxQuant, Spectronaut, DIA-NN, Proteome Discoverer, FragPipe outputs
- Quality Control: Missing value analysis, intensity distributions, sample clustering
- Normalization: Median, quantile, TMM, VSN — choice depends on experimental design (see Interpretation Framework)
- Imputation: MinProb (MNAR), KNN (MAR), QRILC for missing values
- Differential Expression: Limma, DEP, MSstats for statistical testing
- PTM Analysis: Phospho-site localization, PTM enrichment, kinase prediction
- Protein-RNA Integration: Correlation analysis, translation efficiency
- Pathway Enrichment: Over-representation and GSEA for protein sets
- PPI Analysis: Protein complex detection, interaction networks via STRING/IntAct
Workflow Overview
Input: MS Proteomics Data
|
Phase 1: Data Import & QC
Phase 2: Preprocessing (filter, impute, normalize)
Phase 3: Differential Expression Analysis
Phase 4: PTM Analysis (if applicable)
Phase 5: Functional Enrichment (GO, KEGG, Reactome)
Phase 6: Protein-Protein Interactions (STRING networks)
Phase 7: Multi-Omics Integration (optional, protein-RNA correlation)
Phase 8: Generate Report
See PHASE_DETAILS.md for detailed procedures per phase.
Integration with ToolUniverse
| Skill | Used For | Phase |
|---|---|---|
tooluniverse-gene-enrichment |
Pathway enrichment | Phase 5 |
tooluniverse-protein-interactions |
PPI networks | Phase 6 |
tooluniverse-rnaseq-deseq2 |
RNA-seq for integration | Phase 7 |
tooluniverse-multi-omics-integration |
Cross-omics analysis | Phase 7 |
tooluniverse-target-research |
Protein annotation | Phase 8 |
Quantified Minimums
- At least 500 proteins quantified (human: 3,000+ is reasonable; 10,000+ is deep coverage)
- At least 3 biological replicates per condition (non-negotiable for reliable statistics)
- Filter to proteins with 2+ unique peptides (single-peptide IDs are not reported as DE)
- Statistical test: limma or t-test with Benjamini-Hochberg multiple testing correction
- Pathway enrichment: at least one method (GO, KEGG, or Reactome)
- Report must include: QC summary, DE results with volcano plot, pathway analysis, visualizations
Interpretation Framework
Starting Point: Experimental Design
Quantitative proteomics compares protein abundance. LOOK UP DON'T GUESS — always verify the experimental method, platform, and replicate count before choosing an analysis strategy.
Quantification strategy decision tree:
- Cell culture, high accuracy needed → SILAC (ratios within same MS run, most accurate, but culture-only)
- Multiple conditions, multiplexing needed → TMT/iTRAQ (up to 18-plex in one run; TMM/VSN normalization; beware ratio compression artifact that reduces observed fold-changes)
- Discovery study, flexible design → Label-free (LFQ) (intensity-based; median/quantile normalization; more missing values; wider dynamic range)
- Replicates: n < 3 = unreliable fold changes (variance cannot be estimated). Minimum n = 3 biological replicates; n >= 4 preferred for clinical samples. Never report significance from duplicates.
- FDR cutoff: Benjamini-Hochberg correction mandatory. FDR < 0.05 standard; FDR < 0.01 stringent. Never report unadjusted p-values alone.
Protein Identification Reasoning
Protein identification from MS data follows a logical chain. LOOK UP DON'T GUESS — search UniProt and STRING for protein annotation rather than inferring function from name alone.
- Peptide mass fingerprinting (PMF): Intact protein digested → measured peptide masses compared against theoretical digest of all database proteins. A match requires >=4 peptides covering >=15% of the protein sequence. Single-peptide hits are unreliable (could match multiple proteins).
- Tandem MS (MS/MS): Fragment ion spectra matched to peptide sequences via search engines (Andromeda, SEQUEST, X!Tandem). Each peptide-spectrum match (PSM) scored; only PSMs above FDR threshold count. Unique peptides (mapping to one protein) are essential — shared peptides cannot distinguish between protein isoforms.
- Protein inference: Multiple peptides → protein groups. When peptides are shared between homologs, report the protein group (not individual proteins). Use
proteins_api_searchoruniprot_search_proteinsto resolve ambiguous protein groups. - Coverage matters: 2+ unique peptides is the minimum for a confident protein ID. Proteins identified by a single unique peptide should be flagged as tentative.
Post-Translational Modification (PTM) Analysis Reasoning
PTMs (phosphorylation, ubiquitination, acetylation, glycosylation) add biological complexity beyond protein abundance.
- Site localization: A phospho-site is confidently localized only if the localization probability > 0.75 (MaxQuant) or ptmRS score > 75 (Proteome Discoverer). Ambiguous sites should not be reported as specific residue modifications.
- Enrichment is required: Without phospho-enrichment (TiO2, IMAC), only the most abundant phosphopeptides are detected (~1% of phosphoproteome). An absence of a phospho-site in non-enriched data does not mean it is absent biologically.
- Kinase prediction: If phospho-sites are identified, predict upstream kinases using motif analysis. Cross-reference with
OpenTargets_get_target_safety_profile_by_ensemblIDfor kinase-disease associations. LOOK UP kinase-substrate relationships in PhosphoSitePlus rather than guessing from sequence motif alone. - Stoichiometry: A protein can be 5% or 95% phosphorylated at a given site — this matters enormously for function but is hard to measure. Report whether data supports stoichiometry estimation or only site identification.
Differential Expression Thresholds
- Strong: padj < 0.01, FC > 2.0, ≥5 unique peptides, <20% missing
- Moderate: padj 0.01-0.05, FC 1.5-2.0, 2-5 peptides, 20-50% missing
- Weak/unreliable: padj 0.05-0.1, FC 1.2-1.5, 1-2 peptides (single-peptide proteins are unreliable), >50% missing (imputation needed)
Evidence Grading
- T1: Validated by orthogonal method (Western blot, PRM) + functional study
- T2: Significant DE (padj < 0.05, FC > 1.5) in 2+ biological replicates
- T3: Significant DE in 1 experiment, or significant but low FC
- T4: Identified but not quantified, or single peptide identification
Synthesis Questions
- How many proteins are differentially expressed? (>500 DE proteins suggests global perturbation; <50 suggests targeted effect)
- Are key pathway proteins concordantly regulated? (all subunits of a complex changing = high confidence)
- Do proteomics results correlate with transcriptomics? (low correlation is common — post-translational regulation)
- Are PTM changes driving the phenotype? (check phosphoproteomics if available)
- What is the coverage relative to the expected proteome? (human: ~10K quantified is good; <3K is limited)
Limitations
- Platform-specific: Optimized for MS-based proteomics (not Western blot quantification)
- Missing values: High missing rate (>50% per protein) limits statistical power
- PTM analysis: Requires enrichment protocols for comprehensive PTM profiling
- Absolute quantification: Relative abundance only (unless TMT/SILAC used)
- Protein isoforms: Typically collapsed to gene level
- Dynamic range: MS has limited dynamic range vs mRNA sequencing
References
Methods: MaxQuant (doi:10.1038/nbt.1511), Limma for proteomics (doi:10.1093/nar/gkv007), DEP workflow (doi:10.1038/nprot.2018.107)
Databases: STRING, PhosphoSitePlus, CORUM
Reference Files
- PHASE_DETAILS.md - Detailed procedures for each analysis phase, including report template
How to use tooluniverse-proteomics-analysis on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add tooluniverse-proteomics-analysis
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches tooluniverse-proteomics-analysis from GitHub repository mims-harvard/tooluniverse and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate tooluniverse-proteomics-analysis. Access the skill through slash commands (e.g., /tooluniverse-proteomics-analysis) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★62 reviews- ★★★★★Yusuf Srinivasan· Dec 28, 2024
We added tooluniverse-proteomics-analysis from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ira Martinez· Dec 24, 2024
tooluniverse-proteomics-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Nia Singh· Dec 20, 2024
tooluniverse-proteomics-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ganesh Mohane· Dec 16, 2024
Keeps context tight: tooluniverse-proteomics-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Nia Srinivasan· Dec 12, 2024
Registry listing for tooluniverse-proteomics-analysis matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kofi Johnson· Nov 27, 2024
I recommend tooluniverse-proteomics-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Meera Choi· Nov 19, 2024
tooluniverse-proteomics-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yuki Kapoor· Nov 15, 2024
We added tooluniverse-proteomics-analysis from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Aisha Malhotra· Nov 11, 2024
Solid pick for teams standardizing on skills: tooluniverse-proteomics-analysis is focused, and the summary matches what you get after install.
- ★★★★★Sakshi Patil· Nov 7, 2024
tooluniverse-proteomics-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 62