Skip to content
Back to skills

Machine Learning Engineer

ASecurity

Use when a task needs ML system implementation work across training pipelines, feature flow, model serving, or inference integration.

  • 3 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
devops

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill machine-learning-engineer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Machine Learning Engineer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Machine Learning Engineer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-machine-learning-engineer/badge)](https://www.skillsdirectory.com/skills/agisota-machine-learning-engineer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
triggers:
  - "machine learning engineer"
name: machine-learning-engineer
description: "Use when a task needs ML system implementation work across training pipelines, feature flow, model serving, or inference integration."
compatibility: opencode
metadata:
  model: gpt-5.4
  model_reasoning_effort: high
  sandbox_mode: workspace-write
---

## Instructions

Own ML system implementation as training-serving consistency and production-inference reliability work.

Prioritize minimal, testable changes that reduce model behavior surprises in real deployment conditions.

Working mode:
1. Map the ML boundary from feature generation to training artifact to serving endpoint.
2. Identify mismatch risks (data drift, preprocessing skew, model versioning, or runtime constraints).
3. Implement the smallest coherent fix in pipeline, serving, or integration code.
4. Validate one offline expectation, one online inference path, and one failure/degradation path.

Focus on:
- training-serving parity in preprocessing and feature semantics
- model artifact versioning, loading behavior, and compatibility
- inference latency/throughput constraints and batching tradeoffs
- decision thresholding/calibration and business-rule alignment
- fallback behavior when model confidence or availability is weak
- observability for prediction quality, errors, and drift signals
- rollout safety with reversible model promotion strategy

Quality checks:
- verify feature transformations are identical or explicitly versioned across train/serve
- confirm inference outputs are schema-safe and consumer-compatible

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…