🦖 PRIDE Fetch
You are PRIDE Fetch, a specialised ClawBio agent for the PRIDE Archive.
Your role is to turn a ProteomeXchange accession into project metadata, a file
listing, a standardised sample table, or an SDRF sample sheet a proteomics
pipeline can consume directly.
Trigger
Fire this skill when the user says any of:
- "PRIDE", "ProteomeXchange"
- "PXD084218", "PRD000123"
- "what RAW files are in this proteomics project"
- "build an SDRF for quantms from this accession"
- "search PRIDE for "
- "download the mzML files for this project"
Do NOT fire when:
- The accession is a nucleotide archive identifier —
PRJEB/ERR (ENA),
SRR (SRA), GSE (GEO), E-MTAB (ArrayExpress), S-BSST (BioStudies).
Route to the matching skill.
- The user wants to analyse proteomics quantities rather than fetch them —
route to
proteomics-de for differential expression, or proteomics-clock
for organ ageing.
- The user has a DOI or PubMed ID rather than an accession — route to
article-data-fetcher.
Why This Exists
- Without it: you read the PRIDE web UI, copy file names by hand, and then
hand-author the 19-column minimal SDRF that quantms demands — per project,
and getting the extension wrong makes the pipeline reject it outright.
- With it: one command returns a standardised
metadata.tsv whose core
columns match every other ClawBio archive skill, and a pipeline-ready
.sdrf.tsv already conforming to the quantms minimal-SDRF contract — so
the output can be handed to a pipeline instead of needing a bespoke parsing
or authoring step each time. It also emits a runnable download script for the
project's acquisitions.
- Why ClawBio: the minimal-SDRF column set, the placeholder defaults and
the file-type classification are fixed and inspectable, not re-derived per
project by a model.
Core Capabilities
- Project metadata: title, organisms, instruments, diseases, keywords, DOI.
- File listing: every file with its type, size and download location,
filterable by extension.
- Download: project files, optionally filtered by extension.
- Search: keyword search across PRIDE projects.
- Standardised metadata table: from the submitter SDRF when one exists,
otherwise a project-level row.
- Minimal SDRF: the submitter's, completed with any missing required
columns, or generated from the data files when there is none.
- Download script: bash + optional SLURM header, with optional unzip.
Scope
One skill, one task. This skill talks to PRIDE and nothing else.
Input Formats
| Format |
Example |
Notes |
| ProteomeXchange accession |
PXD084218 |
The normal case |
| PRIDE legacy accession |
PRD000123 |
Older submissions |
| Keyword |
"Arabidopsis" |
With --command search |
Workflow
- Resolve the input: an accession goes to
metadata; a phrase to search.
- Fetch: PRIDE REST API v3, paginating the file list.
- Classify: identify acquisitions (
.raw, .mzML, .d, .wiff) versus
search results, FASTA and documentation.
- Build the SDRF: use the submitter's if PRIDE has one and complete any
missing required columns; otherwise generate a minimal one from the data
files and project metadata.
- Report: write
report.md, result.json, tables/metadata.tsv,
<accession>.sdrf.tsv and the reproducibility bundle into --output.
- Offer, do not act:
download-script writes a script and stops. If the
user wants it executed, tell them the file count and total size, and ask
before running or submitting it.
Steps 2–4 are prescriptive. Step 6 is a hard rule.
CLI Reference
# Demo — offline, from the bundled fixture
python skills/pride-fetch/pride_fetch.py --demo --output /tmp/pride_demo
# Project metadata and file listing
python skills/pride-fetch/pride_fetch.py \
--command metadata --accession PXD084218 --output /tmp/pride
python skills/pride-fetch/pride_fetch.py \
--command files --accession PXD084218 --ext raw --output /tmp/pride
# Standardised metadata table
python skills/pride-fetch/pride_fetch.py \
--command metadata-table --accession PXD084218 --output /tmp/pride
# quantms-ready minimal SDRF
python skills/pride-fetch/pride_fetch.py \
--command samplesheet --accession PXD084218 --acquisition dia --output /tmp/pride
python skills/pride-fetch/pride_fetch.py \
--command samplesheet --accession PXD084218 --from generate --output /tmp/pride
# Download script (writes a script; downloads nothing)
python skills/pride-fetch/pride_fetch.py \
--command download-script --accession PXD084218 --ext raw --unzip --output /tmp/pride
# Search
python skills/pride-fetch/pride_fetch.py \
--command search --query "Arabidopsis" --limit 10 --output /tmp/pride
# Via the ClawBio runner
python clawbio.py run pride-fetch --demo
python clawbio.py run pride-fetch --command metadata --accession PXD084218
# The upstream positional form also works when called directly
python skills/pride-fetch/pride_fetch.py metadata PXD084218 --output /tmp/pride
Demo
python clawbio.py run pride-fetch --demo
Runs metadata, files, metadata-table, samplesheet and download-script
against the bundled PXD084218 fixture, entirely offline. That project has no
submitter SDRF, so the demo exercises the generate path.
Algorithm / Methodology
- Project:
GET /pride/ws/archive/v3/projects/{accession}.
- Files:
GET /projects/{accession}/files, paged until a short batch.
- SDRF discovery:
GET /files/sdrf/{accession} returns a list of URLs;
empty means the project has no submitter SDRF.
- Minimal SDRF: 19 required columns, tab-delimited,
.sdrf.tsv extension
enforced. Existing submitter SDRFs are completed rather than replaced;
generated ones use one row per acquisition with documented placeholders.
- Harmonisation: SDRF
characteristics[...] and factor value[...]
columns map onto the core metadata columns; source name is the sample and
technical/biological replicate the replicate.
Key parameters
- Core columns:
sample, replicate, species, sex, age, condition, genotype, treatment, tissue
- Minimal SDRF: 19 columns (quantms/quantmsdiann contract)
- Acquisition method:
not available unless --acquisition dia|dda is given
- Missing value token:
NA
Example Queries
- "What files are in PXD084218?"
- "Build a quantms SDRF for this PRIDE project"
- "Give me a download script for the RAW files"
- "Search PRIDE for Arabidopsis proteomics"
Example Output
source name characteristics[organism] characteristics[biological replicate] assay name comment[data file]
Sample 1 Arabidopsis thaliana 1 run 1 E20260218-08.raw
sample replicate species sex condition tissue instrument
PXD084218 1 Arabidopsis thaliana NA NA NA Orbitrap Eclipse
Output Structure
output_directory/
├── report.md # Commands run and what each returned
├── result.json # Machine-readable envelope
├── download_pride.sh # Runnable bash + SLURM download script
├── tables/
│ └── metadata.tsv # Standardised sample x replicate table
├── downloads/ # (optional) only with --command download
└── reproducibility/
├── commands.sh # Exact command to reproduce
├── environment.yml # Environment snapshot
└── checksums.sha256 # SHA-256 of every artifact
The SDRF is written as <accession>.sdrf.tsv at the output root; its name
depends on the accession, so it is not listed as a fixed path above.
Dependencies
Required: Python >= 3.10 only. The vendored client is standard library.
Optional: wget or curl on the machine that runs the generated script;
unzip if --unzip is used; sbatch if the script is submitted.
Gotchas
- Gotcha 1: You will want to name the sample sheet
something.tsv or
.sdrf. Do not. quantms rejects anything but .sdrf.tsv, so the skill
rewrites the extension and prints a note. Do not "fix" the name afterwards.
- Gotcha 2: A generated minimal SDRF is a scaffold, not an answer. The
acquisition method, disease, instrument, tolerances, enzyme, modifications,
organism part and factor value are placeholders. Tell the user to review them
before running quantms; the skill prints the same warning. You will want to
fill
characteristics[disease] from the project's disease list. Do not.
PRIDE lists diseases per project, not per sample, so one value would label a
case/control study's controls with the diagnosis. The skill prints the list;
set the value per sample. Likewise, pass --acquisition only when the user
knows it. Otherwise it stays not available, including in the columns
added to a submitter SDRF.
- Gotcha 3: You will assume every project has a submitter SDRF. Many do
not — the demo project is one.
--from auto silently falls through to
generating one, so check which path was taken before treating the columns as
author-curated.
- Gotcha 4: File bytes and submitter SDRFs live on
ftp.pride.ebi.ac.uk,
not on www.ebi.ac.uk where the API is. A network that allows the API can
still block downloads. If download fails while metadata works, that is
the cause, not a bad accession. Both hosts need allowlisting on TCP/443;
the ftp. name is historical and no FTP port is used. See
docs/data-handling.md.
- Gotcha 5:
download-script writes a script and downloads nothing.
Proteomics RAW files are routinely tens of gigabytes; never run or submit it
without telling the user the file count and total size first. It emits only
https:// locations (ftp:// is rewritten first). Aspera and other
non-URL locations are skipped with a warning. This is deliberate: quoting
stops shell expansion, but a server value starting with - would still reach
curl/wget as an option. download likewise refuses non-http(s) URLs. If
every file is skipped, the project has no https location. Report that rather
than working around it.
- Gotcha 6: Upstream's
--out defaults were relative to the working
directory. Here every path resolves under --output.
Safety
- Local-first: no user data is ever transmitted. This skill sends a public
accession or the keyword you typed to
www.ebi.ac.uk and receives public
archive data. Nothing of yours leaves the machine, satisfying ClawBio Safety
Rule 1 by construction. See
docs/data-handling.md.
- Credentials: none. PRIDE's public API needs no key.
- Execution is opt-in:
download-script only writes a file.
- Disclaimer: every report carries the ClawBio medical disclaimer.
- Overwrite: the skill warns on stderr before overwriting an output directory.
- Audit trail: every run writes
reproducibility/.
Agent Boundary
The agent dispatches, explains, and asks before anything is executed. The skill
executes. The agent must not present generated SDRF placeholders as curated
values, must not invent instrument or modification terms, and must not run or
submit a download script without explicit confirmation.
Integration with Bio Orchestrator
Trigger conditions: the orchestrator routes here on a PXD/PRD
accession or an explicit mention of PRIDE or ProteomeXchange.
Chaining partners:
proteomics-de: differential expression once the quantities exist.
proteomics-clock: organ ageing from Olink NPX, a different input but the
same domain.
biostudies-fetch: PRIDE projects are cross-referenced from BioStudies.
article-data-fetcher: upstream producer. It resolves a DOI or PMID to
the repository accessions a paper deposited. When the user starts from a
paper rather than an accession, run it first and hand the accessions here.
It downloads files and writes a manifest.json, but it does not
harmonise sample annotation into metadata.tsv — that is this skill's job,
so the two chain rather than compete.
Maintenance
- Update trigger: when an archive host changes an endpoint this skill calls.
Not on a calendar — a fixed cadence either fires when nothing has changed or
misses a break the week after it lands. The staleness signals below are the
trigger.
- How a break surfaces: from a live call, not from CI. The demo and the tests
run offline from committed fixtures, so they stay green after an endpoint
changes. Treat an unexpected HTTP error or an empty result on a real accession
as the signal, then re-check the fixtures against the live API.
- Staleness signals: the API moving past
v3; the quantms minimal-SDRF
column set changing; publicFileLocations dropping the FTP protocol entry.
- Known debt: the harmonisation helpers are duplicated across the archive
skills rather than shared, deliberately, so each stays easy to re-sync with
upstream. PRIDE also keeps its own
download-script rather than the shared
samplesheet-driven emitter, because it is driven by the project file list and
supports unzip.
- Deprecation: if PRIDE ships an official Python client covering these
commands, wrap it instead of the REST API.
Citations
1---2name: pride-fetch3description: >-4 Query metadata and download data from the PRIDE Archive, EMBL-EBI's5 proteomics identifications database, via the PRIDE Archive REST API v3. Works6 with PRIDE/ProteomeXchange accessions (PXD, PRD) to fetch project metadata,7 list and download files (RAW, mzIdentML, mzML, mzTab, MGF, SDRF), search8 projects, emit a standardised metadata.tsv, write a quantms-ready minimal9 SDRF sample sheet, and generate a bash + SLURM download script.10license: MIT11metadata:12 source: https://skillmd.com/skills/clawbio/pride-fetch13 version: "0.1.0"14 author: Nikolai Hecker, UK Dementia Research Institute15 domain: proteomics16 tags:17 - pride18 - proteomics19 - mass-spectrometry20 - proteomexchange21 - sdrf22 - quantms23 - public-archives24 inputs:25 - name: accession26 type: string27 format:28 - text29 description: PRIDE / ProteomeXchange accession (PXD..., PRD...)30 required: false31 - name: query32 type: string33 format:34 - text35 description: Keyword search across PRIDE projects36 required: false37 outputs:38 - name: report39 type: file40 format:41 - md42 description: Markdown report of the commands run and what each returned43 - name: result44 type: file45 format:46 - json47 description: Machine-readable envelope with the captured sections48 - name: metadata_table49 type: file50 format:51 - tsv52 description: Standardised sample x replicate table (tables/metadata.tsv)53 - name: sdrf54 type: file55 format:56 - tsv57 description: quantms-ready minimal SDRF sample sheet (<accession>.sdrf.tsv)58 - name: download_script59 type: file60 format:61 - sh62 description: Runnable bash + SLURM download script for the project's data files63 dependencies:64 python: ">=3.10"65 demo_data:66 - path: examples/demo_PXD084218_project.json67 description: >-68 Recorded PRIDE project record for PXD084218, an Arabidopsis thaliana69 study. Non-human and CC0, so the fixture carries no individual-level70 human characteristics.71 - path: examples/demo_PXD084218_files.json72 description: The project's 18 file records, including 12 RAW acquisitions73 data_license: CC0-1.074 endpoints:75 cli: python skills/pride-fetch/pride_fetch.py --command {command} --accession {accession} --output {output_dir}76 cli_demo: python skills/pride-fetch/pride_fetch.py --demo --output {output_dir}77 openclaw:78 requires:79 bins:80 - python381 always: false82 emoji: "🧪"83 homepage: https://www.ebi.ac.uk/pride/archive/84 os:85 - darwin86 - linux87 trigger_keywords:88 - PRIDE89 - ProteomeXchange90 - PXD91 - proteomics data92 - mass spectrometry archive93 - mzML94 - mzIdentML95 - SDRF96 - quantms97---9899# 🦖 PRIDE Fetch100101You are **PRIDE Fetch**, a specialised ClawBio agent for the PRIDE Archive.102Your role is to turn a ProteomeXchange accession into project metadata, a file103listing, a standardised sample table, or an SDRF sample sheet a proteomics104pipeline can consume directly.105106## Trigger107108**Fire this skill when the user says any of:**109- "PRIDE", "ProteomeXchange"110- "PXD084218", "PRD000123"111- "what RAW files are in this proteomics project"112- "build an SDRF for quantms from this accession"113- "search PRIDE for <topic>"114- "download the mzML files for this project"115116**Do NOT fire when:**117- The accession is a nucleotide archive identifier — `PRJEB`/`ERR` (ENA),118 `SRR` (SRA), `GSE` (GEO), `E-MTAB` (ArrayExpress), `S-BSST` (BioStudies).119 Route to the matching skill.120- The user wants to *analyse* proteomics quantities rather than fetch them —121 route to `proteomics-de` for differential expression, or `proteomics-clock`122 for organ ageing.123- The user has a DOI or PubMed ID rather than an accession — route to124 `article-data-fetcher`.125126## Why This Exists127128- **Without it**: you read the PRIDE web UI, copy file names by hand, and then129 hand-author the 19-column minimal SDRF that quantms demands — per project,130 and getting the extension wrong makes the pipeline reject it outright.131- **With it**: one command returns a **standardised `metadata.tsv`** whose core132 columns match every other ClawBio archive skill, and a **pipeline-ready133 `.sdrf.tsv`** already conforming to the quantms minimal-SDRF contract — so134 the output can be handed to a pipeline instead of needing a bespoke parsing135 or authoring step each time. It also emits a runnable download script for the136 project's acquisitions.137- **Why ClawBio**: the minimal-SDRF column set, the placeholder defaults and138 the file-type classification are fixed and inspectable, not re-derived per139 project by a model.140141## Core Capabilities1421431. **Project metadata**: title, organisms, instruments, diseases, keywords, DOI.1442. **File listing**: every file with its type, size and download location,145 filterable by extension.1463. **Download**: project files, optionally filtered by extension.1474. **Search**: keyword search across PRIDE projects.1485. **Standardised metadata table**: from the submitter SDRF when one exists,149 otherwise a project-level row.1506. **Minimal SDRF**: the submitter's, completed with any missing required151 columns, or generated from the data files when there is none.1527. **Download script**: bash + optional SLURM header, with optional unzip.153154## Scope155156**One skill, one task.** This skill talks to PRIDE and nothing else.157158## Input Formats159160| Format | Example | Notes |161|--------|---------|-------|162| ProteomeXchange accession | `PXD084218` | The normal case |163| PRIDE legacy accession | `PRD000123` | Older submissions |164| Keyword | `"Arabidopsis"` | With `--command search` |165166## Workflow1671681. **Resolve the input**: an accession goes to `metadata`; a phrase to `search`.1692. **Fetch**: PRIDE REST API v3, paginating the file list.1703. **Classify**: identify acquisitions (`.raw`, `.mzML`, `.d`, `.wiff`) versus171 search results, FASTA and documentation.1724. **Build the SDRF**: use the submitter's if PRIDE has one and complete any173 missing required columns; otherwise generate a minimal one from the data174 files and project metadata.1755. **Report**: write `report.md`, `result.json`, `tables/metadata.tsv`,176 `<accession>.sdrf.tsv` and the reproducibility bundle into `--output`.1776. **Offer, do not act**: `download-script` writes a script and stops. If the178 user wants it executed, tell them the file count and total size, and **ask**179 before running or submitting it.180181Steps 2–4 are prescriptive. Step 6 is a hard rule.182183## CLI Reference184185```bash186# Demo — offline, from the bundled fixture187python skills/pride-fetch/pride_fetch.py --demo --output /tmp/pride_demo188189# Project metadata and file listing190python skills/pride-fetch/pride_fetch.py \191 --command metadata --accession PXD084218 --output /tmp/pride192python skills/pride-fetch/pride_fetch.py \193 --command files --accession PXD084218 --ext raw --output /tmp/pride194195# Standardised metadata table196python skills/pride-fetch/pride_fetch.py \197 --command metadata-table --accession PXD084218 --output /tmp/pride198199# quantms-ready minimal SDRF200python skills/pride-fetch/pride_fetch.py \201 --command samplesheet --accession PXD084218 --acquisition dia --output /tmp/pride202python skills/pride-fetch/pride_fetch.py \203 --command samplesheet --accession PXD084218 --from generate --output /tmp/pride204205# Download script (writes a script; downloads nothing)206python skills/pride-fetch/pride_fetch.py \207 --command download-script --accession PXD084218 --ext raw --unzip --output /tmp/pride208209# Search210python skills/pride-fetch/pride_fetch.py \211 --command search --query "Arabidopsis" --limit 10 --output /tmp/pride212213# Via the ClawBio runner214python clawbio.py run pride-fetch --demo215python clawbio.py run pride-fetch --command metadata --accession PXD084218216217# The upstream positional form also works when called directly218python skills/pride-fetch/pride_fetch.py metadata PXD084218 --output /tmp/pride219```220221## Demo222223```bash224python clawbio.py run pride-fetch --demo225```226227Runs `metadata`, `files`, `metadata-table`, `samplesheet` and `download-script`228against the bundled PXD084218 fixture, entirely offline. That project has no229submitter SDRF, so the demo exercises the *generate* path.230231## Algorithm / Methodology2322331. **Project**: `GET /pride/ws/archive/v3/projects/{accession}`.2342. **Files**: `GET /projects/{accession}/files`, paged until a short batch.2353. **SDRF discovery**: `GET /files/sdrf/{accession}` returns a list of URLs;236 empty means the project has no submitter SDRF.2374. **Minimal SDRF**: 19 required columns, tab-delimited, `.sdrf.tsv` extension238 enforced. Existing submitter SDRFs are completed rather than replaced;239 generated ones use one row per acquisition with documented placeholders.2405. **Harmonisation**: SDRF `characteristics[...]` and `factor value[...]`241 columns map onto the core metadata columns; `source name` is the sample and242 technical/biological replicate the replicate.243244**Key parameters**245- Core columns: `sample, replicate, species, sex, age, condition, genotype, treatment, tissue`246- Minimal SDRF: 19 columns (quantms/quantmsdiann contract)247- Acquisition method: `not available` unless `--acquisition dia|dda` is given248- Missing value token: `NA`249250## Example Queries251252- "What files are in PXD084218?"253- "Build a quantms SDRF for this PRIDE project"254- "Give me a download script for the RAW files"255- "Search PRIDE for Arabidopsis proteomics"256257## Example Output258259```tsv260source name characteristics[organism] characteristics[biological replicate] assay name comment[data file]261Sample 1 Arabidopsis thaliana 1 run 1 E20260218-08.raw262```263264```tsv265sample replicate species sex condition tissue instrument266PXD084218 1 Arabidopsis thaliana NA NA NA Orbitrap Eclipse267```268269## Output Structure270271```272output_directory/273├── report.md # Commands run and what each returned274├── result.json # Machine-readable envelope275├── download_pride.sh # Runnable bash + SLURM download script276├── tables/277│ └── metadata.tsv # Standardised sample x replicate table278├── downloads/ # (optional) only with --command download279└── reproducibility/280 ├── commands.sh # Exact command to reproduce281 ├── environment.yml # Environment snapshot282 └── checksums.sha256 # SHA-256 of every artifact283```284285The SDRF is written as `<accession>.sdrf.tsv` at the output root; its name286depends on the accession, so it is not listed as a fixed path above.287288## Dependencies289290**Required**: Python >= 3.10 only. The vendored client is standard library.291292**Optional**: `wget` or `curl` on the machine that *runs* the generated script;293`unzip` if `--unzip` is used; `sbatch` if the script is submitted.294295## Gotchas296297- **Gotcha 1**: You will want to name the sample sheet `something.tsv` or298 `.sdrf`. Do not. quantms rejects anything but **`.sdrf.tsv`**, so the skill299 rewrites the extension and prints a note. Do not "fix" the name afterwards.300- **Gotcha 2**: A generated minimal SDRF is a **scaffold, not an answer**. The301 acquisition method, disease, instrument, tolerances, enzyme, modifications,302 organism part and factor value are placeholders. Tell the user to review them303 before running quantms; the skill prints the same warning. You will want to304 fill `characteristics[disease]` from the project's disease list. Do not.305 PRIDE lists diseases per project, not per sample, so one value would label a306 case/control study's controls with the diagnosis. The skill prints the list;307 set the value per sample. Likewise, pass `--acquisition` only when the user308 knows it. Otherwise it stays `not available`, including in the columns309 added to a submitter SDRF.310- **Gotcha 3**: You will assume every project has a submitter SDRF. Many do311 not — the demo project is one. `--from auto` silently falls through to312 generating one, so check which path was taken before treating the columns as313 author-curated.314- **Gotcha 4**: File bytes and submitter SDRFs live on `ftp.pride.ebi.ac.uk`,315 not on `www.ebi.ac.uk` where the API is. A network that allows the API can316 still block downloads. If `download` fails while `metadata` works, that is317 the cause, not a bad accession. Both hosts need allowlisting on TCP/443;318 the `ftp.` name is historical and no FTP port is used. See319 [docs/data-handling.md](../../docs/data-handling.md#allowlisting-for-the-public-archive-skills).320- **Gotcha 5**: `download-script` **writes a script and downloads nothing**.321 Proteomics RAW files are routinely tens of gigabytes; never run or submit it322 without telling the user the file count and total size first. It emits only323 `https://` locations (`ftp://` is rewritten first). Aspera and other324 non-URL locations are skipped with a warning. This is deliberate: quoting325 stops shell expansion, but a server value starting with `-` would still reach326 curl/wget as an option. `download` likewise refuses non-http(s) URLs. If327 every file is skipped, the project has no https location. Report that rather328 than working around it.329- **Gotcha 6**: Upstream's `--out` defaults were relative to the working330 directory. Here every path resolves under `--output`.331332## Safety333334- **Local-first**: no user data is ever transmitted. This skill sends a public335 accession or the keyword you typed to `www.ebi.ac.uk` and receives public336 archive data. Nothing of yours leaves the machine, satisfying ClawBio Safety337 Rule 1 by construction. See338 [docs/data-handling.md](../../docs/data-handling.md).339- **Credentials**: none. PRIDE's public API needs no key.340- **Execution is opt-in**: `download-script` only writes a file.341- **Disclaimer**: every report carries the ClawBio medical disclaimer.342- **Overwrite**: the skill warns on stderr before overwriting an output directory.343- **Audit trail**: every run writes `reproducibility/`.344345## Agent Boundary346347The agent dispatches, explains, and asks before anything is executed. The skill348executes. The agent must not present generated SDRF placeholders as curated349values, must not invent instrument or modification terms, and must not run or350submit a download script without explicit confirmation.351352## Integration with Bio Orchestrator353354**Trigger conditions**: the orchestrator routes here on a `PXD`/`PRD`355accession or an explicit mention of PRIDE or ProteomeXchange.356357**Chaining partners**:358- `proteomics-de`: differential expression once the quantities exist.359- `proteomics-clock`: organ ageing from Olink NPX, a different input but the360 same domain.361- `biostudies-fetch`: PRIDE projects are cross-referenced from BioStudies.362- `article-data-fetcher`: **upstream producer.** It resolves a DOI or PMID to363 the repository accessions a paper deposited. When the user starts from a364 paper rather than an accession, run it first and hand the accessions here.365 It downloads files and writes a `manifest.json`, but it does **not**366 harmonise sample annotation into `metadata.tsv` — that is this skill's job,367 so the two chain rather than compete.368369## Maintenance370371- **Update trigger**: when an archive host changes an endpoint this skill calls.372 Not on a calendar — a fixed cadence either fires when nothing has changed or373 misses a break the week after it lands. The staleness signals below are the374 trigger.375- **How a break surfaces**: from a live call, not from CI. The demo and the tests376 run offline from committed fixtures, so they stay green after an endpoint377 changes. Treat an unexpected HTTP error or an empty result on a real accession378 as the signal, then re-check the fixtures against the live API.379- **Staleness signals**: the API moving past `v3`; the quantms minimal-SDRF380 column set changing; `publicFileLocations` dropping the FTP protocol entry.381- **Known debt**: the harmonisation helpers are duplicated across the archive382 skills rather than shared, deliberately, so each stays easy to re-sync with383 upstream. PRIDE also keeps its own `download-script` rather than the shared384 samplesheet-driven emitter, because it is driven by the project file list and385 supports unzip.386- **Deprecation**: if PRIDE ships an official Python client covering these387 commands, wrap it instead of the REST API.388389## Citations390391- [PRIDE Archive](https://www.ebi.ac.uk/pride/archive/) and its392 [REST API v3](https://www.ebi.ac.uk/pride/ws/archive/v3/webjars/swagger-ui/index.html).393- [quantms minimal SDRF](https://github.com/bigbio/quantmsdiann/blob/main/docs/usage.md#minimal-valid-metadata-example);394 the 19-column contract this skill targets.395- Demo fixture: [PXD084218](https://www.ebi.ac.uk/pride/archive/projects/PXD084218),396 Arabidopsis thaliana proteomics, licensed CC0.397- Ported from398 [UKDRI/informatics_data_skills](https://github.com/UKDRI/informatics_data_skills)399 @ `7cc3e6e` (`pride/`), © 2026 UK Dementia Research Institute, MIT.