Back to catalog
Human reviewedData & analysis

Skill dossier

ml-pipeline

Source declaration

Designs and implements production-grade ML pipeline infrastructure: configures experiment tracking with MLflow or Weights & Biases, creates Kubeflow or Airflow DAGs for training orchestration, builds feature store schemas with Feast, deploys model registries, and automates retraining and validation workflows. Use when building ML pipelines, orchestrating training workflows, automating model lifecycle, implementing feature stores, managing experiment tracking systems, setting up DVC for data versioning, tuning hyperparameters, or configuring MLOps tooling like Kubeflow, Airflow, MLflow, or Prefect.

The author's original description, preserved in English. It describes intent, not verified performance.

Designs and implements production-grade ML pipeline infrastructure: configures experiment tracking with MLflow or Weights & Biases, creates Kubeflow or Airflow DAGs for training orchestration, builds feature store schemas with Feast, deploys model registries, and automates retraining and validation workflows. Use when building ML pipelines, orchestrating training workflows, automating model lifecycle, implementing feature stores, managing experiment tracking systems, setting up DVC for data versioning, tuning hyperparameters, or configuring MLOps tooling like Kubeflow, Airflow, MLflow, or Prefect.

datareferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A Skill for building production ML pipelines with experiment tracking, orchestration, feature stores and evaluation gates before deployment.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Validates data schema and distributions before training and halts on failure.
  • Logs parameters, metrics and artifacts with MLflow or equivalent.
  • Defines Kubeflow or Airflow pipelines for training orchestration.
  • Applies evaluation gates and A/B or shadow deployment before promotion.

Limitations & scope

  • Requires existing MLOps infrastructure such as Kubeflow, Airflow or MLflow.
  • Templates use library APIs that may differ across versions and are not verified here.
  • Evaluation thresholds are left for the user to define.

Relevant for

  • ML engineers building training pipelines
  • MLOps teams standardizing tracking
  • Data scientists moving models to production

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
120.7 KB
Structural complexity
Moderate

File inventory

PathTypeBytes
skills/ml-pipeline/references/experiment-tracking.mdReference21.4 KB
skills/ml-pipeline/references/feature-engineering.mdReference17.4 KB
skills/ml-pipeline/references/model-validation.mdReference29.8 KB
skills/ml-pipeline/references/pipeline-orchestration.mdReference23 KB
skills/ml-pipeline/references/training-pipelines.mdReference22 KB
skills/ml-pipeline/SKILL.mdInstruction7.2 KB

SKILL.md frontmatter

{
  "name": "ml-pipeline",
  "description": "Designs and implements production-grade ML pipeline infrastructure: configures experiment tracking with MLflow or Weights & Biases, creates Kubeflow or Airflow DAGs for training orchestration, builds feature store schemas with Feast, deploys model registries, and automates retraining and validation workflows. Use when building ML pipelines, orchestrating training workflows, automating model lifecycle, implementing feature stores, managing experiment tracking systems, setting up DVC for data versioning, tuning hyperparameters, or configuring MLOps tooling like Kubeflow, Airflow, MLflow, or Prefect.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "data-ml",
    "triggers": "ML pipeline, MLflow, Kubeflow, feature engineering, model training, experiment tracking, feature store, hyperparameter tuning, pipeline orchestration, model registry, training workflow, MLOps, model deployment, data pipeline, model versioning",
    "role": "expert",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "devops-engineer, kubernetes-specialist, cloud-architect, python-pro"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Design pipeline architecture

    Map data flow, identify stages and define interfaces between components.

  2. 02
    Action

    Validate data schema

    Run schema and distribution checks before training begins.

  3. 03
    Decision

    Halt on failure

    Stop and report when validation fails rather than proceeding to training.

  4. 04
    Output

    Deliver pipeline and gates

    Provide pipeline definition, feature code, tracked training script, evaluation thresholds and deployment config.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

164 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

8 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

154 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 154 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Dynamic command execution is referenced

2 occurrences

A shell, dynamic evaluation, or process execution primitive appears here. Inspect arguments and input control. Presence in source does not prove a command ran. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Check where credentials, data paths and pickled model artifacts are stored and loaded before running generated pipeline code.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/ml-pipeline # .claude/skills/ml-pipeline
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/ml-pipeline/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to add MLflow tracking to a training script and confirm it logs hyperparameters and metrics and validates data first.

Prerequisites

  • Requires existing MLOps infrastructure such as Kubeflow, Airflow or MLflow.
  • Templates use library APIs that may differ across versions and are not verified here.
  • Evaluation thresholds are left for the user to define.

Example prompts

Representative task

Using the ml-pipeline skill, build a Kubeflow training pipeline for a classifier with data validation, MLflow tracking, an evaluation gate with explicit thresholds, and a rollback strategy.

Inspect before use

Read the ml-pipeline skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/ml-pipeline/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Makes data validation and tracking mandatory.
  • Requires recorded validation metrics before deployment.

Considerations

  • Pipeline tooling choices carry significant infrastructure cost.
  • Pickle-based model saving in the template should be reviewed for trust boundaries.
Research conclusion

A reproducibility-focused guide for teams that already run or plan to run MLOps tooling.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/ml-pipeline
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.