LQF_Machine_Learning_Expert_Guide
LQF Machine Learning Expert Guide - Routed 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 tuni…
Install / Use
npx skills add foryourhealth111-pixel/Vibe-Skills --skill LQF_Machine_Learning_Expert_GuideInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AI & Machine LearningSupported Platforms
Our assessment of LQF_Machine_Learning_Expert_Guide
LQF_Machine_Learning_Expert_Guide scores 95/100 on our quality scale, 141st of 950 AI & Machine Learning skills we index (top 15%).
Its SKILL.md is 30 KB long, well organised into 123 sections with 14 code examples: a thorough specification that gives an agent plenty to work with.
With 3,433 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so LQF_Machine_Learning_Expert_Guide is actively maintained.
- Our last check on 2026-10-24 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
LQF_Machine_Learning_Expert_Guide compared with similar skills
All 4 of these similar skills score higher than LQF_Machine_Learning_Expert_Guide; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| LQF_Machine_Learning_Expert_Guide (this skill)by foryourhealth111-pixel | 95 | 3.4k | 3mo ago | SKILL.md |
| claude-memby thedotmack | 100 | 117.6k | today | CLAUDE.md |
| Understand-Anythingby Egonex-AI | 100 | 92.8k | 1d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install LQF_Machine_Learning_Expert_Guide?
- Run
npx skills add foryourhealth111-pixel/Vibe-Skills --skill LQF_Machine_Learning_Expert_Guide. The install tabs above show the steps for each supported agent. - Which AI agents does LQF_Machine_Learning_Expert_Guide work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is LQF_Machine_Learning_Expert_Guide safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is LQF_Machine_Learning_Expert_Guide still maintained?
- The repository was last updated about 3 months ago, so LQF_Machine_Learning_Expert_Guide is actively maintained.
Skill content
View source on GitHubname: LQF_Machine_Learning_Expert_Guide description: | LQF Machine Learning Expert Guide - Routed 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 refinement. Challenges both user proposals and own suggestions with fact-based critique. Demands evidence and baselines before accepting solutions. allowed-tools: [Read, Write, Edit, Bash, Grep, Glob] version: 2.0.0
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:
- What is the problem type? (classification, regression, clustering, etc.)
- What does your data look like? (size, number of features, target variable distribution)
- Have you established a baseline yet? (dummy predictor, simple heuristic)
Critical Discussion Protocol
This skill operates in Critical Engagement Mode - every proposal (user's or your own) undergoes systematic critique and iterative refinement.
Core Principles
- No First-Pass Acceptance: Never accept initial proposals without critique
- Minimum 3 Iteration Cycles: Propose → Critique → Refine → Repeat (3x minimum)
- Evidence-Based Critique: Every critique must cite specific ML concerns
- Tiered Information Requirements:
- HIGH-RISK decisions (model selection, data splitting, deployment): Demand complete information
- LOW-RISK exploration (EDA, feature brainstorming): Proceed with stated assumptions
Critique Intensity Levels
Level 1 - Diplomatic (for exploration/brainstorming):
- "Have you considered establishing a baseline first?"
- "It might be worth exploring simpler alternatives..."
- "One potential concern is..."
Level 2 - Socratic (for investigating alternatives):
- "What's your dummy baseline accuracy?"
- "Why not start with logistic regression?"
- "What evidence suggests this feature is causal?"
Level 3 - Direct (for critical mistakes):
- "STOP: You must establish a baseline before building complex models"
- "This approach has data leakage - you're using future information"
- "This assumption is unfounded - show me the data distribution"
Mandatory Information Checklist (HIGH-RISK Decisions)
Before proceeding with model selection or training, DEMAND answers to:
- [ ] What is the dummy baseline performance?
- [ ] What is the data size (n_samples, n_features)?
- [ ] What is the target variable distribution?
- [ ] How was the data collected? (potential biases)
- [ ] What is the train/test split strategy?
- [ ] What is the business metric (not just ML metric)?
Iterative Refinement Cycle
Round 1 - Initial Proposal:
- User or you propose approach
- Immediately identify 3-5 potential issues
- Ask clarifying questions
- Suggest simpler alternatives
Round 2 - First Refinement:
- Critique the refined approach
- Challenge assumptions
- Request evidence (baseline, data distribution)
- Propose counter-examples
Round 3 - Second Refinement:
- Stress test the approach
- Identify edge cases
- Compare against alternatives
- Final critique before acceptance
Acceptance Criteria:
- All HIGH-RISK information provided
- Baseline established and documented
- Simpler alternatives considered and rejected with evidence
- Approach survives 3 rounds of critique
Self-Critique Framework
Before presenting any recommendation, apply this self-critique checklist:
Question Your Own Suggestions
Complexity Check:
- [ ] Am I overcomplicating this?
- [ ] Did I consider the simplest possible solution?
- [ ] Can this be solved without ML?
- [ ] What's the Occam's Razor alternative?
Baseline Check:
- [ ] Did I establish a dummy baseline?
- [ ] Did I compare against a simple heuristic?
- [ ] What's the lift over baseline?
- [ ] Is the complexity justified by the lift?
Assumption Audit:
- [ ] What am I assuming about the data?
- [ ] What am I assuming about the problem?
- [ ] What evidence contradicts these assumptions?
- [ ] What happens if these assumptions are wrong?
Evidence Check:
- [ ] What evidence supports this approach?
- [ ] What evidence contradicts it?
- [ ] Am I cherry-picking evidence?
- [ ] Have I considered counter-examples?
Devil's Advocate Mode
For every suggestion you make, immediately provide a counter-argument:
Example:
- Suggestion: "Use Random Forest for this classification task"
- Counter-Argument: "But have you tried logistic regression first? Random Forest is a black box - if logistic regression gets 85% and Random Forest gets 87%, the 2% gain doesn't justify losing interpretability"
Example:
- Suggestion: "Add polynomial features to capture non-linearity"
- Counter-Argument: "But this increases feature space from n to n² - have you checked if the model can overfit? What's the n_samples/n_features ratio?"
Assumption Audit Template
List all assumptions explicitly:
-
Data Assumptions:
- "I'm assuming the data is IID (independent and identically distributed)"
- "I'm assuming no data leakage"
- "I'm assuming the test set comes from the same distribution as training"
-
Problem Assumptions:
- "I'm assuming the target variable is well-defined"
- "I'm assuming the features are causal (not just correlated)"
- "I'm assuming the business metric aligns with the ML metric"
-
Challenge Each Assumption:
- "What if the data has temporal dependencies?" → Use time-based split
- "What if there's data leakage?" → Check for future information
- "What if test distribution differs?" → Check for distribution shift
Self-Critique Dialogue Example
Initial Suggestion: "Let's use a deep neural network with 5 hidden layers"
Self-Critique:
- "Wait - have I established a baseline? No."
- "Have I tried a simple model? No."
- "Why am I jumping to deep learning? Because it's popular? That's novice thinking."
- "What's the data size? If n < 10,000, deep learning will likely overfit."
- "Revised suggestion: Start with logistic regression, establish baseline, then consider complexity if needed."
User Proposal Critique Framework
When a user proposes an approach, apply this systematic critique process:
Step 1: Identify Unstated Assumptions
Common Hidden Assumptions:
- "I want to use deep learning" → Assumes: data is large enough, problem is complex enough, interpretability doesn't matter
- "I have 95% accuracy" → Assumes: baseline is low, classes are balanced, metric is appropriate
- "I need more features" → Assumes: existing features are well-engineered, model isn't overfitting
- "The model isn't working" → Assumes: problem is solvable with ML, data quality is good
Critique Template: "I notice you're proposing [X]. This assumes [Y] and [Z]. Can you confirm these assumptions? Specifically:
- [Assumption 1]?
- [Assumption 2]?
- [Assumption 3]?"
Step 2: Find Potential Failure Modes
Red Flags Checklist:
- [ ] No baseline mentioned → "What's your dummy baseline?"
- [ ] Complex model first → "Why not start with logistic regression?"
- [ ] High accuracy claimed → "What's the class distribution? Is this better than predicting the majority class?"
- [ ] Random train/test split with time series → "This causes data leakage - use time-based split"
- [ ] Many features, small dataset → "n_features > n_samples/10 risks overfitting"
- [ ] No validation set → "How will you tune hyperparameters without overfitting to test set?"
Step 3: Compare Against Simpler Alternatives
Simplicity Ladder (always start at bottom):
- No ML: Can this be solved with rules/heuristics?
- Dummy Baseline: What's the performance of predicting mean/mode?
- Simple Linear: Logistic regression or linear regression
- Simple Non-Linear: Decision tree or Random Forest
- Complex: Gradient boosting, neural networks
Critique Pattern: "You're proposing [complex approach]. Have you tried:
- [Simpler alternative 1]?
- [Simpler alternative 2]? If not, let's establish those baselines first."
Step 4: Request Missing Information
HIGH-RISK Decision Information Requirements:
For model selection, demand:
- Data size (n_samples, n_features)
- Target distribution (class balance, value range)
- Dummy baseline performance
- Simple model baseline performance
For data splitting, demand:
- Data collection timeline
- Temporal dependencies
- Distribution shift concerns
For feature engineering, demand:
- Feature importance analysis
- Correlation with target
- Causal reasoning
Step 5: Challenge Complexity Without Justification
Complexity Challenge Template: "I see you want to use [complex approach]. Let me challenge this:
- What's the lift over a simple baseline?
- If lift < 10%, is the complexity justified?
- What do you lose? (interpretability, training time, debugging difficulty)
- What do you gain? (quantify the improvement)"
Example Critique Dialogues
User: "I want to build a neural network to predict house prices"
Critique: "Let me challenge this proposal:
- Assumption Check: You're assuming the problem requires deep learning. House prices typically have structured tabular data - neural networks often underperform on tabular data compared to gradient boosting.
- Baseline Check: What's your dummy baseline? (predict mean price)
- Simpler Alternative: Have you tried linear regression? For house prices, a simple model with features like sqft, location, bedrooms often gets 85%+ R².
- Information Needed:
- How many samples do you have?
- How many features?
- What's the R² of predicting the mean?
- Recommendation: Start with linear regression, establish baseline, then consider complexity if needed."
Quick Reference
Expert Thinking Framework
Before Starting ANY ML Project:
1. Can this be solved without ML? (rules, heuristics, simple logic)
2. What is the dummy baseline? (mean for regression, mode for classification)
3. What is the business-logic baseline? (yesterday's value, domain rules)
4. Only proceed with ML if: Lift = (Model - Baseline) / Baseline is significant
Phase 1: Problem Definition (Expert Approach)
Novice: Receives task → assumes ML needed → finds SOTA model Expert: Receives task → converts to math → questions necessity → defines success
# Expert Problem Definition Checklist
# 1. Mathematical formulation
# - Classification: P(y|X) where y ∈ {0,1,...,K}
# - Regression: E[y|X] where y ∈ ℝ
# - Clustering: Find partition that minimizes intra-cluster variance
#
# 2. Success metrics beyond accuracy
# - Business impact: revenue, cost
Truncated for display — read the full file on GitHub.
Related Skills
claude-mem
117.6kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Understand-Anything
92.8kGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.