Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
pixel-process-ug avatar

Senior Data Scientist

  • 68 installs
  • 1 repo stars
  • Updated March 16, 2026
  • pixel-process-ug/superkit-agents

Helps with ai & agent building tasks.

About

senior-data-scientist is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • senior-data-scientist
  • AI & Agent Building
  • AI-coding skill

Senior Data Scientist by the numbers

  • 68 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #5,858 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pixel-process-ug/superkit-agents --skill senior-data-scientist

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs68
repo stars1
Last updatedMarch 16, 2026
Repositorypixel-process-ug/superkit-agents

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Senior Data Scientist

Overview

Build end-to-end data science workflows from data exploration through model deployment. This skill covers data preprocessing, feature engineering, model selection, hyperparameter tuning, cross-validation, experiment tracking with MLflow/W&B, statistical testing, visualization with matplotlib/seaborn/plotly, and Jupyter notebook best practices.

Announce at start: "I'm using the senior-data-scientist skill for data science workflow."

---

Phase 1: Data Understanding

Goal: Profile the dataset and establish a baseline before any modeling.

Actions

1. Load and profile the dataset (shape, types, distributions) 2. Identify missing values, outliers, and data quality issues 3. Perform exploratory data analysis (EDA) 4. Define the target variable and success metrics 5. Establish baseline performance

Baseline Models (Always Start Here)

TaskBaseline ModelWhy
ClassificationMajority class classifierLower bound for accuracy
ClassificationLogistic regressionSimple, interpretable
RegressionMean predictorLower bound for RMSE
RegressionLinear regressionSimple, interpretable
Time seriesNaive forecast (previous value)Lower bound for MAE
Time seriesSeasonal naiveCaptures basic seasonality

STOP — Do NOT proceed to Phase 2 until:

  • [ ] Dataset is profiled (shape, types, distributions)
  • [ ] Missing values and outliers are documented
  • [ ] Target variable is defined
  • [ ] Success metrics are chosen
  • [ ] Baseline performance is established

---

Phase 2: Feature Engineering

Goal: Transform raw data into features that improve model performance.

Actions

1. Handle missing values (imputation strategy) 2. Encode categorical variables 3. Scale/normalize numerical features 4. Create derived features 5. Feature selection (remove redundant/irrelevant)

Missing Value Strategy Decision Table

StrategyWhen to UseImplementation
Drop rows< 5% missing, MCARdf.dropna()
Mean/MedianNumerical, no outliersSimpleImputer(strategy='median')
ModeCategoricalSimpleImputer(strategy='most_frequent')
KNN ImputerStructured missing patternsKNNImputer(n_neighbors=5)
IterativeComplex relationshipsIterativeImputer()
Flag + ImputeMissingness is informativeAdd is_missing column + impute

Categorical Encoding Decision Table

MethodWhenCardinality
One-HotNominal, low cardinality< 10 categories
Label/OrdinalOrdinal featuresAny
Target EncodingHigh cardinality nominal> 10 categories
Frequency EncodingWhen frequency mattersAny
Binary EncodingVery high cardinality> 50 categories

Scaling Decision Table

ScalerWhenRobust to Outliers?
StandardScalerDefault choice (mean=0, std=1)No
RobustScalerOutliers present (median/IQR)Yes
MinMaxScalerNeural networks, distance-based [0,1]No

Feature Types and Engineering

Feature TypeTechniques
NumericalLog transform, polynomial, binning, interactions (A*B, A/B)
TemporalHour, day-of-week, is_weekend, time_since_event, cyclical (sin/cos), lags
TextTF-IDF, word count, sentiment scores, named entities, embeddings
CategoricalEncoding (above), interaction with numerical features

Feature Selection Decision Table

MethodTypeUse When
Correlation matrixFilterInitial exploration
Mutual informationFilterNon-linear relationships
Recursive Feature EliminationWrapperModel-specific selection
L1 RegularizationEmbeddedLinear models
Feature importanceEmbeddedTree-based models
Permutation importanceModel-agnosticFinal validation

STOP — Do NOT proceed to Phase 3 until:

  • [ ] Missing values are handled with justified strategy
  • [ ] Categorical variables are encoded appropriately
  • [ ] Numerical features are scaled
  • [ ] Feature engineering is done BEFORE train/test split on training data only
  • [ ] Feature selection has reduced dimensionality if needed

---

Phase 3: Modeling

Goal: Select, train, and evaluate candidate models.

Actions

1. Select candidate algorithms 2. Set up cross-validation strategy 3. Train and evaluate candidates 4. Hyperparameter tuning 5. Final model selection and evaluation

Algorithm Decision Table

Data CharacteristicsTry FirstAlso Consider
Tabular, < 10K rowsRandom Forest, XGBoostLogistic/Linear Regression
Tabular, > 10K rowsXGBoost, LightGBMCatBoost, Neural Network
High dimensionalityLasso/Ridge, SVMRandom Forest with selection
Time seriesProphet, ARIMALSTM, XGBoost with lag features
Text classificationFine-tuned transformerTF-IDF + Logistic Regression
Image classificationPre-trained CNN (ResNet, EfficientNet)Vision Transformer
RegressionXGBoost, Random ForestLinear Regression, Neural Network
Anomaly detectionIsolation ForestLOF, Autoencoder

Cross-Validation Strategy Decision Table

StrategyWhenCode
K-Fold (k=5)Default, balanced dataKFold(n_splits=5)
Stratified K-FoldClassification, imbalancedStratifiedKFold(n_splits=5)
Time Series SplitTemporal dataTimeSeriesSplit(n_splits=5)
Group K-FoldGrouped observationsGroupKFold(n_splits=5)
Leave-One-OutVery small datasetsLeaveOneOut()

Evaluation Metrics Decision Table

TaskPrimary MetricSecondary Metrics
Binary ClassificationAUC-ROCF1, Precision, Recall, AP
MulticlassMacro F1Accuracy, Confusion Matrix
RegressionRMSEMAE, R-squared, MAPE
RankingNDCGMAP, MRR
Anomaly DetectionF1, APPrecision@K, Recall@K

Hyperparameter Tuning Decision Table

MethodCompute BudgetSearch SpaceImplementation
Grid SearchLow (< 100 combos)Small, known rangesGridSearchCV
Random SearchMediumLarge, uncertainRandomizedSearchCV
Bayesian (Optuna)AnyLarge, expensiveoptuna.create_study()
Successive HalvingLargeMany candidatesHalvingRandomSearchCV

Common Hyperparameters (XGBoost/LightGBM)

param_space = {
    'n_estimators': [100, 300, 500, 1000],
    'max_depth': [3, 5, 7, 9],
    'learning_rate': [0.01, 0.05, 0.1],
    'subsample': [0.7, 0.8, 0.9],
    'colsample_bytree': [0.7, 0.8, 0.9],
    'min_child_weight': [1, 3, 5],
}

STOP — Do NOT proceed to Phase 4 until:

  • [ ] At least 2 candidate models are evaluated
  • [ ] Cross-validation is used (not just train/test split)
  • [ ] Results beat the baseline from Phase 1
  • [ ] Best model is selected with justification
  • [ ] Overfitting is checked (train vs validation gap)

---

Phase 4: Deployment

Goal: Serialize, serve, and monitor the model in production.

Actions

1. Serialize model and preprocessing pipeline 2. Create prediction API or batch pipeline 3. Set up monitoring for data drift and model degradation 4. Document model card (inputs, outputs, limitations, biases)

STOP — Deployment complete when:

  • [ ] Model is serialized with preprocessing pipeline
  • [ ] Prediction API or batch pipeline works end-to-end
  • [ ] Monitoring is configured for data drift
  • [ ] Model card is documented

---

Experiment Tracking

MLflow Pattern

import mlflow

mlflow.set_experiment("customer-churn-prediction")

with mlflow.start_run(run_name="xgboost-v2"):
    mlflow.log_params(params)
    mlflow.log_metrics({"auc": auc_score, "f1": f1_score})
    mlflow.log_artifact("confusion_matrix.png")
    mlflow.sklearn.log_model(pipeline, "model")
    mlflow.set_tag("version", "2.1")

What to Track

CategoryItems
ParametersAll hyperparameters, random seed
MetricsTrain and validation metrics
DataData version/hash, feature list
ArtifactsPlots, reports, model files
MetadataTraining duration, model size

---

Statistical Tests Decision Table

QuestionTestAssumption
Two group means different?t-test (independent)Normal distribution
Two groups (non-normal)?Mann-Whitney UNone
Paired measurements?Paired t-testNormal differences
3+ group means?ANOVANormal, equal variance
Categorical association?Chi-squaredExpected freq > 5
Distribution normal?Shapiro-Wilkn < 5000
Two distributions different?Kolmogorov-SmirnovContinuous data

P-Value Guidelines

  • p < 0.05: statistically significant (conventional)
  • Always report effect size alongside p-value
  • Adjust for multiple comparisons (Bonferroni, FDR)
  • Statistical significance is not practical significance

---

Visualization Decision Table

Data TypePlotLibrary
DistributionHistogram, KDE, Box plotseaborn
ComparisonBar chart, Grouped barmatplotlib
CorrelationScatter, Heatmapseaborn
TrendLine chartmatplotlib/plotly
CompositionStacked bar, Pie (max 5 slices)matplotlib
InteractiveScatter, Line, Dashboardplotly

Visualization Rules

  • Title every plot descriptively
  • Label axes with units
  • Use colorblind-safe palettes (seaborn: colorblind)
  • Start y-axis at 0 for bar charts
  • Annotate key findings directly on plots

---

Jupyter Notebook Structure

1. ## Setup (imports, configuration)
2. ## Data Loading
3. ## Exploratory Data Analysis
4. ## Data Preprocessing
5. ## Feature Engineering
6. ## Modeling
7. ## Evaluation
8. ## Conclusions

Notebook Best Practices

  • Restart and run all before sharing
  • Keep cells focused and sequential
  • Use markdown cells for explanations
  • Extract reusable code to .py modules
  • Version control with nbstripout
  • Pin all dependency versions

---

Anti-Patterns / Common Mistakes

Anti-PatternWhy It Is WrongCorrect Approach
Training on test dataData leakage, inflated metricsStrict train/test separation
Feature engineering before splitLeaks test information into featuresEngineer on training data only
Reporting training metricsNot generalizableReport validation/test metrics
Accuracy on imbalanced dataMisleading (majority class wins)Use F1, AUC-ROC, or AP
Tuning on test setOverfitting to test dataUse validation set for tuning
No baseline comparisonCannot measure improvementAlways establish baseline first
Cherry-picking evaluation examplesSelection biasReport on full evaluation set
Deploying without drift monitoringSilent model degradationMonitor input distributions

---

Integration Points

SkillRelationship
senior-prompt-engineerPrompt evaluation uses statistical testing methods
testing-strategyML testing follows the evaluation methodology
performance-optimizationModel inference optimization follows measurement cycle
acceptance-testingModel performance thresholds become acceptance criteria
llm-as-judgeSubjective output evaluation uses LLM-as-judge
code-reviewNotebook and pipeline code reviewed for quality

---

Skill Type

FLEXIBLE — Adapt preprocessing, modeling, and evaluation approaches to the specific data characteristics, business requirements, and compute constraints. The four-phase process and experiment tracking are strongly recommended. Always establish a baseline before modeling.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.