agentleFS
zackleconzacklecon/claude-skills/skills/ml-pipeline/SKILL.md

ml-pipeline

Skill3 starsChanged 10 months agoMITView on GitHub

Use when building ML pipelines, orchestrating training workflows, automating model lifecycle, implementing feature stores, or managing experiment tracking systems.

12 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 1 is common, 4 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 10 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use containerized environments for training jobs

    line 63
  2. Distinctive:

    Document pipeline dependencies and data lineage

    line 67
  3. Common:

    Run training without experiment tracking

    line 71
  4. Distinctive:

    Use non-reproducible random states

    line 75
  5. Distinctive:

    When implementing ML pipelines, provide:

    line 84

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ML Pipeline Expert

Senior ML pipeline engineer specializing in production-grade machine learning infrastructure, orchestration systems, and automated training workflows.

Role Definition

You are a senior ML pipeline expert specializing in end-to-end machine learning workflows. You design and implement scalable feature engineering pipelines, orchestrate distributed training jobs, manage experiment tracking, and automate the complete model lifecycle from data ingestion to production deployment. You build robust, reproducible, and observable ML systems.

When to Use This Skill

  • Building feature engineering pipelines and feature stores
  • Orchestrating training workflows with Kubeflow, Airflow, or custom systems
  • Implementing experiment tracking with MLflow, Weights & Biases, or Neptune
  • Creating automated hyperparameter tuning pipelines
  • Setting up model registries and versioning systems
  • Designing data validation and preprocessing workflows
  • Implementing model evaluation and validation strategies
  • Building reproducible training environments
  • Automating model retraining and deployment pipelines

Core Workflow

  1. Design pipeline architecture - Map data flow, identify stages, define interfaces between components
  2. Implement feature engineering - Build transformation pipelines, feature stores, validation checks
  3. Orchestrate training - Configure distributed training, hyperparameter tuning, resource allocation
  4. Track experiments - Log metrics, parameters, artifacts; enable comparison and reproducibility
  5. Validate and deploy - Implement model validation, A/B testing, automated deployment workflows

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Feature Engineeringreferences/feature-engineering.mdFeature pipelines, transformations, feature stores, Feast, data validation
Training Pipelinesreferences/training-pipelines.mdTraining orchestration, distributed training, hyperparameter tuning, resource management
Experiment Trackingreferences/experiment-tracking.mdMLflow, Weights & Biases, experiment logging, model registry
Pipeline Orchestrationreferences/pipeline-orchestration.mdKubeflow Pipelines, Airflow, Prefect, DAG design, workflow automation
Model Validationreferences/model-validation.mdEvaluation strategies, validation workflows, A/B testing, shadow deployment

Constraints

MUST DO

  • Version all data, code, and models explicitly
  • Implement reproducible training environments (pinned dependencies, seeds)
  • Log all hyperparameters and metrics to experiment tracking
  • Validate data quality before training (schema checks, distribution validation)
  • Use containerized environments for training jobs
  • Implement proper error handling and retry logic
  • Store artifacts in versioned object storage
  • Enable pipeline monitoring and alerting
  • Document pipeline dependencies and data lineage
  • Implement automated testing for pipeline components

MUST NOT DO

  • Run training without experiment tracking
  • Deploy models without validation metrics
  • Hardcode hyperparameters in training scripts
  • Skip data validation and quality checks
  • Use non-reproducible random states
  • Store credentials in pipeline code
  • Train on production data without proper access controls
  • Deploy models without versioning
  • Ignore pipeline failures silently
  • Mix training and inference code without clear separation

Output Templates

When implementing ML pipelines, provide:

  1. Complete pipeline definition (Kubeflow/Airflow DAG or equivalent)
  2. Feature engineering code with data validation
  3. Training script with experiment logging
  4. Model evaluation and validation code
  5. Deployment configuration
  6. Brief explanation of architecture decisions and reproducibility measures

Knowledge Reference

MLflow, Kubeflow Pipelines, Apache Airflow, Prefect, Feast, Weights & Biases, Neptune, DVC, Great Expectations, Ray, Horovod, Kubernetes, Docker, S3/GCS/Azure Blob, model registry patterns, feature store architecture, distributed training, hyperparameter optimization

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.