machine-learning-engineer

Align preprocessing, feature generation, model artifacts, and serving integration for training-serving parity.

22|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill machine-learning-engineer-jshsakura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: machine-learning-engineer
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/machine-learning-engineer
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill machine-learning-engineer-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ML systems often drift between training and production, causing degraded performance, inconsistent feature semantics, or fragile deployments. This Skill guides end-to-end alignment across preprocessing, feature flow, model artifacts, and serving integration to reduce drift and accelerate safe improvements.

Core Features & Use Cases

  • End-to-end ML boundary mapping: from feature generation and training artifacts to serving endpoints.
  • Parity validation and artifact versioning: ensure train/serve consistency and safe model promotion.
  • Observability, validation, and safe fixes: measure drift, latency, and errors; implement minimal, verifiable changes.
  • Use Case: When a production model starts behaving unexpectedly, map the pipeline boundaries, identify the root cause, and apply the smallest fix that restores consistency.

Quick Start

Identify the smallest safe change that restores training-serving parity across preprocessing, features, and serving, and implement it.

Frequently Asked Questions about machine-learning-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is training-serving parity in machine learning pipelines?

Training-serving parity ensures identical feature semantics between training and serving environments. It prevents performance degradation by aligning preprocessing, feature generation, and model artifacts across offline and online validation.

How do I fix feature drift between training and production serving?

Map the ML pipeline boundaries from feature generation to serving endpoints to identify the root cause. Apply the smallest safe change that restores training-serving parity across preprocessing and feature flows.

How do I validate model artifacts before deploying to a serving endpoint?

Validate model artifacts by running offline and online parity checks before promotion. This ensures versioned artifacts maintain train and serve consistency, enabling guarded deployments with robust error handling for load failures.

What's the best way to implement observability for an ML serving pipeline?

Implement observability by measuring drift, latency, and errors across the ML pipeline. This validates training-serving alignment and enables minimal, verifiable fixes when a production model behaves unexpectedly.

Why does my production model behave inconsistently after deployment?

Inconsistent production model behavior often stems from training-serving parity issues. Fragile deployments or drifted feature semantics require end-to-end boundary mapping to identify and apply minimal restorative changes.

Can I use this approach for both offline and online ML validation?

Yes, this approach applies to both offline and online validation across end-to-end ML system changes. It ensures robust error handling and guarded deployments while satisfying identical feature semantics between training and serving.