ai-ml-data-science

Build production-ready ML workflows with EDA, feature engineering, and SQLMesh transformations.

73|16|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/vasilyu1983/AI-Agents-public --skill ai-ml-data-science
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-ml-data-science
Source: https://github.com/vasilyu1983/AI-Agents-public/tree/main/frameworks/claude-code-kit/initial-setup/skills/ai-ml-data-science
Command: npx skills add https://github.com/vasilyu1983/AI-Agents-public --skill ai-ml-data-science

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Data science projects often get stuck between experimentation and production, lacking structured workflows for data transformation, feature engineering, and robust model evaluation. This Skill provides end-to-end data science patterns for production-ready ML.

Core Features & Use Cases

  • End-to-End ML Workflow: Covers problem framing, structured EDA, feature engineering (with feature stores), model selection (LightGBM-first), and comprehensive evaluation with slice analysis and model cards.
  • SQL Transformation with SQLMesh: Build staging, intermediate, and marts layers using SQLMesh for robust, version-controlled data transformations and incremental models.
  • MLOps Integration: Set up CI/CD, continuous training (CT), and continuous monitoring (CM) with automated drift detection to ensure train-serve parity and model reliability in production.

Quick Start

Use the ai-ml-data-science skill to outline an EDA workflow for a new tabular dataset, including steps for data profiling and quality checks.

Frequently Asked Questions about ai-ml-data-science

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an end-to-end machine learning pipeline from raw data to production?

End-to-end ML pipelines combine structured EDA with drift detection, feature engineering using feature stores, LightGBM model training, and comprehensive evaluation with slice analysis. This workflow handles data transformation via SQLMesh, CI/CD automation, continuous training, and monitoring to ensure reproducibility and train-serve parity in production.

What's the best way to engineer features and detect data drift in production models?

Feature engineering with feature stores creates reusable, versioned transformations tracked through data lineage. Drift detection monitors train-serve parity by comparing data distributions and model performance over time, triggering retraining when degradation occurs and maintaining data contracts across environments.

How do I set up MLOps with continuous training and monitoring for my data science project?

MLOps integration automates CI/CD pipelines, continuous training schedules, and continuous monitoring dashboards. SQLMesh handles versioned SQL transformations with incremental models, while automated drift detection and model cards provide documentation and governance required for production-grade data science workflows.

Can I use LightGBM with SQLMesh for model development and data transformation?

LightGBM handles model selection and training within the workflow, while SQLMesh manages SQL-based data transformations across staging, intermediate, and mart layers. Both integrate into reproducible pipelines with version control, enabling validated model development paired with robust data engineering.

What's included in a production-ready model evaluation beyond accuracy metrics?

Production-ready evaluation includes slice analysis across data subgroups, model cards documenting assumptions and limitations, and comprehensive reporting of performance, bias, and drift. This ensures transparency, reproducibility, and compliance with data contracts required for continuous monitoring and governance.

Why is data lineage and documentation important for data science projects?

Data lineage traces transformations from raw data through features to model predictions, enabling reproducibility, debugging, and compliance audits. Combined with model cards and automated documentation, it satisfies governance requirements and supports continuous training by clarifying dependencies and data contracts.