CtrlK
BlogDocsLog inGet started
Tessl Logo

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

72

Quality

87%

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

100%Weight 40%Scale 1-3

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

The SKILL.md body is a lean, well-structured, single-purpose skill with executable examples, concrete request patterns, and a verified one-level reference to the bundled script. It does not pad with background and provides clear input/output contracts.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or explanation of concepts Claude already knows; every section (Operating rules, Input, Output, Execution) earns its place.

3 / 3

Actionability

It provides a copy-paste-ready executable bash command, an exact base_url, concrete JSON request patterns, and explicit success/failure output fields.

3 / 3

Workflow Clarity

This is a simple single-action skill (build a JSON object, pipe it to scripts/rest_request.py, interpret the result) and the single action is unambiguous with success/failure handling described; no destructive or batch operation requires a validation checkpoint.

3 / 3

Progressive Disclosure

Under 50 lines with well-organized sections and a single one-level reference to scripts/rest_request.py, which is a real file present in the bundle.

3 / 3

Total

12

/

12

Passed

Description

75%Weight 40%Scale 1-3

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

The description is concise and clearly establishes a distinct ProteomeXchange/PROXI niche with both a what and a when clause. Its main weakness is trigger phrasing that leans on technical jargon and a single action verb rather than diverse natural user phrasings.

Suggestions

Broaden the trigger clause with natural user phrasings (e.g. 'Use when a user wants proteomics dataset summaries, PROXI lookups, or USI/spectrum examples') beyond 'PROXI summaries'.

Vary the action verbs beyond 'Submit' to convey multiple concrete actions (e.g. 'Query, retrieve, and summarize ProteomeXchange PROXI data').

Add common user-facing synonyms like 'proteomics dataset' or 'mass spectrometry data' to improve trigger term coverage.

DimensionReasoningScore

Specificity

It names the domain and many concrete targets ('datasets, libraries, peptidoforms, proteins, PSMs, spectra, and USI examples') but relies on a single action verb ('Submit ... PROXI requests'), so action variety is limited rather than enumerating multiple distinct concrete actions.

2 / 3

Completeness

It explicitly answers both 'what' ('Submit compact ProteomeXchange PROXI requests for ...') and 'when' ('Use when a user wants concise PROXI summaries').

3 / 3

Trigger Term Quality

It includes relevant domain keywords, but the trigger phrasing 'concise PROXI summaries' is technical jargon and it omits common natural variations a user might say (e.g. 'proteomics dataset' or 'mass spectrometry data').

2 / 3

Distinctiveness Conflict Risk

The ProteomeXchange/PROXI niche is highly specific with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.