biotender-max/multi-omics-integration
Workflow for integrating matched or partially matched omics layers into shared latent structure and cross-modal interpretation.
npx skills add https://github.com/BioTender-max/awesome-bio-agent-skills --skill multi-omics-integration
Reference examples assume recent stable releases of the preferred tools, especially MOFA+-style and the other tools listed below.
Before using code or command patterns, verify installed versions match the environment:
python -c "import <module>; print(<module>.__version__)"<tool> --versionWorkflow for integrating matched or partially matched omics layers into shared latent structure and cross-modal interpretation.
references/technical_reference.md when you need deeper tool-selection rules, environment adaptation notes, or extra validation guidance.SKILL.md as the main execution path and load the reference file only when the task or failure mode needs the extra detail.Preferred starting point: MOFA+-style
Inputs: multiple omics matrices, sample metadata, feature mapping resources
Outputs: integrated latent factors, cross-modal associations, integrated visualizations
Confirm which samples are shared and how features relate across modalities.
Handle each omics layer according to its data-generating properties before integration.
Use a factor-based or correlation-based method matched to the question and data structure.
Link integrated components back to biology, covariates, and modality-specific loadings.
Save factors, loadings, and modality-aware summaries.
results/ for final tables and serialized objectsfigures/ for plots and static visual exportsqc/ for checks that justify downstream interpretationintegrated latent factorscross-modal associationsintegrated visualizationsPathway AnalysisSystems BiologyCausal GenomicsMachine Learning For Omicsreactome-databasestring-databaseTake biotender-max/multi-omics-integration from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.