CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pyopenms

Processes mass spectrometry data with pyOpenMS. Supports proteomics and metabolomics workflows—feature detection, peptide/protein identification, label-free quantification, adduct/accurate-mass annotation, and complex LC-MS/MS pipelines. Supports extensive file formats and algorithms. For simple spectral comparison and small-molecule library matching use matchms.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 strong, highly actionable skill body: executable commands everywhere, well-structured script tables, and unusually good scientific guardrails (FDR scope, tolerance semantics, centroid/profile assumptions). The main improvements are trimming low-value sections and converting narrative cautions into explicit validation checkpoints within the workflows.

Suggestions

Condense the ~15-line 'Citing Scientific Agent Skills' arXiv-fetching procedure to 2-3 lines or move it to a reference file; it is the least token-efficient part of the body.

Tighten or drop the generic 'Integration with other tools' section — it lists libraries without actionable guidance.

In the multi-sample recipe (align_link_quantify → consensus_to_matrix), insert an explicit checkpoint (e.g., inspect the consensus XML or residual RT errors before building the quant matrix) so validation is a workflow step, not just a caution.

DimensionReasoningScore

Conciseness

The body is dense with version-pinned operational knowledge Claude cannot reliably know (nanobind migration, 'FeatureFindingMetabo.run(traces, features) fills the map and returns a tuple', 'RT and chromatogram time are seconds') and almost never explains concepts Claude already knows. Minor trimming opportunities remain: the ~15-line arXiv citation-fetching procedure and the generic 'Integration with other tools' listing ('Pandas (DataFrames), NumPy (peak arrays), scikit-learn (ML)') earn fewer tokens than the rest. This fits anchor 4 (efficient, minor over-explanation that could be trimmed) rather than 5, where every token earns its place.

4 / 5

Actionability

Fully executable throughout: install commands ('uv pip install "pyopenms==3.6.0"...'), a verification snippet, runnable script invocations with real flags ('python scripts/align_link_quantify.py s1.mzML s2.mzML s3.mzML --out-prefix study'), complete code blocks for Param management and pandas export, and a 'Common script recipes' section covering the main cases. Matches anchor 5 (copy-paste ready commands covering common cases), not 4, since no significant gaps remain.

5 / 5

Workflow Clarity

Multi-step pipelines are clearly sequenced (inspect → detect → align/link → consensus matrix) and risky operations carry strong validation guidance: 'Before using it, verify target/decoy annotations, score direction, and the search database', an install verification step, and 'Alignment failure stops linking unless explicitly overridden with --allow-unaligned'. However, validation is delivered as narrative cautions rather than explicit validate-then-proceed checkpoints with feedback loops inside the workflows, which is anchor 4 ('most checkpoints present; minor validation gaps') rather than 5.

4 / 5

Progressive Disclosure

The body is a true overview: 17 scripts documented in compact tables with a 'drop into references/ only when no script fits' policy, and six clearly-labeled one-level-deep references ('references/file_io.md – file format handling', etc.), all of which exist on disk with no deeper nesting. Cross-cutting version caveats that affect every operation are appropriately kept inline. Matches anchor 5 (clear overview, well-signaled one-level-deep references, easy navigation).

5 / 5

Total

18

/

20

Passed

Description

75%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 specific, distinctive description that names its domain and concrete capabilities and even disambiguates against a sibling skill. Its weakness is activation guidance: it tells Claude when to use matchms instead of this skill, but never states when this skill itself should be selected.

Suggestions

Add an explicit positive trigger clause, e.g. 'Use when working with raw or processed LC-MS/MS data, proteomics or metabolomics quantification, or peptide/protein identification.'

Include the file formats users naturally mention (mzML, mzXML, MGF, featureXML, consensusXML) as trigger terms, which would also raise trigger-term coverage to comprehensive.

DimensionReasoningScore

Specificity

Multiple concrete actions are enumerated — 'feature detection, peptide/protein identification, label-free quantification, adduct/accurate-mass annotation, and complex LC-MS/MS pipelines' — with domain coverage spanning proteomics and metabolomics. This matches anchor 5 (multiple specific concrete actions, comprehensive coverage) rather than 4, whose example lists three actions with acknowledged gaps.

5 / 5

Completeness

The 'what' is explicit and comprehensive ('Processes mass spectrometry data with pyOpenMS...'), but there is no positive 'Use when...' clause — the only trigger guidance is the negative redirect 'For simple spectral comparison and small-molecule library matching use matchms'. Per the judging guideline, missing 'Use when...' or equivalent explicit activation guidance caps completeness at 3; the redirect routes users to a different skill rather than stating when to activate this one.

3 / 5

Trigger Term Quality

Good natural-keyword coverage: 'mass spectrometry', 'proteomics', 'metabolomics', 'LC-MS/MS', 'label-free quantification', 'spectral comparison'. Missing are the file formats users naturally name when asking for MS work (mzML, mzXML, MGF, featureXML) and common synonyms like 'MS data' or 'spectra', which anchor 5 explicitly expects ('including synonyms and file extensions'). Fits anchor 4 (good coverage, a few natural terms missing).

4 / 5

Distinctiveness Conflict Risk

A clear niche (pyOpenMS mass spectrometry pipelines) with distinct triggers and an explicit disambiguation boundary against matchms, minimizing risk of triggering for the wrong skill. Matches anchor 5 (clear niche, minimal conflict risk); it is strictly stronger than anchor 4, which still admits overlap with closely related skills.

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

K-Dense-AI/scientific-agent-skills

Path

skills/pyopenms/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.