CtrlK
BlogDocsLog inGet started
Tessl Logo

ml-model-training

Train ML models with scikit-learn, PyTorch, TensorFlow. Use for classification/regression, neural networks, hyperparameter tuning, or encountering overfitting, underfitting, convergence issues.

60

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/ml-model-training/skills/ml-model-training/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a solid, code-dense overview with genuine progressive disclosure to two real reference files, and the 'Known Issues Prevention' patterns are concrete and executable. Its main weaknesses are token inefficiency from redundant sections and restated concepts Claude already knows, and a workflow that is listed but lacks explicit validation checkpoints or error-recovery guidance.

Suggestions

Collapse 'Complete Framework Examples' and 'When to Load References' into a single reference section, and remove the duplicated fit-on-train/transform code from either 'Data Preparation' or 'Known Issues Prevention' #1.

Turn the one-line arrow workflow into a short ordered list with an explicit checkpoint after each stage (e.g. 'evaluate on validation set; if overfitting, add regularization before proceeding'), and drop the listed 'Feature Engineering' step or add a section for it.

Delete the Evaluation Metrics table (Accuracy/Precision/Recall/F1, MSE/RMSE/MAE are already known) and move the full inline PyTorch training loop into references/pytorch-training.md, keeping only a minimal sketch in the body.

DimensionReasoningScore

Conciseness

The body is mostly efficient, with concrete code dominating, but includes material Claude already knows (the Accuracy/Precision/Recall/F1 metrics table, boilerplate PyTorch training loops) and notable redundancy: the data-leakage scaling snippet appears in both "Data Preparation" and "Known Issues Prevention", and "Complete Framework Examples" and "When to Load References" repeat the same reference pointers. This matches the 'mostly efficient but could be tightened' anchor rather than level 4, where only minor trims would be needed.

3 / 5

Actionability

Guidance is mostly executable: complete scikit-learn and PyTorch snippets, concrete class-weight/SMOTE and seed-setting code, and copy-ready GridSearchCV usage. It falls short of level 5 only through small gaps — the PyTorch loop references `X_train_tensor`/`y_train_tensor` without defining them, and the class-imbalance snippet uses `np` without importing numpy.

4 / 5

Workflow Clarity

The sequence "1. Data Preparation → 2. Feature Engineering → 3. Model Selection → 4. Training → 5. Evaluation" is present and the sections roughly follow it, but it is a one-line arrow chain with no checkpoints: there is no explicit validate-after-each-step guidance, no error-recovery loop, and no Feature Engineering section despite it being listed. This matches the 'steps listed but validation gaps' anchor; level 4 would require most checkpoints to be explicit.

3 / 5

Progressive Disclosure

The SKILL.md body stays at overview level and points to two real, one-level-deep, well-signaled reference files (references/pytorch-training.md and references/tensorflow-keras.md), each summarized by content bullets. It is not level 5 because the reference pointers are duplicated across two sections ("Complete Framework Examples" and "When to Load References") and a full inline PyTorch training loop duplicates content that belongs in the reference file.

4 / 5

Total

14

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it pairs a concrete 'what' (training ML models with three named frameworks) with an explicit 'Use for...' clause containing natural, varied trigger terms covering tasks and failure modes. Its only real weakness is that the capability side is compressed to a single generic verb, and its breadth leaves some overlap risk with adjacent ML-lifecycle skills.

DimensionReasoningScore

Specificity

"Train ML models with scikit-learn, PyTorch, TensorFlow" names the domain and frameworks but offers only one generic action ("Train"), matching the anchor for naming the domain with 1-2 concrete actions rather than the level-4 anchor requiring several specific actions like tuning, evaluating, or regularizing.

3 / 5

Completeness

It explicitly answers both parts: "Train ML models with scikit-learn, PyTorch, TensorFlow" (what) and "Use for classification/regression, neural networks, hyperparameter tuning, or encountering overfitting, underfitting, convergence issues" (when, with concrete trigger phrases). The level-4 anchor's failure mode (a 'when' that could be more explicit) does not apply, so this is a clear match for level 5.

5 / 5

Trigger Term Quality

Phrases like "classification/regression, neural networks, hyperparameter tuning, or encountering overfitting, underfitting, convergence issues" are natural terms users would say, giving good keyword coverage. It is not level 5 because common variations such as "deep learning", "fine-tuning", "cross-validation", or "model evaluation" are absent.

4 / 5

Distinctiveness Conflict Risk

Naming three specific frameworks carves out a mostly distinct ML-training niche with trigger terms unlikely to fire for unrelated skills. It is not level 5 because broad scope (all of ML model work) creates minor overlap risk with adjacent skills like data preprocessing, feature engineering, or model evaluation.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
secondsky/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.