LLMs-Universal-Life-Science-and-Clinical-Skills- metabolomics-statistics
install
source · Clone the upstream repo
git clone https://github.com/mdbabumiamssm/LLMs-Universal-Life-Science-and-Clinical-Skills-
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/mdbabumiamssm/LLMs-Universal-Life-Science-and-Clinical-Skills- "$T" && mkdir -p ~/.claude/skills && cp -r "$T/Skills/Metabolomics/metabolomics-statistics" ~/.claude/skills/mdbabumiamssm-llms-universal-life-science-and-clinical-skills-metabolomics-stati && rm -rf "$T"
manifest:
Skills/Metabolomics/metabolomics-statistics/SKILL.mdsource content
📈 Metabolomics Statistical Analysis
Statistical analysis module for metabolomics data. PCA, PLS-DA, hierarchical clustering, and univariate tests.
CLI Reference
python omicsclaw.py run met-stat --demo
Why This Exists
- Without it: Metabolomic variance is inherently high-dimensional and non-trivial to dissect
- With it: Advanced clustering algorithms and projections distill variance into biologically valid groups
- Why OmicsClaw: Wraps complex R/Bioconductor modules into a clear Python execution syntax
Workflow
- Calculate: Compute distance matrices (Euclidean, Pearson).
- Execute: Project high-dimensional structures via PCA/t-SNE/UMAP.
- Assess: Execute hierarchical clustering mapping samples to metabolic profiles.
- Generate: Output coordinate projections.
- Report: Synthesize scree plots, scatter projections, and heatmaps.
Example Queries
- "Run PCA on my normalized metabolomics data"
- "Perform hierarchical clustering with Ward's method"
Output Structure
output_directory/ ├── report.md ├── result.json ├── statistics.csv ├── figures/ │ ├── pca_projection.png │ └── sample_heatmap.png ├── tables/ │ └── principal_components.csv └── reproducibility/ ├── commands.sh ├── environment.yml └── checksums.sha256
Safety
- Local-first: Strict offline processing without external upload.
- Disclaimer: Requires OmicsClaw reporting structures and disclaimers.
- Audit trail: Hyperparameters and operational flow states are logged fully.
Integration with Orchestrator
Trigger conditions:
- Automatically invoked dynamically based on tool metadata and user intent matching.
Chaining partners:
— Upstream data scalingmet-normalize
— Parallel structural differential assessmentmet-diff