home / skills / anton-abyzov / specweave / data-scientist
/plugins/specweave-ml/skills/data-scientist
This skill helps you design and analyze experiments, forecast trends, and optimize business outcomes through robust statistical modeling and data analytics.
npx playbooks add skill anton-abyzov/specweave --skill data-scientistReview the files below or copy the command above to add this skill to your agents.
---
name: data-scientist
description: Statistical modeling - A/B testing, causal inference, customer analytics (CLV, churn), time series forecasting. Use for business analytics or experiment design.
model: opus
context: fork
---
## ⚠️ Chunking Rule
Large analyses (EDA + modeling + visualization) = 800+ lines. Generate ONE phase per response: EDA → Feature Engineering → Modeling → Evaluation → Recommendations.
This skill provides statistical modeling and business analytics expertise for A/B testing, causal inference, customer lifetime value (CLV) and churn modeling, and time series forecasting. It is designed to produce reproducible analyses and production-ready code in TypeScript, integrating with AI-assisted developer workflows. The skill emphasizes clear project phases and one-phase-per-response delivery for large analyses.
The skill inspects datasets, experiment designs, and business questions to recommend appropriate statistical methods and produce TypeScript implementations, tests, and documentation. For experiments it runs power calculations, randomization checks, and treatment effect estimation; for customer analytics it implements CLV, churn risk models, and cohort analyses; for time series it fits forecasts with diagnostics. Outputs include model specifications, evaluation metrics, code snippets, and recommended next steps.
Can this skill produce production-ready TypeScript code?
Yes. It generates TypeScript implementations, tests, and documentation suitable for integration into CI/CD pipelines.
How does the chunking rule affect workflow?
For analyses expected to be 800+ lines, responses are limited to a single phase (e.g., EDA) to keep outputs focused, reviewable, and iterative.