affaan-m/everything-claude-code/mle-workflow

Claude Code and agent skill by affaan-m/everything-claude-code

Trust tier 3
  • community
  • ext:[{"type":"hook","description":"Pre/post lifecycle hooks"}]
Source check pending

Checking that the SKILL.md file is still in the repository.

Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.

Install

npx vskill@latest install affaan-m/everything-claude-code/mle-workflow

Semi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard

SKILL.md

The same SKILL.md was published earlier as affaan-m/ecc/mle-workflow.

Machine Learning Engineering Workflow

Use this skill to turn model work into a production ML system with clear data contracts, repeatable training, measurable quality gates, deployable artifacts, and operational monitoring.

When to Activate

  • Planning or reviewing a production ML feature, model refresh, ranking system, recommender, classifier, embedding workflow, or forecasting pipeline
  • Converting notebook code into a reusable training, evaluation, batch inference, or online inference pipeline
  • Designing model promotion criteria, offline/online evals, experiment tracking, or rollback paths
  • Debugging failures caused by data drift, label leakage, stale features, artifact mismatch, or inconsistent training and serving logic
  • Adding model monitoring, canary rollout, shadow traffic, or post-deploy quality checks

Scope Calibration

Use only the lanes that fit the system in front of you. This skill is useful for ranking, search, recommendations, classifiers, forecasting, embeddings, LLM workflows, anomaly detection, and batch analytics, but it should not force one architecture onto all of them.

  • Do not assume every model has supervised labels, online serving, a feature store, PyTorch, GPUs, human review, A/B tests, or real-time feedback.
  • Do not add heavyweight MLOps machinery when a data contract, baseline, eval script, and rollback note would make the change reviewable.
  • Do make assumptions explicit when the project lacks labels, delayed outcomes, slice definitions, production traffic, or monitoring ownership.
  • Treat examples as interchangeable scaffolds. Replace metrics, serving mode, data stores, and rollout mechanics with the project-native equivalents.

Related Skills

  • python-patterns and python-testing for Python implementation and pytest coverage
  • pytorch-patterns for deep learning models, data loaders, device handling, and training loops
  • eval-harness and ai-regression-testing for promotion gates and agent-assisted regression checks
  • database-migrations, postgres-patterns, and clickhouse-io for data storage and analytics surfaces
  • deployment-patterns, docker-patterns, and security-review for serving, secrets, containers, and production hardening

Reuse the SWE Surface

Do not treat MLE as separate from software engineering. Most ECC SWE workflows apply directly to ML systems, often with stricter failure modes:

The recommended minimal --with capability:machine-learning install keeps the core agent surface available alongside this skill. For skill-only or agent-limited harnesses, pair skill:mle-workflow with agent:mle-reviewer where the target supports agents.

SWE surfaceMLE use
product-capability / architecture-decision-recordsTurn model work into explicit product contracts and record irreversible data, model, and rollout choices
repo-scan / codebase-onboarding / code-tourFind existing training, feature, serving, eval, and monitoring paths before introducing a parallel ML stack
plan / feature-devScope model changes as product capabilities with data, eval, serving, and rollback phases
tdd-workflow / python-testingTest feature transforms, split logic, metric calculations, artifact loading, and inference schemas before implementation
code-reviewer / mle-reviewerReview code quality plus ML-specific leakage, reproducibility, promotion, and monitoring risks
build-fix / pr-test-analyzerDiagnose broken CI, flaky evals, missing fixtures, and environment-specific model or dependency failures
quality-gate / test-coverageRequire automated evidence for transforms, metrics, inference contracts, promotion gates, and rollback behavior
eval-harness / verification-loopTurn offline metrics, slice checks, latency budgets, and rollback drills into repeatable gates
ai-regression-testingPreserve every production bug as a regression: missing feature, stale label, bad artifact, schema drift, or serving mismatch
api-design / backend-patternsDesign prediction APIs, batch jobs, idempotent retraining endpoints, and response envelopes
database-migrations / postgres-patterns / clickhouse-ioVersion labels, feature snapshots, prediction logs, experiment metrics, and drift analytics
deployment-patterns / docker-patternsPackage reproducible training and serving images with health checks, resource limits, and rollback
canary-watch / dashboard-builderMake rollout health visible with model-version, slice, drift, latency, cost, and delayed-label dashboards
security-review / security-scanCheck model artifacts, notebooks, prompts, datasets, and logs for secrets, PII, unsafe deserialization, and supply-chain risk
e2e-testing / browser-qa / accessibilityTest critical product flows that consume predictions, including explainability and fallback UI states
benchmark / performance-optimizerMeasure throughput, p95 latency, memory, GPU utilization, and cost per prediction or retrain
cost-aware-llm-pipeline / token-budget-advisorRoute LLM/embedding workloads by quality, latency, and budget instead of defaulting to the largest model
documentation-lookup / search-firstVerify current library behavior for model serving, feature stores, vector DBs, and eval tooling before coding
git-workflow / github-ops / opensource-pipelinePackage MLE changes for review with crisp scope, generated artifacts excluded, and reproducible test evidence
strategic-compact / dmux-workflowsSplit long ML work into parallel tracks: data contract, eval harness, serving path, monitoring, and docs

Ten MLE Task Simulations

Use these simulations as coverage checks when planning or reviewing MLE work. A strong MLE workflow should reduce each task to explicit contracts, reusable SWE surfaces, automated evidence, and a reviewable artifact.

IDCommon MLE taskStreamlined ECC pathRequired outputPipeline lanes covered
MLE-01Frame an ambiguous prediction, ranking, recommender, classifier, embedding, or forecast capabilityproduct-capability, plan, architecture-decision-records, mle-workflowIteration Compact naming who cares, decision owner, success metric, unacceptable mistakes, assumptions, constraints, and first experimentproduct contract, stakeholder loss, risk, rollout
MLE-02Define metric goals, labels, data sources, and the mistake budgetrepo-scan, database-reviewer, database-migrations, postgres-patterns, clickhouse-ioData and metric contract with entity grain, label timing, label confidence, feature timing, point-in-time joins, split policy, and dataset snapshotdata contract, metric design, leakage, reproducibility
MLE-03Build a baseline model and scoring path before adding complexitytdd-workflow, python-testing, python-patterns, code-reviewerBaseline scorer with confusion matrix, calibration notes, latency/cost estimate, known weaknesses, and tests for score shape and determinismbaseline, scoring, testing, serving parity
MLE-04Generate features from hypotheses about what separates outcomespython-patterns, pytorch-patterns, docker-patterns, deployment-patternsFeature plan and transform module covering signal source, missing values, outliers, correlations, leakage checks, and train/serve equivalencefeature pipeline, leakage, training, artifacts
MLE-05Tune thresholds, configs, and model complexity under tradeoffseval-harness, ai-regression-testing, quality-gate, test-coverageThreshold/config report comparing precision, recall, F1, AUC, calibration, group slices, latency, cost, complexity, and acceptable error classesevaluation, threshold, promotion, regression
MLE-06Run error analysis and turn mistakes into the next experimenteval-harness, ai-regression-testing, mle-reviewer, silent-failure-hunterError cluster report for false positives, false negatives, ambiguous labels, stale features, missing signals, and bug traces with lessons capturederror analysis, bug trace, iteration, regression
MLE-07Package a model artifact for batch or online inferenceapi-design, backend-patterns, security-review, security-scanVersioned artifact bundle with preprocessing, config, dependency constraints, schema validation, safe loading, and PII-safe logsartifact, security, inference contract
MLE-08Ship online serving or batch scoring with feedback captureapi-design, backend-patterns, e2e-testing, browser-qa, accessibilityPrediction endpoint or batch job with response envelope, timeout, batching, fallback, model version, confidence, feedback logging, and product-flow testsserving, batch inference, fallback, user workflow
MLE-09Roll out a model with shadow traffic, canary, A/B test, or rollbackcanary-watch, dashboard-builder, verification-loop, performance-optimizerRollout plan naming traffic split, dashboards, p95 latency, cost, quality guardrails, rollback artifact, and rollback triggerdeployment, canary, rollback
MLE-10Operate, debug, and refresh a production model after launchsilent-failure-hunter, dashboard-builder, mle-reviewer, doc-updater, github-opsObservation ledger and refresh plan with drift checks, delayed-label health, alert owners, runbook updates, retrain criteria, and PR evidencemonitoring, incident response, retraining

Iteration Compact

Before touching model code, compress the work into one reviewable artifact. This should be short enough to fit in a PR description and precise enough that another engineer can challenge the tradeoffs.

text
Goal:
Who cares:
Decision owner:
User or system action changed by the model:
Success metric:
Guardrail metrics:
Mistake budget:
Unacceptable mistakes:
Acceptable mistakes:
Assumptions:
Constraints:
Labels and data snapshot:
Baseline:
Candidate signals:
Threshold or config plan:
Eval slices:
Known risks:
Next experiment:
Rollback or fallback:

This compact is the MLE equivalent of a strong SWE design note. It keeps the team from optimizing a metric no one trusts, adding features that do not address the real error mode, or shipping complexity without a rollback.

Decision Brain

Use this loop whenever the task is ambiguous, high-impact, or metric-heavy:

  1. Start from the decision, not the model. Name the action that changes downstream behavior.
  2. Name who cares and why. Different stakeholders pay different costs for false positives, false negatives, latency, compute spend, opacity, or missed opportunities.
  3. Convert ambiguity into hypotheses. Ask what signal would separate outcomes, what evidence would disprove it, and what simple baseline should be hard to beat.
  4. Research prior art or a nearby known problem before inventing a bespoke system.
  5. Score choices with (probability, confidence) x (cost, severity, importance, impact).
  6. Consider adversarial behavior, incentives, selective disclosure, distribution shift, and feedback loops.
  7. Prefer the simplest change that reduces the most important mistake. Simplicity is not laziness; it is a way to minimize blunders while preserving iteration speed.
  8. Capture the decision, evidence, counterargument, and next reversible step.

Metric and Mistake Economics

Choose metrics from failure costs, not habit:

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
184,669
Repository forks
28,535
Repository npm downloads, 7 days
1,807
7-day trend score
78

Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 17 May 2026, 6 months ago.

Extension points

  • hookPre/post lifecycle hooks

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/affaan-m/everything-claude-code/mle-workflow/badge)](https://verified-skill.com/skills/affaan-m/everything-claude-code/mle-workflow)

Something wrong with this skill or its page? Tell us.