pride-database
Search the PRIDE Archive v3 REST API for proteomics datasets: discover projects by keyword + faceted filters (organism, instrument, disease, software), fetch project metadata, list and download RAW/PEAK/RESULT/FASTA files (with FTP/Aspera URLs), look up which projects mention a UniProt accession, and find similar projects. PRIDE v3 no longer exposes peptide/PSM-level identification endpoints — for spectrum-level data download the project's RESULT files. Use uniprot-protein-database for protein sequences; interpro-database for domain architecture.
npx skills add BioTender-max/awesome-bio-agent-skills --skill pride-database --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill enables programmatic exploration of the PRIDE Archive v3 REST API. It supports searching for projects by free-text keyword and facet filters (organism, instrument, disease, software), retrieving full project metadata, and listing or downloading associated files such as RAW, PEAK, RESULT, and FASTA. It also provides a way to look up which PRIDE projects mention a given UniProt accession and to find similar projects. For proteins and domains, it directs usage of external databases (uniprot-protein-database for sequences, interpro-database for domain architecture).
How it works
- Describes usage of PRIDE v3 endpoints: /search/projects for keyword + facet filtering, /facet/projects to discover facet values, /projects/{accession} for full metadata, /projects/{accession}/files or /files/all for project files, /files/sdrf/{accession} for SDRF, /proteins/{accession} for project mappings, and /projects/{accession}/similarProjects for similarity data. It shows example Python snippets that perform HTTP GET requests to these endpoints, parse JSON responses, and extract fields such as accession, title, submissionDate, instruments, organisms, DOIs, and file lists with their categories and public locations. It emphasizes the absence of peptide/PSM endpoints in PRIDE v3 and instructs to use RESULT files for spectrum-level data.
- It instructs how to paginate through results, how to filter on file categories (RAW, PEAK, RESULT, FASTA, OTHER), and how to compute aggregate file sizes from fileSizeBytes fields. It includes code that prints summaries like top projects, file counts by category, and SDRF availability.
- It includes explicit commands and file names like "/search/projects", "/facet/projects", "/projects/{accession}", "/projects/{accession}/files", "/files/all", "/files/sdrf/{projectAccession}", "/proteins/{accession}", "/projects/{accession}/similarProjects", and calls to external databases (uniprot-protein-database, interpro-database).
When to use it
- When you need to find published proteomics datasets by keyword and facet filters (organism, tissue, disease, instrument, software, PTM) for meta-analysis or benchmarking.
- When you want to download raw mass-spectrometry data (RAW, mzML, MGF) or pre-processed identifications (RESULT files) from a specific PRIDE project.
- When you need to determine which PRIDE projects mention a specific UniProt accession (project-level occurrence).
- When you want to discover similar projects or obtain autocomplete suggestions to guide searches.
- When you need to fetch SDRF mappings to model sample-to-MS-run relationships.
What it can touch
- The PRIDE v3 REST API endpoints as listed above. It demonstrates usage via Python's requests to interact with: /search/projects, /facet/projects, /projects/{accession}, /projects/{accession}/files, /files/all, /files/sdrf/{projectAccession}, /proteins/{accession}, /projects/{accession}/similarProjects, and /search/autocomplete.
- It references external databases for protein sequences and domain annotations: uniprot-protein-database and interpro-database.
Caveats
- PRIDE v3 has no /peptides, /psms, or /proteins?proteinAccession= endpoints; peptide/PSM data are only available in local RESULT file parsing after download.
- Endpoints return plain JSON arrays (no HAL), and some endpoints may require pagination for large results.
- No authentication is required for PRIDE v3 endpoints, but rate-limiting guidance suggests bursts under ~5 requests/second with sleeps in loops.
- The skill assumes internet access and Python package availability (requests, pandas, matplotlib).
# PRIDE Database ## Overview The PRIDE Archive (ProteomicsIDEntifications database) at EMBL-EBI is the world's largest public mass-spectrometry proteomics repository — 39,000+ projects and 3.4M+ deposited files as of 2026. Programmatic access is via a JSON REST API at `https://www.ebi.ac.uk/pride/ws/archive/v3/`. No authentication is required. The OpenAPI/Swagger spec is at `https://www.ebi.ac.uk/pride/ws/archive/v3/v3/api-docs`. PRIDE v3 returns **plain JSON arrays** for list endpoints (no HAL+JSON `_embedded` envelope) and intentionally does not expose per-peptide or per-PSM identification endpoints — for spectrum-level identifications, download the project's `RESULT` files (mzIdentML, MaxQuant txt, etc.) and parse them locally. ## When to Use - Finding published proteomics datasets by free-text keyword and facet filters (organism, tissue, disease, instrument, software, PTM) for meta-analysis or benchmarking - Downloading raw mass-spectrometry data (RAW, mzML, MGF) or pre-processed identifications (RESULT files) from a specific PRIDE project accession - Looking up which PRIDE projects mention a specific UniProt protein accession (project-level occurrence map only — no PSM/coverag
- Overview
- When to Use
- Prerequisites
- Quick Start
- Core API
- Module 1: Project Search — /search/projects
- Module 2: Faceted Filter Discovery — /facet/projects
- Module 3: Project Detail — /projects/{accession}
- Module 4: Project Files — /projects/{accession}/files + /files/all
- Module 5: SDRF File — /files/sdrf/{projectAccession}
- Module 6: Protein → Project Mapping — /proteins/{accession}
- Module 7: Discovery Helpers — Similar Projects, Autocomplete
- Module 8: Repository-Wide Counts — /projects/count, /files/count
- Key Concepts
pip install requests pandas matplotlib
What does the pride-database skill do?
Search the PRIDE Archive v3 REST API for proteomics datasets: discover projects by keyword + faceted filters (organism, instrument, disease, software), fetch project metadata, list and download RAW/PEAK/RESULT/FASTA files (with FTP/Aspera URLs), look up which projects mention a UniProt accession, and find similar projects. PRIDE v3 no longer exposes peptide/PSM-level identification endpoints — for spectrum-level data download the project's RESULT files. Use uniprot-protein-database for protein sequences; interpro-database for domain architecture.
How do I install it?
Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill pride-database --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
