data-scientist▌
404kidwiz/claude-supercode-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Provides statistical analysis and predictive modeling expertise specializing in machine learning, experimental design, and causal inference. Builds rigorous models and translates complex statistical findings into actionable business insights with proper validation and uncertainty quantification.
Data Scientist
Purpose
Provides statistical analysis and predictive modeling expertise specializing in machine learning, experimental design, and causal inference. Builds rigorous models and translates complex statistical findings into actionable business insights with proper validation and uncertainty quantification.
When to Use
- Performing exploratory data analysis (EDA) to find patterns and anomalies
- Building predictive models (classification, regression, forecasting)
- Designing and analyzing A/B tests or experiments
- Conducting rigorous statistical hypothesis testing
- Creating advanced visualizations and data narratives
- Defining metrics and KPIs for business problems
Core Capabilities
Statistical Modeling
- Building predictive models using regression, classification, and clustering
- Implementing time series forecasting and causal inference
- Designing and analyzing A/B tests and experiments
- Performing feature engineering and selection
Machine Learning
- Training and evaluating supervised and unsupervised learning models
- Implementing deep learning models for complex patterns
- Performing hyperparameter tuning and model optimization
- Validating models with cross-validation and holdout sets
Data Exploration
- Conducting exploratory data analysis (EDA) to discover patterns
- Identifying anomalies and outliers in datasets
- Creating advanced visualizations for insight discovery
- Generating hypotheses from data exploration
Communication and Storytelling
- Translating statistical findings into business language
- Creating compelling data narratives for stakeholders
- Building interactive notebooks and reports
- Presenting findings with uncertainty quantification
3. Core Workflows
Workflow 1: Exploratory Data Analysis (EDA) & Cleaning
Goal: Understand data distribution, quality, and relationships before modeling.
Steps:
-
Load and Profile Data
import pandas as pd import numpy as np import seaborn as sns import matplotlib.pyplot as plt # Load data df = pd.read_csv("customer_data.csv") # Basic profiling print(df.info()) print(df.describe()) # Missing values analysis missing = df.isnull().sum() / len(df) print(missing[missing > 0].sort_values(ascending=False)) -
Univariate Analysis (Distributions)
# Numerical features num_cols = df.select_dtypes(include=[np.number]).columns for col in num_cols: plt.figure(figsize=(10, 4)) plt.subplot(1, 2, 1) sns.histplot(df[col], kde=True) plt.subplot(1, 2, 2) sns.boxplot(x=df[col]) plt.show() # Categorical features cat_cols = df.select_dtypes(exclude=[np.number]).columns for col in cat_cols: print(df[col].value_counts(normalize=True)) -
Bivariate Analysis (Relationships)
# Correlation matrix corr = df.corr() sns.heatmap(corr, annot=True, cmap='coolwarm') # Target vs Features target = 'churn' sns.boxplot(x=target, y='tenure', data=df) -
Data Cleaning
# Impute missing values df['age'].fillna(df['age'].median(), inplace=True) df['category'].fillna('Unknown', inplace=True) # Handle outliers (Example: Cap at 99th percentile) cap = df['income'].quantile(0.99) df['income'] = np.where(df['income'] > cap, cap, df['income'])
Verification:
- No missing values in critical columns.
- Distributions understood (normal vs skewed).
- Target variable balance checked.
Workflow 3: A/B Test Analysis
Goal: Analyze results of a website conversion experiment.
Steps:
-
Define Hypothesis
- H0: Conversion Rate B <= Conversion Rate A
- H1: Conversion Rate B > Conversion Rate A
- Alpha: 0.05
-
Load and Aggregate Data
# data: ['user_id', 'group', 'converted'] results = df.groupby('group')['converted'].agg(['count', 'sum', 'mean']) results.columns = ['n_users', 'conversions', 'conversion_rate'] print(results) -
Statistical Test (Proportions Z-test)
from statsmodels.stats.proportion import proportions_ztest control = results.loc['A'] treatment = results.loc['B'] count = np.array([treatment['conversions'], control['conversions']]) nobs = np.array([treatment['n_users'], control['n_users']]) stat, p_value = proportions_ztest(count, nobs, alternative='larger') print(f"Z-statistic: {stat:.4f}") print(f"P-value: {p_value:.4f}") -
Confidence Intervals
from statsmodels.stats.proportion import proportion_confint (lower_con, lower_treat), (upper_con, upper_treat) = proportion_confint(count, nobs, alpha=0.05) print(f"Control CI: [{lower_con:.4f}, {upper_con:.4f}]") print(f"Treatment CI: [{lower_treat:.4f}, {upper_treat:.4f}]") -
Conclusion
- If p-value < 0.05: Reject H0. Variation B is statistically significantly better.
- Check practical significance (Lift magnitude).
Workflow 5: Causal Inference (Propensity Score Matching)
Goal: Estimate impact of a "Premium Membership" on "Spend" when A/B test isn't possible (observational data).
Steps:
-
Problem Setup
- Treatment: Premium Member (1) vs Free (0)
- Outcome: Annual Spend ($)
- Confounders: Age, Income, Location, Tenure (Factors affecting both membership and spend)
-
Calculate Propensity Scores
from sklearn.linear_model import LogisticRegression # P(Treatment=1 | Confounders) confounders = ['age', 'income', 'tenure'] logit = LogisticRegression() logit.fit(df[confounders], df['is_premium']) df['propensity_score'] = logit.predict_proba(df[co
How to use data-scientist on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add data-scientist
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches data-scientist from GitHub repository 404kidwiz/claude-supercode-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate data-scientist. Access the skill through slash commands (e.g., /data-scientist) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★63 reviews- ★★★★★Neel Rahman· Dec 20, 2024
data-scientist is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aditi Ramirez· Dec 16, 2024
data-scientist reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kaira Jain· Dec 8, 2024
data-scientist has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Dhruvi Jain· Dec 4, 2024
Keeps context tight: data-scientist is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Jin Jackson· Dec 4, 2024
Registry listing for data-scientist matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kofi Iyer· Nov 27, 2024
data-scientist fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Oshnikdeep· Nov 23, 2024
Registry listing for data-scientist matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Luis Gupta· Nov 23, 2024
Keeps context tight: data-scientist is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Amina Ndlovu· Nov 19, 2024
I recommend data-scientist for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kaira Khanna· Nov 11, 2024
data-scientist reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 63