CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-proteomics-data-retrieval

Find and retrieve proteomics datasets from MassIVE, ProteomeXchange, PRIDE Archive, and the NCI Proteomics Data Commons (PDC). Search by species, keyword, accession, or protein; retrieve detailed metadata (instruments, publications, species, PTMs studied), real file-download URLs (PRIDE), or quantitative abundance matrices with clinical linkage (PDC/CPTAC). Use for locating public proteomics datasets to reanalyze, comparing instrument/protocol coverage across studies, pre-download dataset evaluation, and finding every dataset that identified a specific protein.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is tooluniverse-proteomics-data-retrieval in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is information-dense with real API knowledge and well-sequenced workflows, but it is a monolithic ~370-line file where per-repository detail should be split into reference files, and it carries systematic redundancy (duplicated response-format notes, duplicate taxonomy tables, PRIDE capabilities restated four times). Actionability is strong, held back slightly by a wrong tool name in Limitations.

Suggestions

Deduplicate the repeated material: keep 'Response Format Notes' and the species taxonomy ID table in one place each, and state PRIDE's full-text search / download-URL / protein-lookup differentiators once instead of across the repository table, PRIDE section, fallback table, and Limitations.

Create one-level-deep reference files (e.g., references/pdc.md, references/pride.md, references/peptideatlas.md) and keep SKILL.md as a workflow overview with brief per-repository summaries and links, replacing the fully inlined per-tool parameter tables.

Fix the incorrect tool reference in Limitations ('get details via Dataverse_get_dataset' should be ProteomeXchange_get_dataset) and add one complete example call per tool family to close the actionability gap.

DimensionReasoningScore

Conciseness

The core content is genuinely non-obvious API knowledge (wrapper-format quirks, string-typed taxonomy IDs, parameter limits), but duplication is systematic: 'Response Format Notes' appears verbatim in both Phase 1 and the Tool Parameter Reference, species taxonomy IDs are listed in Phase 0 and again in a dedicated table, and PRIDE's three differentiators (full-text search, download URLs, protein-first lookup) are restated four times (repository table, PRIDE prose, fallback table, Limitations). It fits anchor 3 ('could be tightened') better than anchor 4, whose 'minor instances' standard the repeated sections exceed.

3 / 5

Actionability

Concrete tool names with parameters, defaults, and ranges, plus worked call signatures (e.g., 'MassIVE_search_datasets(page_size=20, species="9606")') and live-verified outputs (PDC000127 reporting 9,591 gene rows). Not anchor 5 because complete call examples are absent for several tools and Limitations references a nonexistent tool name ('Dataverse_get_dataset') instead of ProteomeXchange_get_dataset.

4 / 5

Workflow Clarity

Clear phased workflow (0-3) with per-query-type decision logic, dedicated workflows for PDC and PRIDE, and a fallback-strategy table covering empty results and failed lookups; checkpoints like 'confirm scope with PDC_get_study_summary' are present. Not anchor 5 because there is no explicit validation loop on merged/deduplicated search results, only implicit guidance.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories) and all four tool families (MassIVE/ProteomeXchange, PDC, PRIDE, PeptideAtlas) are fully inlined in a ~370-line SKILL.md. Section headers make it navigable, but the per-repository parameter tables, taxonomy reference, and interpretation framework clearly belong in one-level-deep reference files — anchor 3 ('content that should be separate is inline') rather than 4 ('references mostly clear'), since there are no references at all.

3 / 5

Total

14

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities across four named repositories, enumerates search modes and retrieval outputs with field-level detail, and closes with an explicit 'Use for...' clause covering four trigger scenarios. The only gap is a few natural synonym phrases like 'mass spectrometry' or 'MS data'.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions with comprehensive coverage: 'Search by species, keyword, accession, or protein; retrieve detailed metadata (instruments, publications, species, PTMs studied), real file-download URLs (PRIDE), or quantitative abundance matrices with clinical linkage (PDC/CPTAC)' across four named repositories. It is above anchor 4 because search modes and retrieval outputs are enumerated exhaustively rather than with minor gaps.

5 / 5

Completeness

Explicitly answers both questions: the 'what' ('Find and retrieve proteomics datasets from MassIVE, ProteomeXchange, PRIDE Archive, and the NCI Proteomics Data Commons') and the 'when' ('Use for locating public proteomics datasets to reanalyze, comparing instrument/protocol coverage across studies, pre-download dataset evaluation, and finding every dataset that identified a specific protein').

5 / 5

Trigger Term Quality

Good natural-keyword coverage: 'proteomics datasets', 'MassIVE', 'PRIDE Archive', 'species', 'accession', 'PTMs'. Not anchor 5 because common variations users would say, such as 'mass spectrometry data', 'MS data', or 'mass spec', are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (proteomics dataset retrieval from named public repositories) with repository-specific triggers; retrieval scope is distinct from downstream analysis skills, so minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugins/tooluniverse/skills/tooluniverse-proteomics-data-retrieval/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.