CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pyopenms-skill

Comprehensive tool for computational mass spectrometry using PyOpenMS; use when you need to read/write MS formats (mzML/mzXML/MGF), run signal processing (smoothing/peak picking), detect isotope features, or perform peptide identification in proteomics/metabolomics workflows.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Data Analysis/pyopenms-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Well-structured overview with verified, cleanly linked bundle files and a mostly executable quick-start example, but the body is noticeably padded (a redundant Key Features section, filler version notes, hedged in-code commentary) and the documented Load → Process → Analyze workflow includes no validation checkpoints despite targeting batch pipeline use. Structural design is strong; editorial tightening and a verification step are the main fixes.

Suggestions

Delete the redundant 'Key Features' section and the '(version: latest recommended)' parentheticals, and remove the hedging comments inside the example ('The returned object depends on the implementation of run_workflow...') in favor of the script's actual documented return (a summary dict with spectrum_count, first_spectrum_peaks, mz_range).

Add an explicit validation checkpoint to the workflow, e.g. after processing: check the returned summary (non-zero spectrum_count, peaks present) and handle the empty-spectra case before proceeding — required since the skill advertises batch-processing pipelines.

State the import/run context for the example (e.g. run from the skill directory or add it to PYTHONPATH) so the 'from scripts.process_ms import run_workflow' snippet is reliably copy-paste executable.

DimensionReasoningScore

Conciseness

Several padded sections: 'Key Features' fully duplicates 'When to Use' and the frontmatter description; '(version: latest recommended)' appears twice as filler; the code example carries hedging commentary ('The returned object depends on the implementation of run_workflow. Common patterns include...'); and 'Implementation Details' explains a known concept ('PyOpenMS, the Python bindings for the OpenMS C++ library') and re-describes the workflow the example already shows. This matches the 2 anchor ('noticeably verbose; several unnecessary explanations or padded sections') — not 1, since there is no wall of generic tutorial prose, and not 3, because the redundancy spans whole sections rather than isolated sentences.

2 / 5

Actionability

Gives a concrete install command ('uv pip install pyopenms pandas numpy') and a runnable example whose call 'run_workflow("data.mzML", apply_filter=True)' matches the actual script signature, matching the 4 anchor ('mostly executable guidance; concrete code or commands with minor gaps'). Not 5 because the example hedges on its own outcome (undocumented return value, 'is expected to read the input mzML') and relies on an import path ('from scripts.process_ms import') that only works from the skill directory; not 3 because the code is genuinely executable, not pseudocode.

4 / 5

Workflow Clarity

A clear Load → Process → Analyze sequence is listed ('1. Load an MS run from disk... 2. Process spectra... 3. Analyze results'), but there are zero validation or verification checkpoints — no instruction to confirm the file loaded, spectra were found, or output is usable — matching the 3 anchor ('steps listed but validation gaps'). The batch-processing use case ('batch-processing mass spectrometry files as part of a pipeline') also invokes the guideline capping workflow clarity at 3, ruling out 4.

3 / 5

Progressive Disclosure

The body is a genuine overview pointing to real, verified, one-level-deep bundle files with clear navigation ('File operations: references/file_io.md', 'Signal processing algorithms: references/signal_processing.md', plus scripts/process_ms.py), and neither reference file nests further references. This matches the 5 anchor ('clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation') — the duplication in 'Key Features' is a conciseness defect, not a file-organization one, so it does not drop this dimension to 4.

5 / 5

Total

14

/

20

Passed

Description

95%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 capability list, natural trigger terms including file extensions, and an explicit use-when clause. The only flaw is the second-person 'use when you need to' construction (guidelines require third person), which costs it a specificity point.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'read/write MS formats (mzML/mzXML/MGF)', 'run signal processing (smoothing/peak picking)', 'detect isotope features', 'perform peptide identification' — which matches the 5 anchor, but the second-person phrasing 'use when you need to' and the buzzword opener 'Comprehensive tool' trigger the -1 penalty guideline, landing it at 4 rather than 5.

4 / 5

Completeness

Explicitly answers what ('read/write MS formats', 'signal processing', 'detect isotope features', 'perform peptide identification in proteomics/metabolomics workflows') and when ('use when you need to read/write MS formats (mzML/mzXML/MGF), run signal processing (smoothing/peak picking), detect isotope features, or perform peptide identification') with concrete trigger phrases, exactly matching the 5 anchor.

5 / 5

Trigger Term Quality

Includes file extensions users naturally say ('mzML/mzXML/MGF'), technique names ('smoothing/peak picking', 'isotope', 'peptide identification'), and domain synonyms ('proteomics/metabolomics'), matching the 5 anchor's comprehensive coverage with extensions and synonyms; only a colloquial variant like 'mass spec' is missing, which is not enough to drop to 4.

5 / 5

Distinctiveness Conflict Risk

Clear niche — computational mass spectrometry via PyOpenMS — with distinct triggers (mzML, MGF, peak picking, isotope patterns) that no generic file-processing or data skill would claim, matching the 5 anchor's minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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