agentsclimarketplace

Router

Skill HolobiomicsLab/asb-skill-collections/collections/metabolomics/v2/skills/_router

Use when an agent needs to find and apply a computational-metabolomics / LC-MS-MS skill from this collection, and optionally ground it against the source paper via Perspicacité before acting.From its SKILL.md

Install
npx -y skills add HolobiomicsLab/asb-skill-collections --skill _router

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

  • 15 stars15 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 file declares

Copied from the file, not written here

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

5.5 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it

ASB Metabolomics Skill Collection — router

This is the default entry point for the ASB Metabolomics collection (v2): 5,865 evidence-grounded skills and 909 software-tool records for computational metabolomics — predominantly LC-MS/MS, but also LC-MS, GC-MS, mass-spectrometry imaging, ion mobility, lipidomics, and some NMR / multi-omics — each derived from a peer-reviewed method paper and its public code repository.

You (the agent) use this router in three steps: search → apply → (optionally) ground.

1. Search — find the right skill

Every skill is one skills/<slug>/SKILL.md with YAML frontmatter. Two machine indexes at the collection root make lookup cheap — load whichever fits:

  • skills_index.json — one row per skill: slug, name, description, edam_operation, edam_topics, tools, dois, techniques.
  • tools_index.json — one row per tool: slug, name, canonical_url, edam_topics, dois.

Pick a skill by matching the user's task against, in order of precision:

  1. Technique (techniques) — analytical platform tags: LC-MS (incl. LC-MS/MS), GC-MS, CE-MS, direct-infusion-MS, MS-imaging, ion-mobility-MS, NMR, mass-spectrometry (generic). e.g. jq '.[]|select(.techniques[]?=="LC-MS")'.
  2. EDAM operation/topic IRI — exact ontology match (e.g. peak picking = operation_3215, spectral library matching, formula prediction).
  3. Tool name — the user already names a tool ("run XCMS", "use SIRIUS", "GNPS molecular networking", "MZmine", "matchms").
  4. Keyword over name + description.

Then read that skill's skills/<slug>/SKILL.md and follow it.

2. Apply — use the skill

The skill body carries the procedure; its frontmatter carries tools (what to install/invoke), derived_from (source paper DOIs), and evidence_spans (verbatim anchors from the paper/repo). Use the tool records in tools_index.json for canonical install URLs.

3. Ground (recommended) — verify against the source via Perspicacité

Before trusting a parameter, claim, or default, ground the skill against the paper it was built from. The mapping skill → source DOI(s) → KB is precomputed in kb_bundle.json (each skill's kb_slugs are the SAME asb-paper-<doi> KBs the collection was assembled against). A running Perspicacité instance plus scripts/perspicacite_kb_bind.py makes this one command:

# auto-create + ingest the skill's KB (paper full text + supplementary info),
# then ask a grounded, cited question against it:
python scripts/perspicacite_kb_bind.py query \
  --collection collections/metabolomics/v2 \
  --skill <slug> \
  --question "<what you need to verify>"

The KB is generated on first use (idempotent — reused thereafter). Choose the grounding tier with --tier:

tiergrounds againstuse for
paper (default)paper full text + supplementary informationparameters, claims, methods
sisupplementary tables/figures emphasisedexact thresholds, benchmark numbers
repothe tool's source repo (no KB; returns repo URLs)implementation details, CLI flags

prepare (build the KB without querying) and resolve (print the grounding map offline) are the other two subcommands.

License tier

When routing or presenting candidate skills, read each candidate's license_tier from skills_index.json or the skill's SKILL.md frontmatter (metadata.license_tier). Apply the following rules, in addition to normal routing logic:

  • open — surface freely; no gate required. Discovery defaults to open-tier skills whenever the consumer has not expressed a specific tier preference.
  • noncommercial — flag the blocking acknowledgment before applying the skill: commercial use is forbidden without a separate license. Defer to the asb-metabolomics gate (which checks metadata.tool_license) — the user must explicitly confirm a permitted (academic / noncommercial) purpose. Do not apply a noncommercial skill until the acknowledgment is confirmed.
  • restricted — show the soft note: "no clear license detected — verify before commercial use or redistribution" (non-blocking). Proceed only after surfacing this caveat.

All other routing behavior (technique, EDAM, tool name, keyword matching) is unchanged; tier-awareness is an additional layer applied after candidate selection.

Provenance

Each skill is grounded (derived_from DOIs + evidence_spans), license-tagged (CC-BY-4.0), and EDAM-annotated. Non-open-access sources and ungrounded skills were held out at release. See corpus.yaml for the per-paper access basis (repo-oa: the redistributable source repository was cloned at build time) and gate_report.json for the passing release-gate verdict.

What ships with it

Read from the repository

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

Keep looking

Skills are one crate of 325,949. 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.