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

81%

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

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.

Operationally rich content with genuinely useful tool documentation, workflows, and fallbacks, weakened by internal duplication (taxonomy IDs x3, response-format notes x2), a domain-primer section of knowledge Claude already has, two factual inconsistencies in the Limitations section, and zero use of bundle files for the long reference tables. The core retrieval workflow itself is clear and actionable.

Suggestions

Deduplicate the body: keep the species taxonomy IDs in one place (the table), state the Response Format Notes once (the Tool Parameter Reference section), and delete the redundant opening paragraph that restates the frontmatter description.

Move the Tool Parameter Reference, Common Species Taxonomy IDs table, and Interpretation Framework into a single reference file (e.g., references/tool-reference.md) linked from SKILL.md, keeping the main file as a lean overview plus workflows.

Fix the Limitations section: replace 'Dataverse_get_dataset' with 'ProteomeXchange_get_dataset', and reword 'No full-text search' to acknowledge that PRIDE_search_proteomics provides full-text search while MassIVE/ProteomeXchange do not.

Trim or cut the 'Domain Reasoning: Dataset Quality Assessment' section, which re-explains well-known proteomics fundamentals (TMT ratio compression, DIA vs DDA, Orbitrap resolution) in favor of skill-specific guidance.

DimensionReasoningScore

Conciseness

The bulk is dense, high-value operational reference material, but there is real waste: species taxonomy IDs appear three times (KEY PRINCIPLES, Phase 0, and the Common Species Taxonomy IDs table), the 'Response Format Notes' block appears twice nearly verbatim, the opening paragraph restates the frontmatter description, and the 'Domain Reasoning' section explains TMT/iTRAQ bias and Orbitrap-vs-ion-trap quality that Claude largely already knows. Not 4 because the duplication and primer content go beyond minor trimming.

3 / 5

Actionability

Highly concrete guidance: exact tool names, parameter names, types, defaults, and response formats, plus copy-paste-ready calls like `MassIVE_search_datasets(page_size=20, species="9606")` and per-repository workflows. Not 5 because of two factual flaws: the Limitations section references a nonexistent `Dataverse_get_dataset` (should be `ProteomeXchange_get_dataset`), and 'No full-text search' directly contradicts the PRIDE section's documented full-text search capability.

4 / 5

Workflow Clarity

Clear Phases 0-3 with input-resolution decision logic, per-phase workflows, and a Fallback Strategies table covering error recovery (e.g., 'MassIVE_get_dataset fails for PXD accession -> Use ProteomeXchange_get_dataset'). Not 5 because there are no explicit validation checkpoints (e.g., confirming an accession exists before a detail call) and no explicit feedback loops beyond the fallback table; not 3 because the sequence and fallbacks are well defined for this read-only retrieval domain.

4 / 5

Progressive Disclosure

Good in-file structure with clear section headers, but the skill is a single 370-line monolith with no bundle files at all: the Tool Parameter Reference, species taxonomy table, and Interpretation Framework are exactly the content that belongs in one-level-deep reference files per the rubric's rationale. Anchor 3 fits: some structure, but content that should be separate is inline; not 2 because headers make navigation easy and nothing is buried.

3 / 5

Total

14

/

20

Passed

Description

88%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: concrete, comprehensive capability statements paired with an explicit 'Use for...' clause containing specific trigger scenarios. Third-person voice throughout, no fluff. Minor gaps in natural-synonym coverage and slight overlap risk with sibling tooluniverse skills.

DimensionReasoningScore

Specificity

The description lists multiple specific 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)', and 'quantitative abundance matrices with clinical linkage (PDC/CPTAC)'. Not the level below (4) because the action list is comprehensive across all four named repositories rather than having minor gaps.

5 / 5

Completeness

Clearly answers both 'what' ('Find and retrieve proteomics datasets... retrieve detailed metadata... file-download URLs... abundance matrices') and 'when' with an explicit trigger clause: '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 keyword coverage with natural terms users would say ('proteomics datasets', 'reanalyze', 'accession', 'protein', and repository names MassIVE/ProteomeXchange/PRIDE/PDC). Not 5 because common variations like 'mass spectrometry data', 'MS data', or 'mass spec' are absent, leaving a few natural trigger phrases missing.

4 / 5

Distinctiveness Conflict Risk

Mostly distinct: named repositories and proteomics-specific triggers create a clear niche with minimal conflict risk. Not 5 because the 'when' phrasing ('locating public proteomics datasets', 'comparing instrument/protocol coverage') overlaps with closely related sibling skills like multi-omics-integration and proteomics-analysis in the same tooluniverse family.

4 / 5

Total

18

/

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

plugin/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.