Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Deploy ML models to production with pipelines, monitoring, serving, and reproducibility best practices.
Deploy ML models to production with pipelines, monitoring, serving, and reproducibility best practices.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
TopicFileKey TrapCI/CD and DAGspipelines.mdCoupling training/inference depsModel servingserving.mdCold start with large modelsDrift and alertsmonitoring.mdOnly technical metricsVersioningreproducibility.mdNot versioning preprocessingGPU infrastructuregpu.mdGPU request = full device
Training-Serving Skew: Preprocessing in notebook β preprocessing in service β silent bugs Pandas in notebook β memory leaks in production (use native types) Feature store values at training time β serving time without proper joins GPU Memory: requests.nvidia.com/gpu: 1 reserves ENTIRE GPU, not partial memory MIG/MPS sharing has real limitations (not plug-and-play) OOM on GPU kills pod with no useful logs Model Versioning β Code Versioning: Model artifacts need separate versioning (MLflow, W&B, DVC) Training data version + preprocessing version + code version = reproducibility Rollback requires keeping old model versions deployable Drift Detection Timing: Retraining trigger isn't just "drift > threshold" β cost/benefit matters Delayed ground truth makes concept drift detection lag weeks Upstream data pipeline changes cause drift without model issues
This skill ONLY covers: CI/CD pipelines for models Model serving and scaling Monitoring and drift detection Reproducibility practices GPU infrastructure patterns Does NOT cover: ML algorithms, feature engineering, hyperparameter tuning.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.