Agent skill · Code Review & Quality

LQF_Machine_Learning_Expert_Guide

LQF Machine Learning Expert Guide - Auto-activating skill for ML/Statistical Modeling with Critical Discussion Mode. Triggers on: machine learning, modeling, prediction, training, classification, regression, clustering, deep learning, neural network, model evaluation, feature engineering, hyperparameter tuning, overfitting, underfitting, baseline, ablation study, critique my approach, review my model, is this a good idea, should I use, what's wrong with, evaluate my solution, challenge my assumptions, discuss my approach Engages in critical discussion with minimum 3 rounds of iterative refinem

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill lqf-machine-learning-expert-guide --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 30 KB
Bundled scripts: none
Version: 2.0.0
Allowed tools: ReadWriteEditBashGrepGlob
Path: skills/ai-ml/lqf-machine-learning-expert-guide/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

The skill engages in critical discussion mode for ML projects, requiring at least three refinement rounds. It prompts the agent to demand a dummy baseline, data size, target distribution, and data collection details before proceeding. It enforces explicit baselines, simple vs. complex model comparisons, and ablation checks. It uses a tiered critique approach (diplomatic, Socratic, direct) and mandates evidence-based reasoning with baseline lifts and potential data leakage checks. It prescribes stepwise progression from problem framing to data engineering and modeling, prioritizing simpler, interpretable baselines and only increasing complexity when justified by measurable improvement. It imposes mandatory information checks for high-risk decisions and includes a self-critique framework to assess complexity, baselines, assumptions, and evidence. It also provides structured critique templates and examples to challenge proposals and ensure robust evaluation. The skill signals that it operates within a critical engagement protocol and requires minimum three iteration cycles, evidence-based critique, and validation against baselines before acceptance. Commands, file names, and tool names are quoted exactly as described, and all steps are described concretely only if explicitly stated in the skill.

How it works

The skill defines a multi-round critique protocol: Round 1 proposes an approach and identifies 3–5 potential issues, asks clarifying questions, and suggests simpler alternatives. Round 2 critiques the refined approach, requests evidence (baseline, data distribution), and proposes counter-examples. Round 3 stresses edge cases, compares against alternatives, and delivers a final critique before acceptance. During critiques, it enforces mandatory information checks for high-risk decisions, including data size (n_samples, n_features), dummy baseline performance, target distribution, data collection details, train/test split strategy, and business metrics. It also provides a self-critique checklist covering complexity, baseline justification, assumptions, and evidence, plus a devil’s advocate section that immediately provides counter-arguments to each suggestion. The pattern includes a Simplicity Ladder of alternatives (No ML, Dummy Baseline, Simple Linear, Simple Non-Linear, Complex) and a Phase-based workflow: Problem Definition, Baseline Thinking, Data Engineering, Modeling, and Ablation. It concludes with a summary to ensure the approach has baseline justification and 3 refinement rounds.

When to use it

Use this skill to drive critical evaluation of ML/modeling proposals, especially when high-stakes decisions or complex modeling are involved. It should be applied when there is a need to establish baselines, test for data leakage, verify the necessity of complexity, and require evidence of lift over baselines before adopting advanced models. It is geared toward tasks involving ML classification, regression, clustering, feature engineering, hyperparameter tuning, and model validation, with a focus on transparent justification and rigorous critique.

What it can touch

Not applicable beyond the described workflow. The skill references using baselines, comparing models, and requesting information; no external touchpoints or explicit tool invocations are listed in the provided content beyond the general critique framework.

Caveats

The description emphasizes iterative critique and evidence-based decisions but does not guarantee model performance, baselines, or data quality. It requires explicit input from the user (data characteristics, baselines, split strategy) and enforces critique cycles before any acceptance. License, dependencies, and implementation specifics are not stated beyond the critique protocol.

From the SKILL.md

# LQF Machine Learning Expert Guide ## When to Use This Skill Use this skill when: - Building ML models (classification, regression, clustering, forecasting) - Evaluating model performance and debugging issues - Feature engineering and data preprocessing for ML - Hyperparameter tuning and model optimization - Debugging overfitting, underfitting, or poor generalization - Choosing between traditional ML and deep learning approaches - Establishing baselines and conducting ablation studies - Performing error analysis and model validation - Statistical modeling with predictive components ## Not For / Boundaries **Out of Scope:** - Pure data visualization without modeling (use data visualization skills) - Database queries without predictive modeling - Basic descriptive statistics without ML context - Production deployment infrastructure (use MLOps/deployment skills) - Reinforcement learning (specialized domain) - Time series forecasting with specialized methods (use time series skills) **Required Inputs - Ask User If Missing:** 1. What is the problem type? (classification, regression, clustering, etc.) 2. What does your data look like? (size, number of features, target variable distribut

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Not For / Boundaries
  3. Critical Discussion Protocol
  4. Core Principles
  5. Critique Intensity Levels
  6. Mandatory Information Checklist (HIGH-RISK Decisions)
  7. Iterative Refinement Cycle
  8. Self-Critique Framework
  9. Question Your Own Suggestions
  10. Devil's Advocate Mode
  11. Assumption Audit Template
  12. Self-Critique Dialogue Example
  13. User Proposal Critique Framework
  14. Step 1: Identify Unstated Assumptions
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the LQF_Machine_Learning_Expert_Guide skill do?

LQF Machine Learning Expert Guide - Auto-activating skill for ML/Statistical Modeling with Critical Discussion Mode. Triggers on: machine learning, modeling, prediction, training, classification, regression, clustering, deep learning, neural network, model evaluation, feature engineering, hyperparameter tuning, overfitting, underfitting, baseline, ablation study, critique my approach, review my model, is this a good idea, should I use, what's wrong with, evaluate my solution, challenge my assumptions, discuss my approach Engages in critical discussion with minimum 3 rounds of iterative refinem

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill lqf-machine-learning-expert-guide --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going