LLMs-Universal-Life-Science-and-Clinical-Skills- proteomics-ms-qc
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/Proteomics/proteomics-ms-qc" ~/.claude/skills/mdbabumiamssm-llms-universal-life-science-and-clinical-skills-proteomics-ms-qc && rm -rf "$T"
manifest:
Skills/Proteomics/proteomics-ms-qc/SKILL.mdsource content
📊 Proteomics MS-QC
Mass spectrometry data quality control. Computes basic QC statistics for protein/peptide abundance tables.
CLI Reference
python omicsclaw.py run proteomics-ms-qc --demo python omicsclaw.py run proteomics-ms-qc --input <data.csv> --output <dir>
Why This Exists
- Without it: Instrument drift, missed cleavages, or poor LC gradients ruin quantitative integrity
- With it: Identifies bad samples early before costly downstream statistical processing
- Why OmicsClaw: Provides a unified mass-spectrometer agnostic report dashboard
Workflow
- Calculate: Extract basic peptide features and contaminant ratios.
- Execute: Run descriptive statistics across raw files.
- Assess: Flag outliers outside expected robust median ranges.
- Generate: Output normalized QC matrices.
- Report: Synthesize multiple metric traces across runs.
Example Queries
- "Run mass spec QC on this data using PTXQC"
- "Assess proteomics instrument performance"
Output Structure
output_directory/ ├── report.md ├── result.json ├── metrics.csv ├── figures/ │ └── qc_dashboard.pdf ├── tables/ │ └── qc_summary.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 format parsingdata-import
— Downstream normalized feature tablesquantification