agentsclimarketplace

Metabolomic network edge type prioritization

Skill HolobiomicsLab/asb-skill-collections/collections/metabolomics/v2/skills/metabolomic-network-edge-type-prioritization

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 metabolomic-network-edge-type-prioritization

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 when your metabolomic network contains multiple edge types (Biochemical, Structural, Mass Spectral, Correlation) between the same node pairs and you want to export a unique-edge network in which each node pair is connected by exactly one edge—the one with highest priority according to the.

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, as published. Nobody here has run it

metabolomic-network-edge-type-prioritization

Summary

Filter a metabolomic network to retain only one edge per node pair by applying a fixed priority hierarchy across edge types (Biochemical > Structural > Mass Spectral > Correlation). This is used when multiple edges of different types connect the same nodes and you need a simplified, non-redundant network representation.

When to use

When your metabolomic network contains multiple edge types (Biochemical, Structural, Mass Spectral, Correlation) between the same node pairs and you want to export a unique-edge network in which each node pair is connected by exactly one edge—the one with highest priority according to the Biochemical > Structural > Mass Spectral > Correlation hierarchy. This is applicable when the user enables the 'unique edges' checkbox in MetaMapR's network tab.

When NOT to use

  • Your network contains only a single edge type per node pair (no filtering needed).
  • You want to preserve all edge types for downstream analysis (use 'return all edges' mode instead).
  • You require partial correlations or other edge types not yet implemented in MetaMapR.

Inputs

  • metabolomic network with multiple edge types
  • edge list with source node ID, target node ID, and edge type (Biochemical|Structural|Mass Spectral|Correlation)

Outputs

  • filtered metabolomic network (unique edges per node pair)
  • cytoscape.js-compatible JSON network representation

How to apply

Load the input network containing all edge types between metabolite/protein node pairs. Group edges by their source–target node pair identifier. For each pair with multiple edges, compare the edge types and select the single edge with the highest priority in the fixed hierarchy: Biochemical (highest) > Structural > Mass Spectral > Correlation (lowest). Discard all other edges for that pair. Construct the filtered network containing only the selected edges, then export in cytoscape.js-compatible JSON format. The rationale is that Biochemical edges represent the strongest mechanistic evidence, so they are preferred when present; if absent, the next-highest priority type is chosen, ensuring deterministic and reproducible filtering.

Related tools

  • MetaMapR (Primary network filtering and export tool; implements the unique-edges checkbox and edge-type hierarchy selection) — https://github.com/dgrapov/MetaMapR
  • cytoscape.js (Target format for filtered network export and visualization)

Evaluation signals

  • Verify that the output network has exactly one edge per unique source–target node pair (no duplicate pairs).
  • Check that for any node pair that had multiple edge types in the input, only the highest-priority edge type is retained in the output.
  • Confirm the output JSON is valid cytoscape.js format and can be imported without parsing errors.
  • Manually inspect a sample of node pairs that had multiple edge types: verify the retained edge matches the hierarchy (e.g., if Biochemical and Mass Spectral were both present, only Biochemical remains).
  • Compare edge count between input (all edges) and output (unique edges): output should have fewer or equal edges.

Limitations

  • The priority hierarchy is fixed and not user-customizable in the current implementation.
  • Partial correlations are not yet supported as an edge type.
  • The network mapping feature is still under development.
  • Edge type assignment must be reliable upstream; errors in edge-type classification will propagate through the filtering step.

Evidence

  • [readme] The priority hierarchy and when it is applied: "If the option is selected then edges are returned based on a hierarchy Biochemical > Structural > Mass Spectral > Correlation"
  • [other] Input data structure and node-pair grouping logic: "Group edges by their source–target node pair. For each node pair with multiple edges, select the single edge with the highest priority according to the hierarchy"
  • [other] Output format specification: "Export the filtered network in a cytoscape.js-compatible format (JSON)"
  • [readme] Rationale for the hierarchy ordering: "The default setting for returning all edge types or only unique edges can be found under the network tab using the unique edges checkbox"

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.