agentsclimarketplace

Metadata field validation

Skill HolobiomicsLab/asb-skill-collections/collections/metabolomics/v2/skills/metadata-field-validation

Curated, evidence-grounded skill and software-tool collections for scientific AI agents, generated by the AgenticScienceBuilder

Install
npx -y skills add HolobiomicsLab/asb-skill-collections --skill metadata-field-validation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when you have received new or updated MassBank records (in plain-text or structured format) that must be integrated into the MassBank-data repository and you need to ensure they conform to the MassBank format specification before acceptance.

The file declares its own license as CC-BY-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.0 KB, 983 tokens by cl100k_base, as published. Nobody here has run it

metadata-field-validation

License: restricted — no clear open-source license detected for the underlying tool; verify licensing before commercial use or redistribution. <!-- asb-license-banner -->

Summary

Automated validation of structured metadata records against a defined schema and rule set to ensure content conformance before integration into a curated repository. This skill enforces data type, format, presence, and value-range constraints across all fields in a record.

When to use

Apply this skill when you have received new or updated MassBank records (in plain-text or structured format) that must be integrated into the MassBank-data repository and you need to ensure they conform to the MassBank format specification before acceptance. Use it as part of a continuous integration workflow to catch validation failures early.

When NOT to use

  • Records that are already pre-validated and archived in Zenodo or a stable release
  • Ad-hoc exploratory analysis where schema enforcement is not required
  • Raw spectral data before metadata extraction and structuring

Inputs

  • MassBank record file (plain-text or structured format)
  • MassBank record string
  • Record metadata fields (accession, name, formula, mass, spectrum peaks)

Outputs

  • Validation report with passed and failed checks
  • Specific error messages for each failed rule
  • Validation status badge (pass/fail) for CI workflow

How to apply

Load a MassBank record from an input file or string and parse its metadata fields (accession, name, formula, mass, spectrum peaks, etc.) according to the MassBank format specification. Apply the validation rules implemented in MassBank-web Validator.java, which check field presence, data type, value range, and format constraints. Collect validation errors or warnings for each failed rule. Generate a validation report listing passed and failed checks with specific error messages. Use GitHub Actions to invoke validation automatically on every commit or pull request to main and dev branches.

Related tools

Evaluation signals

  • All required metadata fields are present in the record
  • Field values conform to specified data types and format constraints
  • Numeric values (mass, m/z, intensity) fall within acceptable ranges
  • Validation report shows zero errors (warnings may be acceptable)
  • CI workflow badge shows passing status on the main and dev branches

Limitations

  • The MassBank-web repository is deprecated; validators are now maintained in MassBank-cli-tools, which may have different rule sets or invocation patterns
  • No changelog is available to track changes to validation rules over time
  • Validation rules are enforced at the syntax and schema level but do not assess biological or chemical accuracy of record content

Evidence

  • [other] Parse the record's metadata fields (accession, name, formula, mass, spectrum peaks, etc.) according to MassBank format specification.: "Parse the record's metadata fields (accession, name, formula, mass, spectrum peaks, etc.) according to MassBank format specification."
  • [other] Apply the validation rules implemented in MassBank-web Validator.java (field presence, data type, value range, format constraints).: "Apply the validation rules implemented in MassBank-web Validator.java (field presence, data type, value range, format constraints)."
  • [other] Collect validation errors or warnings for each failed rule. Generate a validation report listing passed and failed checks with specific error messages.: "Collect validation errors or warnings for each failed rule. Generate a validation report listing passed and failed checks with specific error messages."
  • [readme] uses GitHub Actions to validate the content of all records with the Validator from MassBank-web: "uses GitHub Actions to validate the content of all records with the Validator from MassBank-web"
  • [readme] This repo is deprecated. Please do not use it! The new MassBank web app is maintained in repo https://github.com/MassBank/MassBank3. The validator and other command line tools are maintained in https://github.com/MassBank/MassBank-cli-tools: "The validator and other command line tools are maintained in https://github.com/MassBank/MassBank-cli-tools"

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.