leonardodalinky/scider/ml-model-evaluation
Claude Code and agent skill by leonardodalinky/scider
- community
Checking that the SKILL.md file is still in the repository.
Model evaluation framework — cross-validation strategies, metric selection by task type, baseline requirements, ablation design, and train/val/test discipline. Use for all ML experiments before reporting results.
Install
npx vskill@latest install leonardodalinky/scider/ml-model-evaluationSKILL.md
ML Model Evaluation
Overview
Rigorous model evaluation is the foundation of credible ML research. This skill covers the complete evaluation pipeline: how to split data correctly, which metrics to report for which tasks, what baselines are required, how to structure ablation studies, and how to verify that results are statistically meaningful. Apply this skill before writing any results section or claiming model performance.
When to Use This Skill
Use this skill when:
- Selecting cross-validation strategy for a new experiment
- Choosing which metrics to compute and report for a task
- Setting up baseline comparisons before training models
- Designing ablation studies to identify component contributions
- Assessing whether train/val/test splits are clean and leak-free
- Tuning hyperparameters with nested cross-validation
- Reporting confidence intervals and checking statistical significance
- Completing the results section of a paper or technical report
Hard Rules (follow for every experiment)
- NEVER report accuracy alone for imbalanced datasets — always pair with F1, AUC-PR, or MCC
- ALWAYS compare against at least one trivial baseline before claiming model performance
- ALWAYS use cross-validation (or a proper held-out test set) — never evaluate on training data
- ALWAYS report confidence intervals or standard deviation across folds
- For ablation studies: change ONE component at a time and report the delta
Cross-Validation Taxonomy
Choose the CV strategy based on your data structure. Wrong CV choice is one of the most common sources of inflated reported performance.
Standard K-Fold
Use when: data is IID, classes are balanced, no group structure.
Stratified K-Fold
Use when: classification task with class imbalance. Preserves class distribution in each fold.
Group K-Fold
Use when: samples are not independent — they come from groups (e.g., multiple measurements per patient, sentences from the same document). Leaking groups across folds gives optimistically biased estimates.
Time-Series Split
Use when: data has temporal ordering. Future data must never appear in training folds.
Expanding window (default TimeSeriesSplit) — training set grows with each fold:
Sliding window — fixed-size training window (manual):
Nested Cross-Validation (Hyperparameter Tuning + Evaluation)
Use nested CV when you tune hyperparameters AND want an unbiased generalization estimate. The outer loop estimates generalization; the inner loop selects hyperparameters.
Rule: never use the same CV split for both tuning and evaluation — this is a common source of optimistic bias.
Metric Selection Guide by Task Type
Classification
| Metric | When to Use | When NOT to Use | |
|---|---|---|---|
| Accuracy | Balanced classes only | Imbalanced datasets | |
| Balanced Accuracy | Imbalanced, multi-class | — | |
| Precision / Recall | When false positives or false negatives have asymmetric costs | Don't use alone | |
| F1 (macro) | Multi-class, treat all classes equally | When class sizes matter | |
| F1 (weighted) | Multi-class, weight by support | Obscures minority class performance | |
| AUC-ROC | Binary, probabilistic output | Severely imbalanced (prefer AUC-PR) | |
| AUC-PR | Imbalanced binary problems | Not useful for balanced data | |
| MCC | Best single metric for imbalanced binary | Less intuitive to report |
Regression
| Metric | Formula | When to Use | |||||
|---|---|---|---|---|---|---|---|
| RMSE | √(mean((ŷ-y)²)) | Default; penalizes large errors; interpretable in target units | |||||
| MAE | mean(\ | ŷ-y\ | ) | When outliers are expected and should not dominate | |||
| R² | 1 - SS_res/SS_tot | Explained variance; use as secondary metric | |||||
| MAPE | mean(\ | ŷ-y\ | /\ | y\ | )×100 | When relative error matters; AVOID when y≈0 | |
| Huber Loss | Hybrid MAE/MSE | Robust to outliers; use δ≈1.35×MAD |
Clustering
Distinguish external metrics (require true labels) from internal metrics (only use features):
Ranking / Retrieval
Generation / Seq2Seq
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryChecking.scider/skills/ml-model-evaluation/SKILL.md
Popularity
- Repository stars
- 88
- Repository forks
- 7
- 7-day trend score
- 22
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 28 Oct 2026, 11 days ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/leonardodalinky/scider/ml-model-evaluation)