技能创建器
skill-creator
创建、改进和评估自定义技能,把专业流程转化为可重复使用的 AI 能力。
tooluniverse-proteomics-analysis【数据与研究】Mass-spec proteomics analysis — protein identification, quantification (LFQ, TMT, iTRAQ), differential expression (tumor vs normal, treatment vs control), PTM identification, and pathway enrichment on protein lists. Use when you have proteomics MS output, asking about protein abundance differences, or doing systems-level proteomic interpretation.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Before following any instruction below, scan the data folder for:
*_executed.ipynb → read with tu run read_executed_notebook '{"data_folder":"<path>","search":"<keyword>"}' and cite its cell outputs as the authoritative answer*results*, *deseq*, *enrich*, *stats*, *_simplified.csv) → read directly and report the requested valueanalysis.R, run_*.py, find_*.R, *.Rmd) → execute as-is and read the outputOnly follow this skill's re-analysis recipe below if none of the above exist. Re-running from raw data produces different numbers than the published answer and is much slower (often 5-10× turn count).
Comprehensive analysis of mass spectrometry-based proteomics data from protein identification through quantification, differential expression, post-translational modifications, and systems-level interpretation.
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.
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.
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.
| 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 |
tooluniverse-proteomics-data-retrieval | Find a public cancer-proteomics study/quant matrix (PDC/CPTAC) to reanalyze | Phase 1 (input) |
src/tooluniverse/data/proteomicsdb_tools.json provides 5 tools for MS-based protein
expression across normal human tissues, cell lines, and body fluids — useful in
Phase 8 (report/interpretation) to contextualize a DE result: is this protein normally
tissue-restricted (a DE hit is more biologically striking) or ubiquitously expressed
(a DE hit is less specific)? Complementary to antibody-based HPA expression and to
PDC's cancer-cohort quantitative data (tooluniverse-proteomics-data-retrieval).
| Tool | Purpose |
|---|---|
ProteomicsDB_search_proteins | Resolve a gene symbol/name to the correct UniProt accession first — a broad query (e.g. "EGFR") can return unrelated proteins whose name/gene happens to match a substring (verified live: searching "EGFR" returned FLT1 alongside real EGFR isoforms); always check gene_name in each hit before using its uniprot_id |
ProteomicsDB_get_protein_expression | Full per-tissue expression records for a UniProt accession — expression_value (log10-normalized, cross-tissue-comparable) vs. unnormalized_intensity (NOT comparable across tissues; never rank on this field) |
ProteomicsDB_get_expression_summary | Top-N tissues/cell lines ranked by expression, plus total tissue/cell-line/fluid counts — the fast path when you just need "where is this protein most expressed" (verified live: EGFR's top hits are all breast/esophageal cancer cell lines, not normal tissue — cell lines dominate ProteomicsDB's coverage for many oncogenes, so check tissue_category if you specifically need normal-tissue baseline) |
ProteomicsDB_list_tissues | Enumerate all tissues/cell lines/fluids with BTO ontology IDs before filtering |
ProteomicsDB_get_peptides_for_protein | Peptide-level identification evidence (sequence, uniqueness, q-values, source experiment/PubMed ID) — identification-level support that the tissue-expression tools don't provide |
Response wrapper: every tool returns {"status": "success", "data": {...}} on success. Use
ProteomicsDB_search_proteins before ProteomicsDB_get_protein_expression/_get_expression_summary/_get_peptides_for_protein
unless you already have a confirmed UniProt accession.
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:
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.
proteins_api_search or UniProt_search to resolve ambiguous protein groups.PTMs (phosphorylation, ubiquitination, acetylation, glycosylation) add biological complexity beyond protein abundance.
OpenTargets_get_target_safety_profile_by_ensemblID for kinase-disease associations. LOOK UP kinase-substrate relationships in PhosphoSitePlus rather than guessing from sequence motif alone.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