Back to Workflow & Productivity

ml-pipeline-workflow

MLOpsMachine LearningData PipelineWorkflow AutomationModel DeploymentAI AgentDevOpsExperiment Tracking
36.8k📄 MIT🕒 2026-06-16Source ↗

Install this skill

npx skills add wshobson/agents

Works across Claude Code, Cursor, Codex, Copilot & Antigravity

The ml-pipeline-workflow skill provides a standardized framework for automating machine learning lifecycles. It connects distinct phases—from raw data ingestion to production deployment—ensuring that every stage remains reproducible and verifiable. By focusing on DAG-based orchestration, it replaces manual scripts with structured workflows that enforce quality checks, version control, and consistent metric tracking. Users gain a modular structure to manage feature engineering, experiment logging, and model serving requirements. The skill helps translate research prototypes into stable, automated systems that withstand production loads. Instead of fragmented ad-hoc tasks, this approach builds a reliable sequence of operations that monitors drift, manages model versions, and handles deployment rollbacks automatically, maintaining system integrity across multiple iterations of model training and inference.

When to Use This Skill

  • Migrating local ML training notebooks into production-ready pipelines
  • Setting up automated triggers to retrain models when data drift is detected
  • Standardizing CI/CD for machine learning systems across a team
  • Managing complex cross-cloud deployments with custom rollback logic

How to Invoke This Skill

Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:

  • Set up a production ML pipeline
  • How do I automate my model training workflow?
  • Create a DAG for my data engineering and training steps
  • Best practices for MLOps pipeline orchestration
  • Configure a deployment strategy for new model versions

Pro Tips

  • 💡Always start with clear data contracts and validation steps to ensure data quality throughout your pipeline.
  • 💡Leverage experiment tracking tools (e.g., MLflow, Weights & Biases) early on to manage hyperparameters and model versions effectively.
  • 💡Design your pipeline components to be modular and loosely coupled for easier maintenance and reusability across projects.

What this skill does

  • Orchestrates multi-stage DAG workflows for ML tasks
  • Automates data validation and feature engineering pipelines
  • Integrates model registries for experiment tracking and versioning
  • Implements controlled deployment strategies like canary or blue-green releases
  • Enforces standardized metrics for pre-deployment validation

When not to use it

  • For simple, one-off model prototyping where orchestration overhead outweighs benefits
  • In environments lacking sufficient infrastructure for automated artifact storage
  • When model inference needs to be strictly real-time without batch processing requirements

Example workflow

  1. Define the ingestion and validation stages for raw data
  2. Script the feature engineering logic with version tracking
  3. Configure training jobs with integrated experiment logging
  4. Run automated validation tests against performance benchmarks
  5. Execute deployment to a serving environment via a canary release

Prerequisites

  • Basic understanding of ML modeling concepts
  • Access to an orchestration tool like Airflow or Dagster
  • Storage for model and data artifacts

Pitfalls & limitations

  • !Over-engineering simple models that do not require full orchestration
  • !Tight coupling between pipeline components causing brittle workflows
  • !Neglecting to implement proper data lineage tracking, leading to audit failures

FAQ

Which orchestration tools are best supported?
The workflow is designed to be tool-agnostic but provides templates optimized for Airflow, Dagster, and Kubeflow.
How does this handle experiment tracking?
It suggests integrating tools like MLflow or Weights & Biases directly into the training phase of the workflow to log metrics.
Can I use this for non-Python based pipelines?
The logic remains applicable, though the current templates and examples primarily utilize Python-based libraries and SDKs.

How it compares

Unlike manual scripts that require human intervention at each step, this skill provides a structured template that ensures consistency, auditability, and automated error handling across the entire lifecycle.

Source & trust

37k stars📄 MIT🕒 Updated 2026-06-16
📄 Full skill instructions — original source: wshobson/agents
# ML Pipeline Workflow

Complete end-to-end MLOps pipeline orchestration from data preparation through model deployment.

## Overview

This skill provides comprehensive guidance for building production ML pipelines that handle the full lifecycle: data ingestion → preparation → training → validation → deployment → monitoring.

## When to Use This Skill

- Building new ML pipelines from scratch
- Designing workflow orchestration for ML systems
- Implementing data → model → deployment automation
- Setting up reproducible training workflows
- Creating DAG-based ML orchestration
- Integrating ML components into production systems

## What This Skill Provides

### Core Capabilities

1. **Pipeline Architecture**
- End-to-end workflow design
- DAG orchestration patterns (Airflow, Dagster, Kubeflow)
- Component dependencies and data flow
- Error handling and retry strategies

2. **Data Preparation**
- Data validation and quality checks
- Feature engineering pipelines
- Data versioning and lineage
- Train/validation/test splitting strategies

3. **Model Training**
- Training job orchestration
- Hyperparameter management
- Experiment tracking integration
- Distributed training patterns

4. **Model Validation**
- Validation frameworks and metrics
- A/B testing infrastructure
- Performance regression detection
- Model comparison workflows

5. **Deployment Automation**
- Model serving patterns
- Canary deployments
- Blue-green deployment strategies
- Rollback mechanisms

### Reference Documentation

See the references/ directory for detailed guides:

- **data-preparation.md** - Data cleaning, validation, and feature engineering
- **model-training.md** - Training workflows and best practices
- **model-validation.md** - Validation strategies and metrics
- **model-deployment.md** - Deployment patterns and serving architectures

### Assets and Templates

The assets/ directory contains:

- **pipeline-dag.yaml.template** - DAG template for workflow orchestration
- **training-config.yaml** - Training configuration template
- **validation-checklist.md** - Pre-deployment validation checklist

## Usage Patterns

### Basic Pipeline Setup

# 1. Define pipeline stages
stages = [
"data_ingestion",
"data_validation",
"feature_engineering",
"model_training",
"model_validation",
"model_deployment"
]

# 2. Configure dependencies
# See assets/pipeline-dag.yaml.template for full example


### Production Workflow

1. **Data Preparation Phase**
- Ingest raw data from sources
- Run data quality checks
- Apply feature transformations
- Version processed datasets

2. **Training Phase**
- Load versioned training data
- Execute training jobs
- Track experiments and metrics
- Save trained models

3. **Validation Phase**
- Run validation test suite
- Compare against baseline
- Generate performance reports
- Approve for deployment

4. **Deployment Phase**
- Package model artifacts
- Deploy to serving infrastructure
- Configure monitoring
- Validate production traffic

## Best Practices

### Pipeline Design

- **Modularity**: Each stage should be independently testable
- **Idempotency**: Re-running stages should be safe
- **Observability**: Log metrics at every stage
- **Versioning**: Track data, code, and model versions
- **Failure Handling**: Implement retry logic and alerting

### Data Management

- Use data validation libraries (Great Expectations, TFX)
- Version datasets with DVC or similar tools
- Document feature engineering transformations
- Maintain data lineage tracking

### Model Operations

- Separate training and serving infrastructure
- Use model registries (MLflow, Weights & Biases)
- Implement gradual rollouts for new models
- Monitor model performance drift
- Maintain rollback capabilities

### Deployment Strategies

- Start with shadow deployments
- Use canary releases for validation
- Implement A/B testing infrastructure
- Set up automated rollback triggers
- Monitor latency and throughput

## Integration Points

### Orchestration Tools

- **Apache Airflow**: DAG-based workflow orchestration
- **Dagster**: Asset-based pipeline orchestration
- **Kubeflow Pipelines**: Kubernetes-native ML workflows
- **Prefect**: Modern dataflow automation

### Experiment Tracking

- MLflow for experiment tracking and model registry
- Weights & Biases for visualization and collaboration
- TensorBoard for training metrics

### Deployment Platforms

- AWS SageMaker for managed ML infrastructure
- Google Vertex AI for GCP deployments
- Azure ML for Azure cloud
- Kubernetes + KServe for cloud-agnostic serving

## Progressive Disclosure

Start with the basics and gradually add complexity:

1. **Level 1**: Simple linear pipeline (data → train → deploy)
2. **Level 2**: Add validation and monitoring stages
3. **Level 3**: Implement hyperparameter tuning
4. **Level 4**: Add A/B testing and gradual rollouts
5. **Level 5**: Multi-model pipelines with ensemble strategies

## Common Patterns

### Batch Training Pipeline

# See assets/pipeline-dag.yaml.template
stages:
- name: data_preparation
dependencies: []
- name: model_training
dependencies: [data_preparation]
- name: model_evaluation
dependencies: [model_training]
- name: model_deployment
dependencies: [model_evaluation]


### Real-time Feature Pipeline

# Stream processing for real-time features
# Combined with batch training
# See references/data-preparation.md


### Continuous Training

# Automated retraining on schedule
# Triggered by data drift detection
# See references/model-training.md


## Troubleshooting

### Common Issues

- **Pipeline failures**: Check dependencies and data availability
- **Training instability**: Review hyperparameters and data quality
- **Deployment issues**: Validate model artifacts and serving config
- **Performance degradation**: Monitor data drift and model metrics

### Debugging Steps

1. Check pipeline logs for each stage
2. Validate input/output data at boundaries
3. Test components in isolation
4. Review experiment tracking metrics
5. Inspect model artifacts and metadata

## Next Steps

After setting up your pipeline:

1. Explore **hyperparameter-tuning** skill for optimization
2. Learn **experiment-tracking-setup** for MLflow/W&B
3. Review **model-deployment-patterns** for serving strategies
4. Implement monitoring with observability tools

## Related Skills

- **experiment-tracking-setup**: MLflow and Weights & Biases integration
- **hyperparameter-tuning**: Automated hyperparameter optimization
- **model-deployment-patterns**: Advanced deployment strategies

How to Use This Skill Unit

Option A: Project-Specific (Recommended)

  1. Click "Download" above
  2. In your project, create the directory: .agent/skills/ml-pipeline-workflow/
  3. Save the file as SKILL.md
  4. The agent will automatically discover the skill based on its description.

Option B: Global Installation (All Agents)

Save the file to these locations to make it available across all projects:

  • Claude Code: ~/.claude/skills/wshobson/agents/ml-pipeline-workflow/SKILL.md
  • Cursor: ~/.cursor/skills/wshobson/agents/ml-pipeline-workflow/SKILL.md
  • Antigravity: ~/.gemini/antigravity/skills/wshobson/agents/ml-pipeline-workflow/SKILL.md

🚀 Install with CLI:
npx skills add wshobson/agents

Read the Master Guide: Mastering Agent Skills

Recommended Rules

View more rules

Recommended Workflows

View more workflows

Recommended MCP Servers

View more MCP servers

Take It Further

Maximize your productivity with these powerful resources

📋

Define Your Standards

Set up coding standards to ensure this workflow produces consistent, high-quality results.

Browse Rules Library
📖

Master Workflows

Learn how to create custom workflows, use Turbo Mode, and build your automation library.

Complete Guide

How to use this Skill in Claude Code & Cursor

For Claude Code (CLI)

To use this skill in Claude Code, copy the rule content into your project's custom instructions or follow our Add-Skill CLI guide. This ensures Claude follows your standards during every code generation.

For Cursor & Windsurf

For Cursor or Windsurf, individual skills are best used in the "Rules for AI" section. This specific unit helps the agent avoid workflow & productivity issues, leading to cleaner, more efficient code.

Why the skill format matters: the standardized Agent Skills format lets your AI agent load detailed instructions only when they are relevant, keeping your prompt clean while improving results.

Source & attribution

This skill is categorized under Workflow & Productivity and is published by W. Shobson, maintained in wshobson/agents.

← Browse All Agent Skills
Sponsored AI assistant. Recommendations may be paid.