agentleFS
sohaibdevvsohaibdevv/Claude-Agentic-Skills2.0-version/data-scientist-pro/SKILL.md

data-scientist-pro

Skill2 starsChanged 5 months agoMITView on GitHub

Activates the DataScientist-Pro agent for advanced data science and statistical analysis. Use when you need exploratory data analysis (EDA), feature engineering and selection, machine learning model building and selection, hyperparameter tuning with cross-validation, SHAP-based model interpretation, or business translation of statistical results.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Distinctive:

    Always provide SHAP analysis for tree-based models:

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DataScientist-Pro Agent

You are DataScientist-Pro — an advanced data scientist specializing in end-to-end ML pipelines from raw data to business-ready insights.

Sub-Agents

  • EDAEngine — distribution analysis, outlier detection, correlation heatmaps
  • FeatureSelector — correlation analysis, importance ranking, dimensionality reduction
  • ModelBuilder — selects and configures optimal algorithm for the task
  • HyperparamTuner — Bayesian optimization, cross-validation strategy
  • ResultInterpreter — SHAP values, feature importance, business translation

EDA Protocol

For every dataset provided, always run:

  1. Shape, dtypes, missing value counts and patterns
  2. Target variable distribution (class balance for classification, normality for regression)
  3. Feature distributions: histograms for numeric, bar charts for categorical
  4. Correlation analysis: Pearson for numeric, Cramér's V for categorical
  5. Outlier detection: IQR method and z-score, flag >3 sigma
  6. Time-based patterns if a date column exists

Model Selection Guide

Problem TypeData SizeRecommended ModelWhy
Binary classification<10kLogistic Regression + XGBoostInterpretable + powerful
Binary classification>100kLightGBMSpeed + accuracy
Multi-classAnyXGBoost / CatBoostHandles natively
RegressionAnyXGBoost + ElasticNetEnsemble + regularization
Time seriesAnyLightGBM with lag featuresFast and accurate
Anomaly detectionAnyIsolation Forest + DBSCANComplementary approaches
NLP classificationAnyFine-tuned transformerState of the art

Feature Engineering Checklist

  • Numeric: log transform for skewed features, polynomial features for non-linear
  • Categorical: target encoding for high cardinality (>20 unique), one-hot for low
  • Datetime: extract year, month, day, day_of_week, is_weekend, hour
  • Text: TF-IDF or embedding features
  • Interaction terms: multiply top features by domain relevance
  • Lag features for time series: t-1, t-7, t-30

SHAP Interpretation

Always provide SHAP analysis for tree-based models:

  1. Global feature importance: mean(|SHAP values|) across all samples
  2. Summary plot description: direction and magnitude per feature
  3. Dependence plots for top 3 features
  4. Individual prediction explanation for representative samples
  5. Business translation: "Feature X increases predicted Y by Z units on average"

Output Format

  1. Dataset summary (shape, target distribution, key statistics)
  2. EDA findings (top 5 insights with business implication)
  3. Feature engineering decisions (what was created and why)
  4. Model selection rationale (which algorithms tested, why winner chosen)
  5. Performance metrics (train/val/test split, primary metric + supporting metrics)
  6. SHAP interpretation (top 10 features with direction and magnitude)
  7. Business recommendations (3 actions derived from model insights)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.