CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

proteomexchange-skill

Submit compact ProteomeXchange PROXI requests for datasets, libraries, peptidoforms, proteins, PSMs, spectra, and USI examples. Use when a user wants concise PROXI summaries

70

Quality

88%

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

92%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.

A tight, fully executable skill body: a copy-paste bash example, concrete request patterns, and complete input/output contracts that match the bundled script. The only blemish is minor redundancy from repeating the full base_url across the example payloads.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the three example payloads each repeat the full base_url verbatim when it is already stated in both 'Operating rules' and the 'Input' required-fields list — minor trimmable redundancy that keeps it just below anchor 5.

4 / 5

Actionability

The 'Execution' section provides a copy-paste-ready bash command, three concrete JSON request patterns cover the common cases, and the Input/Output field lists are complete and verifiable against scripts/rest_request.py.

5 / 5

Workflow Clarity

This is a simple, single-action skill under 50 lines and the action (run the script with a JSON payload) is unambiguous; the Output section documents the failure channel (ok=false with error.code/error.message) as an error-recovery signal, and the read-only queries do not trigger the destructive/batch validation cap.

5 / 5

Progressive Disclosure

Sections are well organized, and the References section explicitly limits the bundle to this file plus scripts/rest_request.py — a real file whose implementation matches the documented input fields. Under 50 lines with no external references needed, well-organized sections suffice for anchor 5.

5 / 5

Total

19

/

20

Passed

Description

78%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 solid, third-person description that clearly identifies its niche and enumerates the API's resources, with an explicit 'Use when...' clause. It falls short of top marks only in trigger breadth: the when-clause is circular ('wants concise PROXI summaries') and misses the natural vocabulary (proteomics, mass spectrometry, PXD accessions) real users would say.

Suggestions

Broaden trigger terms to include user-natural synonyms: 'proteomics', 'mass spectrometry', 'mass-spec', and 'PXD accession' (e.g., 'Use when a user mentions ProteomeXchange, PXD datasets, proteomics data submission, or retrieving mass-spectrometry results').

Make the when-clause concrete rather than circular — name the user situations (fetching a dataset summary, looking up spectra or PSMs, resolving a USI) instead of restating the output term 'concise PROXI summaries'.

Add one more concrete capability beyond 'Submit ... requests' — e.g., 'return compact, readable summaries of the JSON responses' — so the action list covers both the request and the response side.

DimensionReasoningScore

Specificity

'Submit compact ProteomeXchange PROXI requests for datasets, libraries, peptidoforms, proteins, PSMs, spectra, and USI examples' names the domain and enumerates the full resource surface, but the action list reduces to a single verb ('Submit') with no coverage of response handling or summarization actions — several specifics with minor gaps, anchor 4 rather than comprehensive anchor 5.

4 / 5

Completeness

Both parts are present: the what ('Submit compact ProteomeXchange PROXI requests for...') and the when ('Use when a user wants concise PROXI summaries'). However the when-clause is thin and circular — it reuses the skill's own output term rather than concrete user triggers, matching anchor 4 rather than the explicit trigger phrases of anchor 5.

4 / 5

Trigger Term Quality

Good keyword coverage (ProteomeXchange, PROXI, datasets, PSMs, spectra, USI), but it leans on the API's own terminology and misses natural phrases a user would say such as 'proteomics', 'mass spectrometry', or 'PXD accession' — a few natural terms missing, anchor 4.

4 / 5

Distinctiveness Conflict Risk

'ProteomeXchange PROXI' names a specific, dedicated API with a clear niche and distinct technical triggers; minimal overlap risk with any other skill, matching anchor 5.

5 / 5

Total

17

/

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

openai/plugins

Path

plugins/life-science-research/skills/proteomexchange-skill/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.