agentsclimarketplace

R function calling

Skill HolobiomicsLab/asb-skill-collections/collections/metabolomics/v2/skills/r-function-calling

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 r-function-calling

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 after AutoTuner has completed peak identification (TIC analysis), peak isolation, and EIC parameter extraction on at least 3 raw mass spectrometry samples (qTOF, orbitrap, or FTICR formats converted to mzML/mzXML/CDF), and you need to export the tuned parameters in a format ready for XCMS.

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

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

Extract parameter estimates via R function call

Summary

Call the returnParams R function on an AutoTuner object to extract nine optimized parameter estimates for direct input into XCMS or other metabolomics processing software. This skill bridges AutoTuner's statistical parameter inference with downstream tool configuration.

When to use

After AutoTuner has completed peak identification (TIC analysis), peak isolation, and EIC parameter extraction on at least 3 raw mass spectrometry samples (qTOF, orbitrap, or FTICR formats converted to mzML/mzXML/CDF), and you need to export the tuned parameters in a format ready for XCMS processing of untargeted metabolomics data.

When NOT to use

  • AutoTuner has not yet completed EICparams extraction — call EICparams() and isolatePeaks() first.
  • Your input data consists of fewer than 3 raw samples — AutoTuner requires at least 3 samples for robust parameter estimation.
  • You are working with targeted metabolomics or already have manually tuned parameters — returnParams is designed for untargeted parameter discovery, not refinement of existing parameter sets.

Inputs

  • AutoTuner object (R) with completed EICparams and peak isolation results
  • Raw mass spectrometry data files (mzML, mzXML, or CDF format) used to generate the AutoTuner object

Outputs

  • Parameter estimate table (nine distinct parameters)
  • Structured parameter file (CSV or TSV) formatted for XCMS input
  • Parameter vector suitable for direct entry into xcmsSet() or related XCMS functions

How to apply

Load the AutoTuner object containing completed EICparams results into an R session (R ≥ 3.6). Call the returnParams function on the AutoTuner object; this extracts the nine distinct parameter estimates produced by statistical inference from the sliding-window TIC analysis and EIC bounds expansion. Format the returned parameter table as a structured file (CSV or TSV) suitable for direct ingestion by XCMS or MZmine2. The output parameters encapsulate peak detection thresholds, mass error bounds, and chromatographic feature definitions learned from your specific dataset and instrument, eliminating manual trial-and-error tuning.

Related tools

  • Autotuner (Source object containing parameter estimates; returnParams is an Autotuner class method) — https://github.com/KujawinskiLaboratory/Autotuner
  • XCMS (Downstream consumer of the nine returned parameter estimates for peak detection and feature alignment in untargeted metabolomics)
  • MZmine2 (Alternative downstream consumer of AutoTuner parameter estimates for metabolomics data processing)
  • R (Runtime environment for loading AutoTuner and executing returnParams function call)

Examples

# Load AutoTuner library and object, then call returnParams
library(Autotuner)
params <- returnParams(autotuner_object)
write.csv(params, file='autotuner_xcms_params.csv', row.names=FALSE)

Evaluation signals

  • returnParams returns exactly nine parameter estimates (no more, no fewer) that match the documented AutoTuner output schema.
  • Returned parameter values are numeric, within expected ranges for mass error (typically < 50 ppm), retention time windows (seconds), and peak width bounds (in scan units or seconds depending on instrument).
  • Exported CSV/TSV file can be read back and successfully passed to XCMS::xcmsSet() or equivalent function without format errors.
  • Parameter estimates are consistent with the input dataset's instrument type (qTOF, orbitrap, or FTICR) and are more permissive/accurate than generic defaults used without AutoTuner.
  • The nine parameters include representatives of mass accuracy, peak width, peak intensity threshold, and retention time clustering parameters documented in AutoTuner publication.

Limitations

  • AutoTuner requires R ≥ 3.6; older versions are not supported.
  • Input raw data must be in open formats (mzML, mzXML, CDF) — proprietary instrument formats (e.g., .raw, .d) must be converted via MSconvert first.
  • AutoTuner has been tested on qTOF, orbitrap, and FTICR instruments; performance on other mass analyzer types is unknown.
  • A metadata spreadsheet with sample names and experimental factor assignments must be prepared separately; returnParams alone does not infer experimental design.
  • No changelog is available in the repository, making it difficult to track version-specific changes to the returnParams output schema.

Evidence

  • [other] The returnParams function outputs parameter estimates from EICparams results and the AutoTuner object that can be entered directly into XCMS to process raw untargeted metabolomics data.: "The returnParams function outputs parameter estimates from EICparams results and the AutoTuner object that can be entered directly into XCMS"
  • [intro] Using statistical inference, AutoTuner quickly finds estimates for nine distinct parameters.: "Using statistical inference, AutoTuner quickly finds estimates for nine distinct parameters."
  • [intro] AutoTuner is a parameter tuning algorithm for XCMS, MZmine2, and other metabolomics data processing softwares.: "AutoTuner is a parameter tuning algorithm for XCMS, MZmine2, and other metabolomics data processing softwares."
  • [readme] For input, AutoTuner requires at least 3 samples of raw data converted from proprietary instrument formats (eg .mzML, .mzXML, or .CDF).: "AutoTuner requires at least 3 samples of raw data converted from proprietary instrument formats (eg .mzML, .mzXML, or .CDF)"
  • [readme] AutoTuner has been tested on untargeted data generated on qTOF, orbitrap and Fourier transform ion cyclotron resonance mass analyzers.: "AutoTuner has been tested on untargeted data generated on qTOF, orbitrap and Fourier transform ion cyclotron resonance mass analyzers."

Gives 0 of the 12 instructions most mcp tooling skills give in ~1.2k tokens

Counted across 638 of the 750 authors here whose files we hold, read 2026-08-07

  • create ten complex read-only evaluation questionsin 69 of 638, across 15 files
  • test servers using MCP Inspectorin 61 of 638, across 19 files
  • provide actionable error messagesin 54 of 638, across 12 files
  • prioritize comprehensive API coverage over specific workflowsin 54 of 638, across 12 files
  • use TypeScript and Streamable HTTP for remote serversin 54 of 638, across 8 files
  • define structured output schemas where possiblein 50 of 638, across 8 files
  • use Zod or Pydantic for input schemasin 47 of 638, across 5 files
  • fetch MCP specification pages with markdown suffixin 46 of 638, across 4 files
  • load framework documentation using WebFetchin 45 of 638, across 3 files
  • verify each evaluation answer independentlyin 45 of 638, across 3 files
  • implement API client with authentication and paginationin 45 of 638, across 3 files
  • Define input schemas with validationin 27 of 638, across 9 files

Said here and by no other author read

  • execute EICparams and isolatePeaks first
  • provide at least three raw samples
  • convert proprietary formats to open formats
  • load the AutoTuner object into R
  • call returnParams on the AutoTuner object
  • verify exactly nine parameter estimates are returned

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

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.