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
- santiago-migoni/claude-skillsedited, first seen Nov 8, 2026
- lsyamsiar/claude-skillsedited, first seen Nov 1, 2026
- codeApe-7/ai-agent-workflowGroupedited, first seen Nov 1, 2026
- hu465/claude-skills-edited, first seen Oct 25, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- labdaps/labskillstheir own version, first seen Sep 26, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 8
- Jeffallan/claude-skills★ 12k25% same
- codeApe-7/ai-agent-workflowGroup★ 1826% same
- PIXARTSeu/Synapse★ 926% same
- hu465/claude-skills-★ 025% same
- james-paul25/claude-skill★ 026% same
- lsyamsiar/claude-skills★ 025% same
- santiago-migoni/claude-skills★ 025% same
- usmanmubarak1/ClaudeSkilledAgents★ 092% same
Wrote their own version · 4
- nimadorostkar/Claude-Skills-collection★ 33same name
- HyperFrequency/skills★ 15same name
- alex-voloshin-dev/ai-skills★ 2same name
- labdaps/labskills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- angular-architectSkill
- api-designerSkill
- architecture-designerSkill
- atlassian-mcpSkill
- chaos-engineerSkill
- cli-developerSkill
- cloud-architectSkill
- code-documenterSkill
- code-reviewerSkill
- cpp-proSkill
- csharp-developerSkill
- database-optimizerSkill
- debugging-wizardSkill
- devops-engineerSkill
- django-expertSkill
- dotnet-core-expertSkill
- embedded-systemsSkill
- fastapi-expertSkill
- feature-forgeSkill
- fine-tuning-expertSkill
- flutter-expertSkill
- fullstack-guardianSkill
- game-developerSkill
- golang-proSkill
- graphql-architectSkill
- java-architectSkill
- javascript-proSkill
- kotlin-specialistSkill
- kubernetes-specialistSkill
- laravel-specialistSkill
- legacy-modernizerSkill
- mcp-developerSkill
- microservices-architectSkill
- monitoring-expertSkill
- nestjs-expertSkill
- nextjs-developerSkill
- pandas-proSkill
- php-proSkill
- playwright-expertSkill
- postgres-proSkill
- prompt-engineerSkill
- python-proSkill
- rag-architectSkill
- rails-expertSkill
- react-expertSkill
- react-native-expertSkill
- rust-engineerSkill
- salesforce-developerSkill
- secure-code-guardianSkill
- security-reviewerSkill
- shopify-expertSkill
- spark-engineerSkill
- spec-minerSkill
- spring-boot-engineerSkill
- sql-proSkill
- sre-engineerSkill
- swift-expertSkill
- terraform-engineerSkill
- test-masterSkill
- The first 60 shown.
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
- Distinctive: line 63
Use containerized environments for training jobs
- Distinctive: line 67
Document pipeline dependencies and data lineage
- Common: line 71
Run training without experiment tracking
- Distinctive: line 75
Use non-reproducible random states
- Distinctive: line 84
When implementing ML pipelines, provide:
“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.
Files
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
- Design pipeline architecture - Map data flow, identify stages, define interfaces between components
- Implement feature engineering - Build transformation pipelines, feature stores, validation checks
- Orchestrate training - Configure distributed training, hyperparameter tuning, resource allocation
- Track experiments - Log metrics, parameters, artifacts; enable comparison and reproducibility
- Validate and deploy - Implement model validation, A/B testing, automated deployment workflows
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
| Feature Engineering | references/feature-engineering.md | Feature pipelines, transformations, feature stores, Feast, data validation |
| Training Pipelines | references/training-pipelines.md | Training orchestration, distributed training, hyperparameter tuning, resource management |
| Experiment Tracking | references/experiment-tracking.md | MLflow, Weights & Biases, experiment logging, model registry |
| Pipeline Orchestration | references/pipeline-orchestration.md | Kubeflow Pipelines, Airflow, Prefect, DAG design, workflow automation |
| Model Validation | references/model-validation.md | Evaluation 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:
- Complete pipeline definition (Kubeflow/Airflow DAG or equivalent)
- Feature engineering code with data validation
- Training script with experiment logging
- Model evaluation and validation code
- Deployment configuration
- 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
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
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.

