CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

matchms

Process, clean, and compare mass spectrometry (MS/MS) spectra with Matchms; use when you need reproducible spectral filtering and similarity scoring for metabolomics workflows.

Quality

70%

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/matchms/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers genuinely useful, executable material (a runnable Python example, a packaged CLI script, and real one-level-deep references), but its structure is broken: five sections are duplicated wholesale, boilerplate framing pads the token budget, and the workflow lacks an explicit validation checkpoint for a batch scoring operation. Consolidating the duplicate sections and moving match-mechanics detail into the existing references would lift every dimension.

Suggestions

Deduplicate the body: merge the two "When to Use"/"Key Features"/"Dependencies"/"Example Usage"/"Implementation Details" section pairs into single sections, removing template boilerplate like "Use this skill when a data analytics task needs a packaged method instead of ad-hoc freeform output".

Add an explicit validation checkpoint to the run plan (e.g. verify spectra loaded cleanly and inspect score output before returning results) with a fix-and-retry loop, since all-vs-all scoring is a batch operation.

Move the Greedy/Hungarian/Modified-Cosine mechanics out of "Implementation Details" into references/similarity.md and reference them with a clear link instead of the hedged "if present in the repository" phrasing; replace the leaked "20260316/scientific-skills/..." cd path with a repo-relative path.

DimensionReasoningScore

Conciseness

Five entire sections are duplicated verbatim in structure ("When to Use", "Key Features", "Dependencies", "Example Usage", "Implementation Details" each appear twice), plus template boilerplate like "Use this skill when a data analytics task needs a packaged method instead of ad-hoc freeform output" and "Repository baseline for current packaged skills". This matches anchor 2 (noticeably verbose, several padded sections); it is not anchor 1 because the Python example and reference pointers carry genuine value and it avoids explaining generic concepts at length.

2 / 5

Actionability

A complete, runnable Python example (load_from_mgf → calculate_scores → iterate) and concrete commands ("python -m py_compile scripts/similarity_pipeline.py", "python scripts/similarity_pipeline.py --help") cover the common case. Minor gaps keep it at anchor 4 rather than 5: the "cd "20260316/scientific-skills/..."" path is a leaked environment-specific directory, and the two competing "Example Usage" sections dilute the executable path.

4 / 5

Workflow Clarity

A run plan is listed (confirm inputs → edit config → run script → review output), but there is no explicit validation checkpoint — the review step is only implicit. All-vs-all spectral comparison is a batch operation and the rubric caps workflow clarity at 3 when validation feedback loops are missing, so this cannot score 4.

3 / 5

Progressive Disclosure

Real one-level-deep references exist (references/filtering.md, similarity.md, workflows.md) and are linked from the body, alongside scripts/similarity_pipeline.py. However, signaling is hedged ("if present in the repository"), the five duplicated top-level sections are a significant organization failure, and implementation detail (Greedy vs. Hungarian matching mechanics) is inlined in SKILL.md instead of living in the existing reference files — more than the "minor organization gaps" of anchor 4.

3 / 5

Total

12

/

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.

The description is strong: concrete actions, an explicit "use when" clause, and a well-defined metabolomics/mass-spectrometry niche with minimal conflict risk. Its main limitation is keyword breadth — natural trigger phrases like library matching, cosine scoring, and MGF/MSP file extensions are absent.

Suggestions

Broaden trigger terms to include common phrasings like "library matching", "cosine similarity", "spectral comparison", and file extensions users actually name (MGF, MSP, mzML).

Expand the "when" clause to enumerate concrete trigger moments, e.g. "Use when the user mentions MS/MS spectra, MGF/MSP files, spectral similarity, or metabolomics library matching."

DimensionReasoningScore

Specificity

"Process, clean, and compare mass spectrometry (MS/MS) spectra with Matchms" lists several concrete actions (process, clean, compare, filter, score), with minor gaps such as import formats, library matching, and clustering left unmentioned. It sits at anchor 4 rather than 5 because coverage is not comprehensive, and above anchor 3 because more than 1-2 specific actions are named.

4 / 5

Completeness

It explicitly answers both "what" (process, clean, and compare spectra with Matchms) and "when" ("use when you need reproducible spectral filtering and similarity scoring for metabolomics workflows"). The "when" clause is present but narrower than anchor 5's concrete trigger enumeration ("or when the user mentions X, Y, Z"), placing it at anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural user terms are present ("mass spectrometry", "MS/MS", "spectra", "Matchms", "metabolomics", "similarity scoring", "filtering"), but common variations like "library matching", "cosine", and file extensions (MGF/MSP) are missing. This matches anchor 4 (good coverage, a few natural terms missing) rather than 3, since coverage clearly exceeds the minimal one-or-two-keyword level.

4 / 5

Distinctiveness Conflict Risk

"mass spectrometry (MS/MS) spectra with Matchms" and "metabolomics workflows" define a clear niche with distinct triggers and minimal overlap risk with other skills, matching anchor 5.

5 / 5

Total

17

/

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