Ai ml workflow

Skill toilact/godchi/skills/ai-ml-workflow

Use when starting or planning any machine-learning task — exploring a dataset, engineering features, training, tuning hyperparameters, evaluating, integrating a model into a service or device, or deploying. Gives the senior AI-engineer lifecycle and routes to the right guard and detailed phase doc.From its SKILL.md

Install

npx -y skills add toilact/godchi --skill ai-ml-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

AI/ML Workflow

Overview

The disciplined lifecycle toilact follows for ML work. This skill is the map: it names the phases, the order, and which guard/doc to pull for each. Detailed playbooks live in the on-demand library — load them with /gc-lib ml-lifecycle/<phase> only when you reach that phase (they are not auto-loaded).

When to Use

Any ML/data task: EDA, feature engineering, preprocessing, training, hyperparameter tuning, evaluation, the iterate loop, on-device/service integration, deployment. Works for any ML project — tabular, time-series / forecasting, or NLP (e.g. a daily prediction pipeline, a fine-tuned transformer).

The lifecycle (follow in order; don't skip ahead)

EDA → /gc-lib ml-lifecycle/eda — understand distributions, missingness, leakage risk, target balance.
Feature engineering → /gc-lib ml-lifecycle/feature-engineering — MUST honor ml-data-leakage-guard.
Preprocessing → /gc-lib ml-lifecycle/preprocess — fit transforms on the train fold only.
Training → /gc-lib ml-lifecycle/training — reproducible runs, seeds, logged metrics.
Tuning → /gc-lib ml-lifecycle/tuning — search with an inner split; MUST honor walk-forward-guard.
Evaluate + loop → /gc-lib ml-lifecycle/loop — out-of-sample only; decide iterate vs ship.
Integrate → /gc-lib ml-lifecycle/integrate — share ONE feature builder train↔serve; MUST honor model-feature-versioning.
Deploy → /gc-lib ml-lifecycle/deploy — version, monitor, roll back safely.

Non-negotiable guards (auto-active skills)

ml-data-leakage-guard — feature(T) uses only data known at T.
walk-forward-guard — train-on-past / test-on-future, no shuffle.
model-feature-versioning — frozen feature contract, no train/serve skew.

Behaviour

Follow the godchi gate: brainstorm the approach, write a short plan, confirm with the user before changing a chosen modelling decision, review results before declaring success. Reply in Vietnamese.