mcpbeat Sign in

Data Engineering Data Driven Feature Agent Skill

Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.

3k tokens
context cost
the whole folder, loaded on every use
17
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill data-engineering-data-driven-feature

What comes with it

10 386 bytes besides the instruction
sub-skills/1-exploratory-data-analysis.md
sub-skills/10-analytics-validation.md
sub-skills/11-experiment-setup.md
sub-skills/12-gradual-rollout.md
sub-skills/13-real-time-monitoring.md
sub-skills/14-statistical-analysis.md
sub-skills/15-business-impact-assessment.md
sub-skills/16-post-launch-optimization.md
sub-skills/2-business-hypothesis-development.md
sub-skills/3-statistical-experiment-design.md
sub-skills/4-feature-architecture-planning.md
sub-skills/5-analytics-instrumentation-design.md
sub-skills/6-data-pipeline-architecture.md
sub-skills/7-backend-implementation.md
sub-skills/8-frontend-implementation.md
sub-skills/9-ml-model-integration-if-applicable.md

The instruction itself

22 sections, as written by the author

Data-Driven Feature Development

Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation.

[Extended thinking: This workflow orchestrates a comprehensive data-driven development process from initial data analysis and hypothesis formulation through feature implementation with integrated analytics, A/B testing infrastructure, and post-launch analysis. Each phase leverages specialized agents to ensure features are built based on data insights, properly instrumented for measurement, and validated through controlled experiments. The workflow emphasizes modern product analytics practices, statistical rigor in testing, and continuous learning from user behavior.]

Use this skill when

  • Working on data-driven feature development tasks or workflows
  • Needing guidance, best practices, or checklists for data-driven feature development

Do not use this skill when

  • The task is unrelated to data-driven feature development
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Phase 1: Data Analysis and Hypothesis Formation

🧠 Knowledge Modules (Fractal Skills)

1. 1. Exploratory Data Analysis

2. 2. Business Hypothesis Development

3. 3. Statistical Experiment Design

4. 4. Feature Architecture Planning

5. 5. Analytics Instrumentation Design

6. 6. Data Pipeline Architecture

7. 7. Backend Implementation

8. 8. Frontend Implementation

9. 9. ML Model Integration (if applicable)

10. 10. Analytics Validation

11. 11. Experiment Setup

12. 12. Gradual Rollout

13. 13. Real-time Monitoring

14. 14. Statistical Analysis

15. 15. Business Impact Assessment

16. 16. Post-Launch Optimization

Other skills for the same job

different authors, same section of the catalogue
Webapp Testing
by anthropics
vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Systematic Debugging
by ratacat
×7

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

10k tokens scripts
Verification Before Completion
by ZhanlinCui
×6

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

1k tokens
Backtest Expert
by BaggaT236
×3

Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.

15k tokens scripts
Adaptyv
by christophacham
×3

Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.

16k tokens
Aeon
by christophacham
×3

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.

19k tokens

How to use it

Copy the folder

Take dokhacgiakhoa/data-engineering-data-driven-feature from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.