plugin/skills/tooluniverse-proteomics-data-retrieval/SKILL.md
Find and retrieve proteomics datasets from MassIVE and ProteomeXchange. Search by species, keyword, or accession; retrieve detailed metadata (instruments, publications, species, PTMs studied). Use for locating public proteomics datasets to reanalyze, comparing instrument/protocol coverage across studies, and pre-download dataset evaluation.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-proteomics-data-retrievalInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Find and retrieve metadata for publicly available proteomics datasets from MassIVE and ProteomeXchange repositories. Supports searching by species, keyword, or accession, and returns detailed dataset metadata including instruments, publications, species, and post-translational modifications.
Triggers:
Use Cases:
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.
Dataset quality depends on instrument, sample preparation, and quantification method. TMT/iTRAQ (isobaric labeling) datasets have ratio compression and co-isolation interference biases that differ from label-free quantification (LFQ). DIA datasets require different analysis pipelines than DDA. Check the original publication for methods before reusing data in a meta-analysis or cross-study comparison. Instrument resolution (Orbitrap > ion trap) and acquisition mode (DIA > DDA for completeness) directly affect how many proteins are quantified and at what confidence.
| Repository | Coverage | Strengths | |-----------|----------|-----------| | MassIVE | 10,000+ datasets | Rich metadata (summaries, keywords, modifications, contacts), species filtering by taxonomy ID | | ProteomeXchange | Aggregates PRIDE, MassIVE, PeptideAtlas, jPOST, iProX | Broadest coverage, standardized PXD accessions |
Query (keyword / species / accession)
|
+-- PHASE 0: Input Resolution
| Determine search type: keyword, species, or accession lookup
|
+-- PHASE 1: Repository Search
| Search MassIVE and/or ProteomeXchange based on query type
|
+-- PHASE 2: Dataset Detail Retrieval
| Get full metadata for promising hits
|
+-- PHASE 3: Result Synthesis
Compile datasets with metadata, publications, and relevance assessment
Objective: Determine the query type and prepare appropriate search parameters.
PXD000001, MSV000079514):
ProteomeXchange_get_dataset and optionally MassIVE_get_datasetMassIVE_get_datasetMassIVE_search_datasets with species filterProteomeXchange_search_datasets with query parameterObjective: Find relevant datasets across repositories.
MassIVE_search_datasets:
page_size: Number of results to return (integer, max 100, default 10)species: NCBI taxonomy ID string to filter by species (e.g., "9606" for human)accessions (array), title, summary, species, instruments, keywordsProteomeXchange_search_datasets:
query: Optional search filter -- keyword or dataset accession (e.g., "phosphoproteomics", "PXD")limit: Max results (1-50, default 10){data: [{accession, title, species}], metadata: {source, total_returned, query}}For species-specific search:
MassIVE_search_datasets(page_size=20, species="9606") for species-filtered resultsProteomeXchange_search_datasets(limit=20) for broader listingFor keyword search:
ProteomeXchange_search_datasets(query="keyword", limit=20)For comprehensive discovery:
{data: ...} wrapper){data: [...], metadata: {...}}Objective: Get full metadata for datasets of interest.
MassIVE_get_dataset:
accession: Dataset accession -- accepts both MSV and PXD formats (e.g., "MSV000079514", "PXD003971")accessions, title, summary, species, instruments, keywords, contacts, publications, modificationsProteomeXchange_get_dataset:
px_id: ProteomeXchange identifier in PXD format (e.g., "PXD000001"){data: {px_id, title, species, identifiers, instruments, publications, file_count}, metadata: {...}}ProteomeXchange_get_dataset for file count; use MassIVE_get_dataset for richer summary/keywordsObjective: Compile and present dataset results in a structured format.
# Proteomics Dataset Search Results
**Query**: [original query]
**Date**: YYYY-MM-DD
**Repositories searched**: MassIVE, ProteomeXchange
## Summary
Found N datasets matching [criteria].
## Datasets
### 1. [Title]
- **Accession**: PXD/MSV number
- **Species**: [organism]
- **Instruments**: [MS platforms]
- **Publications**: [PubMed IDs / DOIs]
- **Modifications**: [PTMs if available]
- **Files**: [count if available]
- **Summary**: [brief description]
### 2. [Title]
...
## Data Gaps
[Note any limitations in search coverage]
| Tool | Parameter | Notes |
|------|-----------|-------|
| MassIVE_search_datasets | page_size | Integer, max 100. Default 10 |
| MassIVE_search_datasets | species | NCBI taxonomy ID as string (e.g., "9606" not 9606) |
| MassIVE_get_dataset | accession | Accepts both MSV and PXD formats |
| ProteomeXchange_search_datasets | query | Optional keyword or accession filter |
| ProteomeXchange_search_datasets | limit | Integer, 1-50 |
| ProteomeXchange_get_dataset | px_id | PXD format only (e.g., "PXD000001") |
Response Format Notes:
{data: [...], metadata: {...}}{data: {...}, metadata: {...}}| Situation | Fallback | |-----------|----------| | MassIVE search returns empty | Use ProteomeXchange search (broader coverage) | | ProteomeXchange search returns empty | Try broader/simpler query terms | | MassIVE_get_dataset fails for PXD accession | Use ProteomeXchange_get_dataset instead | | Species taxonomy ID unknown | Search ProteomeXchange by keyword (organism name) | | No keyword search results | Try individual terms instead of multi-word queries |
| Species | Taxonomy ID | |---------|-------------| | Human | 9606 | | Mouse | 10090 | | Rat | 10116 | | Zebrafish | 7955 | | Fruit fly | 7227 | | C. elegans | 6239 | | S. cerevisiae | 559292 | | A. thaliana | 3702 | | E. coli | 562 |
| Quality Indicator | Good | Acceptable | Caution | |-------------------|------|------------|---------| | Instrument | Orbitrap Exploris/Eclipse, timsTOF | Q Exactive, TripleTOF 6600 | Older LTQ, ion trap only | | Publication | Peer-reviewed with PubMed ID | Preprint or DOI only | No associated publication | | Metadata completeness | Species + instrument + PTMs + summary | Species + instrument only | Title only, no annotations |
Interpreting dataset search results:
Synthesis questions to address in the report:
species parameterDataverse_get_datasetpage_size/limit reasonable| Skill | Relationship |
|-------|-------------|
| tooluniverse-proteomics-analysis | Use retrieved datasets as input for MS data analysis |
| tooluniverse-protein-modification-analysis | Find PTM-specific datasets to complement iPTMnet annotations |
| tooluniverse-multi-omics-integration | Discover proteomics datasets for cross-omics integration |
tools
Generate the success criteria for a task or question, then review work against them. Given a task, goal, or open-ended question, decompose it into scenarios, evaluation perspectives, and fine-grained weighted YES/NO criteria using the Recursive Expansion Tree (RET) method; if work is supplied, score it criterion-by-criterion and surface what is missing or could be better. Use when asked to self-review or check your own work, judge whether a task is done well or completely, build a definition-of-done or completeness checklist, create an evaluation rubric or grading criteria, score or grade answers to a question, set up an LLM-as-judge rubric, or when the user mentions self-review, completeness check, success criteria, evaluation criteria, scoring rubric, Qworld, or the RET algorithm.
tools
Find the real protein target(s) of a peptide from its sequence — peptide target deorphanization / off-target identification, for ANY target class (GPCR, ion channel, protease, cytokine/growth-factor receptor, enzyme, integrin), not only GPCRs. Use when a peptide has a phenotype but does not bind its hypothesized target, when a peptide binds a target in one species or assay but not another, or to screen candidate targets for an orphan peptide. A target-class router steers a multi-route keyless pipeline (PROSITE/ELM motif, BLAST homology, HGNC/InterPro/GPCRdb/GtoPdb target-family enumeration, OpenTargets phenotype anchor, EnsemblCompara/Alliance cross-species reconciliation) plus optional NVIDIA-NIM co-folding (Boltz2, AlphaFold2-Multimer, OpenFold3) for structural confirmation.
tools
Install or update ToolUniverse in Claude Science — create the conda env, install the tooluniverse pip package, and (re)build the tooluniverse-research skill by fetching the current workflow library from GitHub. Use for first-time setup, upgrading the ToolUniverse version, refreshing the bundled workflows after an upstream release, or reinstalling on a new machine.
tools
Install, set up, verify, update, pin, uninstall, or troubleshoot the ToolUniverse plugin on OpenAI Codex. ALWAYS consult this skill for any of those — don't answer from memory, because the exact marketplace name (mims-harvard/ToolUniverse), the "codex plugin marketplace add" then "codex plugin add -m tooluniverse" flow, Codex's startup auto-upgrade behavior, the uvx tooluniverse MCP server, and the API-key env vars are easy to get wrong. Use it whenever someone wants to get ToolUniverse (or "the 1000+ scientific tools" / "the harvard tools") working on Codex, says the Codex plugin or its tools/skills won't load, hits a uvx or MCP-server startup error, asks how Codex updates it, wants to pin or remove it, or finds it running an old tool version — even if they never say the word "plugin". Not for the Claude Code plugin (use tooluniverse-claude-code-plugin), for running research with the tools, or for authoring new tools or skills.