K-Dense-AI/scientific-agent-skills

matchms

Process, clean, compare, and search tandem mass spectra with matchms. Use for MS/MS file I/O, metadata harmonization, peak filtering, spectral similarity, library matching, score matrices, and molecular-similarity networks. Use pyopenms instead for LC-MS feature detection or proteomics pipelines.

88Collecting
See how to use itView GitHub source
npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill "skills/matchms"
Automated source guide

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Turn matchms's source instructions into a guide you can follow

According to the pinned SKILL.md from K-Dense-AI/scientific-agent-skills: Process, clean, compare, and search tandem mass spectra with matchms. Use for MS/MS file I/O, metadata harmonization, peak filtering, spectral similarity, library matching, score matrices, and molecular-similarity networks.

npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill "skills/matchms"
Check the pinned source

Best fit

  • Process, clean, compare, and search tandem mass spectra with matchms. Use for MS/MS file I/O, metadata harmonization, peak filtering, spectral similarity, library matching, score matrices, and molecular-similarity networks. Use pyopenms instead for LC-MS feature detection or proteomics pipelines.

Bring this context

  • A concrete task that matches the documented purpose of matchms.
  • The files, examples, or context the task depends on.
  • Your constraints, target environment, and definition of done.

Expected outputs

  • A result that follows the pinned matchms instructions.
  • A concise record of assumptions, inputs used, and unresolved questions.
  • A final check against the source workflow and relevant permission signals.

Key source sections

Read matchms through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

Operating Workflow

1. Inspect the inputs. Record format, spectrum count, MS level, precursor coverage, ion mode, peak counts, and identifier fields. 2. Load with metadata harmonization enabled unless preserving source keys is a deliberate requirement. 3. Apply the same peak-processing steps to que…

SKILL.md · Operating Workflow
Inspect the inputs. Record format, spectrum count, MS level, precursorLoad with metadata harmonization enabled unless preserving source keys isApply the same peak-processing steps to query and reference spectra.
02

Quick Start: Clean and Search a Library

SpectrumProcessor automatically orders built-in filters according to matchms's filter order. The aggregate defaultfilters callable is not in that registry, so run it first as above or expand its nine component filters. Inspect processor.processingsteps and preserve it with resul…

SKILL.md · Quick Start: Clean and Search a Library
SpectrumProcessor automatically orders built-in filters according to matchms's filter order. The aggregate defaultfilters callable is not in that registry, so run it first as above or expand its nine component filters.…
03

Purpose and Scope

Matchms is a Python package for importing, cleaning, processing, and comparing tandem mass spectra. This skill targets matchms 0.33.1, released 2026-06-08, and corrects several breaking API changes that older tutorials do not reflect.

SKILL.md · Purpose and Scope
MS/MS library search and query-versus-reference scoringMetadata harmonization, adduct/precursor handling, and peak filteringCosine, modified-cosine, neutral-loss, approximate, and entropy scoring
04

Install the Verified Release

Create or activate an environment, then install the release used by this skill:

SKILL.md · Install the Verified Release
Create or activate an environment, then install the release used by this skill:Matchms 0.33.1 supports Python 3.10-3.14 and installs RDKit as a regular dependency. The old matchms[chemistry] extra is not part of the current package metadata.
05

Current API Guardrails

These points prevent the most common failures from pre-0.33 examples:

SKILL.md · Current API Guardrails
Use ModifiedCosineGreedy or ModifiedCosineHungarian; ModifiedCosine wasDo not call addlosses(). It was removed in 0.27.0; useSpectrumProcessor is not callable. Use processspectrum() or

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Task-start prompt

Confirm source fit, inputs, and outputs before acting.

Use matchms to help me with: [specific task]. Context: [files, data, or background]. Constraints: [environment, scope, and prohibited actions]. Before acting, check the pinned SKILL.md and explain which sections apply, what inputs are still missing, and what you will deliver.

Source-guided execution

Make the Agent explicitly follow the key extracted sections.

Apply the pinned matchms source to [task]. Pay particular attention to these source sections: “Operating Workflow”, “Quick Start: Clean and Search a Library”, “Purpose and Scope”, “Install the Verified Release”, “Current API Guardrails”. Preserve the important decision at each step. Mark facts not covered by the source as “needs confirmation” instead of inventing them. Then verify the result against my acceptance criteria: [criteria].

Result-review prompt

Check omissions, permissions, and source drift before delivery.

Review the current matchms result: (1) does it satisfy the original task; (2) were any applicable steps or limits in the pinned SKILL.md missed; (3) did it perform any unauthorized file, command, network, or data action; and (4) which conclusions remain unverified? List issues first, then fix only what the source or user authorization supports.

Output checklist

Verify each item before delivery

The task matches the purpose documented in the SKILL.md.

The source section “Operating Workflow” has been checked.

The source section “Quick Start: Clean and Search a Library” has been checked.

The source section “Purpose and Scope” has been checked.

The source section “Install the Verified Release” has been checked.

Inputs, constraints, and acceptance criteria are explicit.

Unverified facts, compatibility, and outcome claims are clearly marked.

Any file, command, network, or data action has been reviewed.

Choose a different workflow

When another Skill is the better fit

simpy

Build, inspect, test, and analyze bounded process-based discrete-event simulations with SimPy, including events, resources, interrupts, monitoring, replications, warm-up, and reproducible output analysis.

A separate implementation from K-Dense-AI/scientific-agent-skills; compare its source, maintenance signals, and permission requirements.

Open source detail

flowstudio-power-automate-build

Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio MCP server. Your agent constructs flow definitions, wires connections, deploys, and tests — all via MCP without opening the portal. Load this skill when asked to: create a flow, build a new flow, deploy a flow definition, scaffold a Power Automate workflow, construct a flow JSON, update an existing flow's actions, patch a flow definition, add actions to a flow, wire up connections, or generate a workflow definition from

A separate implementation from github/awesome-copilot; compare its source, maintenance signals, and permission requirements.

Open source detail

uncertainty-and-units

Track physical units and propagate measurement uncertainty in scientific calculations using pint and uncertainties. Use for unit conversion and dimensional checking, GUM uncertainty budgets, Type A and Type B evaluation, coverage factors and expanded uncertainty, Monte Carlo propagation, significant-figure and plus-minus reporting, error propagation through curve fits, CODATA constants, auditing Python code for stripped units or broken uncertainty propagation, and order-of-magnitude plausibility

A separate implementation from K-Dense-AI/scientific-agent-skills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does matchms do?

Process, clean, compare, and search tandem mass spectra with matchms. Use for MS/MS file I/O, metadata harmonization, peak filtering, spectral similarity, library matching, score matrices, and molecular-similarity networks.

How do I start using matchms?

The catalog detected this source-specific install command: npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill "skills/matchms". Inspect the command and pinned source before running it.

Which Agent platforms does it declare?

No dedicated Agent platform is declared in the pinned source record.

Repository stars
31,966
Repository forks
3,175
Quality
88/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

88/100
Documentation28/30
Specificity18/25
Maintenance20/20
Trust signals22/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

simpy by k-dense-ai

Build, inspect, test, and analyze bounded process-based discrete-event simulations with SimPy, including events, resources, interrupts, monitoring, replications, warm-up, and reproducible output analysis.

flowstudio-power-automate-build by github

Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio MCP server. Your agent constructs flow definitions, wires connections, deploys, and tests — all via MCP without opening the portal. Load this skill when asked to: create a flow, build a new flow, deploy a flow definition, scaffold a Power Automate workflow, construct a flow JSON, update an existing flow's actions, patch a flow definition, add actions to a flow, wire up connections, or generate a workflow definition from

uncertainty-and-units by k-dense-ai

Track physical units and propagate measurement uncertainty in scientific calculations using pint and uncertainties. Use for unit conversion and dimensional checking, GUM uncertainty budgets, Type A and Type B evaluation, coverage factors and expanded uncertainty, Monte Carlo propagation, significant-figure and plus-minus reporting, error propagation through curve fits, CODATA constants, auditing Python code for stripped units or broken uncertainty propagation, and order-of-magnitude plausibility

deployment-patterns by affaan-m

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

pathml by k-dense-ai

Use PathML for local, research-only computational pathology workflows: load and tile slides, build preprocessing and QC pipelines, manage h5path data, quantify multiplex images, construct spatial graphs, and plan bounded model inference.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 5 min

Matchms

Purpose and Scope

Matchms is a Python package for importing, cleaning, processing, and comparing tandem mass spectra. This skill targets matchms 0.33.1, released 2026-06-08, and corrects several breaking API changes that older tutorials do not reflect.

Use matchms for:

  • MS/MS library search and query-versus-reference scoring
  • Metadata harmonization, adduct/precursor handling, and peak filtering
  • Cosine, modified-cosine, neutral-loss, approximate, and entropy scoring
  • Structured score matrices, top-hit extraction, and spectral networks
  • MGF, MSP, mzML, mzXML, JSON, mzSpecLib, and metabolomics-USI workflows

Do not use matchms as a replacement for:

  • LC-MS feature detection, chromatographic alignment, peptide identification, or protein quantification — use pyopenms
  • Vendor raw-file conversion — convert to mzML/mzXML first
  • A validated compound-identification protocol — similarity is evidence, not proof of identity

Install the Verified Release

Create or activate an environment, then install the release used by this skill:

uv pip install "matchms==0.33.1"

Verify the runtime:

uv run python -c "import matchms; print(matchms.__version__)"

Matchms 0.33.1 supports Python 3.10-3.14 and installs RDKit as a regular dependency. The old matchms[chemistry] extra is not part of the current package metadata.

Operating Workflow

  1. Inspect the inputs. Record format, spectrum count, MS level, precursor coverage, ion mode, peak counts, and identifier fields.
  2. Load with metadata harmonization enabled unless preserving source keys is a deliberate requirement.
  3. Apply the same peak-processing steps to query and reference spectra. Keep metadata enrichment separate when reference annotations are richer.
  4. Drop invalid spectra explicitly. Many require_* filters return None.
  5. Choose the score from the scientific question, not from convenience. Modified and neutral-loss scores require valid precursor_mz.
  6. Estimate len(references) * len(queries) before scoring. A sparse result container does not automatically avoid computing every requested pair.
  7. Report score settings and evidence. Include tolerance, preprocessing, score name, number of matched peaks when available, and candidate metadata.
  8. Validate top hits visually and chemically. Use mirror plots, precursor agreement, ion/adduct compatibility, and orthogonal evidence.

Current API Guardrails

These points prevent the most common failures from pre-0.33 examples:

  • Use ModifiedCosineGreedy or ModifiedCosineHungarian; ModifiedCosine was removed in 0.32.0.
  • Do not call add_losses(). It was removed in 0.27.0; use spectrum.losses, spectrum.compute_losses(...), or NeutralLossesCosine directly.
  • SpectrumProcessor is not callable. Use process_spectrum() or process_spectra().
  • process_spectra() returns (processed_spectra, processing_report).
  • Scores.scores is a StackedSparseArray, often with separate structured fields such as CosineGreedy_score and CosineGreedy_matches.
  • scores_by_query() returns (reference_spectrum, score_record) pairs, not reference indices.
  • Prefer spectra in parameter names. The legacy spelling spectrums is deprecated.
  • Never load pickle files from an untrusted source; unpickling can execute code.

See references/migration.md for a complete old-to-current mapping.

Quick Start: Clean and Search a Library

from matchms import SpectrumProcessor, calculate_scores
from matchms.filtering import (
    default_filters,
    normalize_intensities,
    require_minimum_number_of_peaks,
    select_by_relative_intensity,
)
from matchms.importing import load_spectra
from matchms.similarity import ModifiedCosineGreedy


def load_and_process(path):
    spectra = [default_filters(spectrum) for spectrum in load_spectra(path)]
    processor = SpectrumProcessor(
        [
            normalize_intensities,
            (select_by_relative_intensity, {"intensity_from": 0.01}),
            (require_minimum_number_of_peaks, {"n_required": 5}),
        ]
    )
    processed, _ = processor.process_spectra(
        spectra,
        progress_bar=False,
        create_report=False,
    )
    return processed


references = load_and_process("library.msp")
queries = load_and_process("queries.mgf")

metric = ModifiedCosineGreedy(tolerance=0.02)
scores = calculate_scores(
    references=references,
    queries=queries,
    similarity_function=metric,
)

score_name = "ModifiedCosineGreedy_score"
matches_name = "ModifiedCosineGreedy_matches"
for query in queries:
    ranked = scores.scores_by_query(query, name=score_name, sort=True)
    for reference, values in ranked[:5]:
        print(
            query.get("spectrum_id", query.get("id")),
            reference.get("compound_name", reference.get("spectrum_id")),
            float(values[score_name]),
            int(values[matches_name]),
        )

SpectrumProcessor automatically orders built-in filters according to matchms's filter order. The aggregate default_filters callable is not in that registry, so run it first as above or expand its nine component filters. Inspect processor.processing_steps and preserve it with results.

Pair Scoring

Similarity classes expose pair() for one reference/query pair. Cosine-family results are structured NumPy scalars:

from matchms.similarity import CosineGreedy

result = CosineGreedy(tolerance=0.02).pair(reference, query)
similarity = float(result["score"])
matched_peaks = int(result["matches"])

Use calculate_scores() for matrix-oriented methods such as FlashSimilarity; its single-pair path is supported but intentionally not the optimized path.

Choose a Similarity Method

  • CosineGreedy — standard peak cosine with greedy peak assignment.
  • CosineHungarian — exact assignment; slower, useful for benchmarks.
  • CosineLinear — current linear-scaling cosine implementation.
  • ModifiedCosineGreedy — permits precursor-delta-shifted matches; common for analog search.
  • ModifiedCosineHungarian — exact modified-cosine assignment.
  • NeutralLossesCosine — compares losses computed from precursor and fragments.
  • BlinkCosine — fast BLINK-style cosine approximation for larger matrices.
  • FlashSimilarity — optimized matrix scoring using spectral entropy or cosine with fragment, neutral-loss, or hybrid matching.
  • BinnedEmbeddingSimilarity — binned spectral vectors and optional approximate nearest-neighbor indexing.
  • PrecursorMzMatch, ParentMassMatch, MetadataMatch — candidate masks or metadata constraints, not rich spectral scores.
  • FingerprintSimilarity — molecular-structure similarity; it is not spectral similarity and requires fingerprints prepared from valid structures.

Read references/similarity.md before choosing a fast method, combining scores, or interpreting structured outputs.

Large Comparisons

For all-vs-all scoring of one collection, set is_symmetric=True:

scores = calculate_scores(
    references=spectra,
    queries=spectra,
    similarity_function=CosineGreedy(tolerance=0.02),
    array_type="sparse",
    is_symmetric=True,
)

For a precursor-gated search, compute and filter PrecursorMzMatch first, then calculate the spectral metric only on retained coordinates through Pipeline or Scores.calculate(...). See references/workflows.md.

Do not choose a universal "identification threshold." Score distributions depend on preprocessing, mass accuracy, collision conditions, library quality, and metric. At minimum, retain both score and matched-peak count for cosine-family methods.

Bundled Library-Search CLI

scripts/library_search.py provides a reproducible query-versus-library search with current score extraction, pair-count limits, preprocessing, and CSV output:

uv run python scripts/library_search.py \
  queries.mgf library.msp hits.csv \
  --metric modified \
  --tolerance 0.02 \
  --top-k 10 \
  --min-score 0.6 \
  --min-matches 5

Run --help for fast metrics, preprocessing options, identifier fields, overwrite control, and the explicit large-matrix override.

Spectrum Objects and Visualization

import numpy as np
from matchms import Spectrum

spectrum = Spectrum(
    mz=np.array([100.0, 150.0, 200.0]),
    intensities=np.array([0.2, 1.0, 0.4]),
    metadata={"spectrum_id": "query-1", "precursor_mz": 250.5},
)

print(spectrum.peaks.mz)
print(spectrum.get("precursor_mz"))
losses = spectrum.compute_losses(loss_mz_from=5.0, loss_mz_to=200.0)
spectrum.plot()
spectrum.plot_against(reference_spectrum)

References

Read only the reference needed for the task:

  • references/importing_exporting.md — formats, return types, generic I/O, mzSpecLib, score serialization, and pickle safety
  • references/filtering.md — current filter catalog, clone/None semantics, default filters, ordering, and SpectrumProcessor
  • references/similarity.md — all current similarity classes, outputs, candidate masking, performance, and interpretation
  • references/workflows.md — library search, sparse gating, Pipeline, networks, plotting, and provenance
  • references/migration.md — breaking changes and deprecated APIs
  • references/sources.md — authoritative docs, release notes, user guides, and scientific publications used for this refresh

Non-Negotiable Checks

  • Never compare raw queries against differently processed references.
  • Never use modified or neutral-loss scoring without valid precursor metadata.
  • Never assume a Scores value is a plain float; inspect score_names.
  • Never treat a high similarity score alone as confirmed identification.
  • Never deserialize untrusted pickle data.
  • Never launch an unbounded all-pairs comparison without estimating pair count.
Skill path
skills/matchms/SKILL.md
Commit SHA
e7ac42510774
Repository license
MIT
Data collected