sklearn-explainability
Skill22 starsChanged 9 months agoMITView on GitHub
Advanced sub-skill for scikit-learn focused on model interpretability, feature importance, and diagnostic tools. Covers global and local explanations using built-in inspection tools and SHAP/LIME integrations.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
Check Feature Correlations: - If two features are highly correlated, importance will be split between them, making both look "less …
- Distinctive: line 61
Don't use Feature Importance on Training Data: - Always calculate it on the Test Set to see what features actually help with generalization.
- Distinctive: line 110
If a feature has 99% importance and wasn't expected to, it's likely a data leak (e.g., a sample timestamp or ID).
- Distinctive: line 114
Run permutation importance with different random seeds.
- Distinctive: line 118
Use 2D PDP to see if the model captured the interaction between features (e.g., Pressure only matters if Temperature > 100°C).
- Distinctive: line 132
If Feature_A and Feature_B are 100% correlated, the model might only use one.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
scikit-learn - Explainability & Interpretability
In scientific research, a model's "why" is as important as its "what". This guide focuses on tools that reveal the decision-making process of machine learning models, ensuring they are scientifically valid and not just overfitting on artifacts.
When to Use
- Validating that a model uses physically meaningful features (e.g., in drug discovery).
- Identifying biases or "shortcuts" the model has learned from the training data.
- Explaining individual predictions to non-experts (Local explanations).
- Ranking the global impact of variables on a complex system (Global explanations).
- Scientific auditing and regulatory compliance.
Core Principles
1. Model-Specific vs. Model-Agnostic
- Model-Specific: Tools like
feature_importances_in Random Forests. Fast but tied to one architecture. - Model-Agnostic: Tools like SHAP or Permutation Importance. Work on any model (SVM, MLP, etc.) but are more compute-intensive.
2. Global vs. Local Explanations
- Global: How does the feature "Temperature" affect the model overall?
- Local: Why did the model predict "Reaction Failed" for this specific sample?
3. Feature Importance vs. Feature Contribution
Importance tells you if a feature is used; Contribution tells you how it changed the output (positive or negative).
Quick Reference: Built-in Inspection
from sklearn.inspection import permutation_importance, PartialDependenceDisplay
# 1. Permutation Importance (Better than default tree importance)
result = permutation_importance(model, X_test, y_test, n_repeats=10)
print(result.importances_mean)
# 2. Partial Dependence Plots (How one feature affects prediction)
PartialDependenceDisplay.from_estimator(model, X, features=['temp', 'pressure'])Critical Rules
✅ DO
- Prefer Permutation Importance over default RandomForest.feature_importances_ - Default importance is biased toward high-cardinality features (like unique IDs).
- Use PartialDependenceDisplay - To visualize the relationship between a feature and the target (Linear, Exponential, or Sigmoid).
- Scale Features before Interpretability - Many models (like Logistic Regression) require scaling for their coefficients (β) to be comparable.
- Check Feature Correlations - If two features are highly correlated, importance will be split between them, making both look "less important" than they are.
❌ DON'T
- Don't trust coefficients (β) of unregularized models - High variance in coefficients can lead to false conclusions about feature importance.
- Don't use Feature Importance on Training Data - Always calculate it on the Test Set to see what features actually help with generalization.
- Don't confuse Correlation with Causation - ML models show which features are predictive, not necessarily which ones are causative.
Interpretation Patterns
1. SHAP Integration (The Gold Standard)
import shap
# Works for any scikit-learn model
explainer = shap.Explainer(model.predict, X_test)
shap_values = explainer(X_test)
# Visualize global importance
shap.plots.bar(shap_values)
# Visualize local explanation for the first sample
shap.plots.waterfall(shap_values[0])2. Partial Dependence (PDP) for Science
from sklearn.inspection import PartialDependenceDisplay
# Check if the model learned the correct physical law
# (e.g., does the reaction rate increase with temperature?)
fig, ax = plt.subplots(figsize=(8, 4))
PartialDependenceDisplay.from_estimator(model, X, [0, (0, 1)], ax=ax)
# [0] is a 1D plot, [(0, 1)] is a 2D interaction plotAdvanced: Feature Contribution (ELI5 style)
For a single prediction, see which features pushed it towards which class.
def explain_prediction(model, sample):
# For linear models, this is: intercept + sum(coef * value)
prediction = model.predict_proba(sample)
# ... logic to map coefficients to feature names ...
passPractical Workflows: Validating a Scientific Model
Step 1: Detect "Leakage" Features
If a feature has 99% importance and wasn't expected to, it's likely a data leak (e.g., a sample timestamp or ID).
Step 2: Stability Analysis
Run permutation importance with different random seeds. If the top features change significantly, the model is unstable and unreliable.
Step 3: Interaction Check
Use 2D PDP to see if the model captured the interaction between features (e.g., Pressure only matters if Temperature > 100°C).
Common Pitfalls
The "Default Importance" Bias
In RandomForest, features with many categories (like Serial_Number) look very important because the tree can split on them many times.
# ✅ Solution: Use Permutation Importance on the test set instead.Multicollinearity Ghosting
If Feature_A and Feature_B are 100% correlated, the model might only use one.
# ✅ Solution: Use hierarchical clustering on features or check VIF
# before interpreting importance.Explainability turns Machine Learning into a true scientific tool. It allows researchers to move beyond the "Black Box" and extract new hypotheses directly from trained models.
In this repository69 other files it gives its agents.
- aseSkill
- astropySkill
- biopythonSkill
- chempySkill
- cobrapySkill
- dask-optimizationSkill
- daskSkill
- dowhySkill
- duckdbSkill
- example-skillSkill
- fastapi-streamlitSkill
- geopandasSkill
- gmsh-meshioSkill
- h5pySkill
- jax-pdeSkill
- jaxSkill
- lifelinesSkill
- matplotlib-proSkill
- matplotlibSkill
- mdanalysisSkill
- mneSkill
- networkxSkill
- numbaSkill
- numpy-low-levelSkill
- numpySkill
- openbabelSkill
- opencvSkill
- ortoolsSkill
- pandas-performanceSkill
- pennylaneSkill
- photutilsSkill
- plotlySkill
- polarsSkill
- prodySkill
- pydicomSkill
- pymcSkill
- pyomoSkill
- pyprojSkill
- pysamSkill
- pyscfSkill
- pytorch-deploymentSkill
- pytorch-geometricSkill
- pytorch-researchSkill
- pytorchSkill
- qiskit-hardwareSkill
- qiskitSkill
- qutipSkill
- rasterioSkill
- rdkitSkill
- scanpySkill
- scikit-bioSkill
- scikit-imageSkill
- scikit-learnSkill
- scikit-videoSkill
- scipySkill
- seabornSkill
- shapelySkill
- simpySkill
- sklearn-advancedSkill
- sktime-tsfreshSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

