skill-library-mcp 1.0.0

package/skills/mixpanel-automation/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: mixpanel-automation
+description: "Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Mixpanel Automation via Rube MCP
+
+Automate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`
+3. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Aggregate Event Data
+
+**When to use**: User wants to count events, get totals, or track event trends over time
+
+**Tool sequence**:
+1. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]
+2. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]
+
+**Key parameters**:
+- `event`: Event name or array of event names to aggregate
+- `from_date` / `to_date`: Date range in 'YYYY-MM-DD' format
+- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')
+- `type`: Aggregation type ('general', 'unique', 'average')
+- `where`: Filter expression for event properties
+
+**Pitfalls**:
+- Date format must be 'YYYY-MM-DD'; other formats cause errors
+- Event names are case-sensitive; use exact names from your Mixpanel project
+- `where` filter uses Mixpanel expression syntax (e.g., `properties["country"] == "US"`)
+- Maximum date range may be limited depending on your Mixpanel plan
+
+### 2. Run Segmentation Queries
+
+**When to use**: User wants to break down events by properties for detailed analysis
+
+**Tool sequence**:
+1. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]
+
+**Key parameters**:
+- `event`: Event name to segment
+- `from_date` / `to_date`: Date range in 'YYYY-MM-DD' format
+- `on`: Property to segment by (e.g., `properties["country"]`)
+- `unit`: Time granularity
+- `type`: Count type ('general', 'unique', 'average')
+- `where`: Filter expression
+- `limit`: Maximum number of segments to return
+
+**Pitfalls**:
+- The `on` parameter uses Mixpanel property expression syntax
+- Property references must use `properties["prop_name"]` format
+- Segmentation on high-cardinality properties returns capped results; use `limit`
+- Results are grouped by the segmentation property and time unit
+
+### 3. Analyze Funnels
+
+**When to use**: User wants to track conversion funnels and identify drop-off points
+
+**Tool sequence**:
+1. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]
+2. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]
+
+**Key parameters**:
+- `funnel_id`: ID of the saved funnel to query
+- `from_date` / `to_date`: Date range
+- `unit`: Time granularity
+- `where`: Filter expression
+- `on`: Property to segment funnel by
+- `length`: Conversion window in days
+
+**Pitfalls**:
+- `funnel_id` is required; resolve via LIST_FUNNELS first
+- Funnels must be created in Mixpanel UI first; API only queries existing funnels
+- Conversion window (`length`) defaults vary; set explicitly for accuracy
+- Large date ranges with segmentation can produce very large responses
+
+### 4. Manage User Profiles
+
+**When to use**: User wants to query or update user profiles in Mixpanel
+
+**Tool sequence**:
+1. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]
+2. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]
+
+**Key parameters**:
+- `where`: Filter expression for profile properties (e.g., `properties["plan"] == "premium"`)
+- `output_properties`: Array of property names to include in results
+- `page`: Page number for pagination
+- `session_id`: Session ID for consistent pagination (from first response)
+- For batch update: array of profile updates with `$distinct_id` and property operations
+
+**Pitfalls**:
+- Profile queries return paginated results; use `session_id` from first response for consistent paging
+- `where` uses Mixpanel expression syntax for profile properties
+- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles
+- Batch update has a maximum number of profiles per request; chunk larger updates
+- Profile property names are case-sensitive
+
+### 5. Manage Cohorts
+
+**When to use**: User wants to list or analyze user cohorts
+
+**Tool sequence**:
+1. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]
+
+**Key parameters**:
+- No required parameters; returns all accessible cohorts
+- Response includes cohort `id`, `name`, `description`, `count`
+
+**Pitfalls**:
+- Cohorts are created and managed in Mixpanel UI; API provides read access
+- Cohort IDs are numeric; use exact ID from list results
+- Cohort counts may be approximate for very large cohorts
+- Cohorts can be used as filters in other queries via `where` expressions
+
+### 6. Run JQL and Insight Queries
+
+**When to use**: User wants to run custom JQL queries or insight analyses
+
+**Tool sequence**:
+1. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]
+2. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]
+
+**Key parameters**:
+- For JQL: `script` containing the JQL JavaScript code
+- For Insight: `bookmark_id` of the saved insight
+- `project_id`: Project context for the query
+
+**Pitfalls**:
+- JQL uses JavaScript-like syntax specific to Mixpanel
+- JQL queries have execution time limits; optimize for efficiency
+- Insight `bookmark_id` must reference an existing saved insight
+- JQL is a legacy feature; check Mixpanel documentation for current availability
+
+## Common Patterns
+
+### ID Resolution
+
+**Project name -> Project ID**:
+```
+1. Call MIXPANEL_GET_ALL_PROJECTS
+2. Find project by name in results
+3. Extract project id
+```
+
+**Funnel name -> Funnel ID**:
+```
+1. Call MIXPANEL_LIST_FUNNELS
+2. Find funnel by name
+3. Extract funnel_id
+```
+
+### Mixpanel Expression Syntax
+
+Used in `where` and `on` parameters:
+- Property reference: `properties["property_name"]`
+- Equality: `properties["country"] == "US"`
+- Comparison: `properties["age"] > 25`
+- Boolean: `properties["is_premium"] == true`
+- Contains: `"search_term" in properties["name"]`
+- AND/OR: `properties["country"] == "US" and properties["plan"] == "pro"`
+
+### Pagination
+
+- Event queries: Follow date-based pagination by adjusting date ranges
+- Profile queries: Use `page` number and `session_id` for consistent results
+- Funnel/cohort lists: Typically return complete results without pagination
+
+## Known Pitfalls
+
+**Date Formats**:
+- Always use 'YYYY-MM-DD' format
+- Date ranges are inclusive on both ends
+- Data freshness depends on Mixpanel ingestion delay (typically minutes)
+
+**Expression Syntax**:
+- Property references always use `properties["name"]` format
+- String values must be quoted: `properties["status"] == "active"`
+- Numeric values are unquoted: `properties["count"] > 10`
+- Boolean values: `true` / `false` (lowercase)
+
+**Rate Limits**:
+- Mixpanel API has rate limits per project
+- Large segmentation queries may time out; reduce date range or segments
+- Use batch operations where available to minimize API calls
+
+**Response Parsing**:
+- Response data may be nested under `data` key
+- Event data is typically grouped by date and segment
+- Numeric values may be returned as strings; parse explicitly
+- Empty date ranges return empty objects, not empty arrays
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |
+| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |
+| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |
+| List funnels | MIXPANEL_LIST_FUNNELS | (none) |
+| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |
+| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |
+| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |
+| List cohorts | MIXPANEL_COHORTS_LIST | (none) |
+| JQL query | MIXPANEL_JQL_QUERY | script |
+| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |

package/skills/ml-engineer/SKILL.md

@@ -0,0 +1,168 @@
+---
+name: ml-engineer
+description: Build production ML systems with PyTorch 2.x, TensorFlow, and
+  modern ML frameworks. Implements model serving, feature engineering, A/B
+  testing, and monitoring. Use PROACTIVELY for ML model deployment, inference
+  optimization, or production ML infrastructure.
+metadata:
+  model: inherit
+---
+
+## Use this skill when
+
+- Working on ml engineer tasks or workflows
+- Needing guidance, best practices, or checklists for ml engineer
+
+## Do not use this skill when
+
+- The task is unrelated to ml engineer
+- 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`.
+
+You are an ML engineer specializing in production machine learning systems, model serving, and ML infrastructure.
+
+## Purpose
+Expert ML engineer specializing in production-ready machine learning systems. Masters modern ML frameworks (PyTorch 2.x, TensorFlow 2.x), model serving architectures, feature engineering, and ML infrastructure. Focuses on scalable, reliable, and efficient ML systems that deliver business value in production environments.
+
+## Capabilities
+
+### Core ML Frameworks & Libraries
+- PyTorch 2.x with torch.compile, FSDP, and distributed training capabilities
+- TensorFlow 2.x/Keras with tf.function, mixed precision, and TensorFlow Serving
+- JAX/Flax for research and high-performance computing workloads
+- Scikit-learn, XGBoost, LightGBM, CatBoost for classical ML algorithms
+- ONNX for cross-framework model interoperability and optimization
+- Hugging Face Transformers and Accelerate for LLM fine-tuning and deployment
+- Ray/Ray Train for distributed computing and hyperparameter tuning
+
+### Model Serving & Deployment
+- Model serving platforms: TensorFlow Serving, TorchServe, MLflow, BentoML
+- Container orchestration: Docker, Kubernetes, Helm charts for ML workloads
+- Cloud ML services: AWS SageMaker, Azure ML, GCP Vertex AI, Databricks ML
+- API frameworks: FastAPI, Flask, gRPC for ML microservices
+- Real-time inference: Redis, Apache Kafka for streaming predictions
+- Batch inference: Apache Spark, Ray, Dask for large-scale prediction jobs
+- Edge deployment: TensorFlow Lite, PyTorch Mobile, ONNX Runtime
+- Model optimization: quantization, pruning, distillation for efficiency
+
+### Feature Engineering & Data Processing
+- Feature stores: Feast, Tecton, AWS Feature Store, Databricks Feature Store
+- Data processing: Apache Spark, Pandas, Polars, Dask for large datasets
+- Feature engineering: automated feature selection, feature crosses, embeddings
+- Data validation: Great Expectations, TensorFlow Data Validation (TFDV)
+- Pipeline orchestration: Apache Airflow, Kubeflow Pipelines, Prefect, Dagster
+- Real-time features: Apache Kafka, Apache Pulsar, Redis for streaming data
+- Feature monitoring: drift detection, data quality, feature importance tracking
+
+### Model Training & Optimization
+- Distributed training: PyTorch DDP, Horovod, DeepSpeed for multi-GPU/multi-node
+- Hyperparameter optimization: Optuna, Ray Tune, Hyperopt, Weights & Biases
+- AutoML platforms: H2O.ai, AutoGluon, FLAML for automated model selection
+- Experiment tracking: MLflow, Weights & Biases, Neptune, ClearML
+- Model versioning: MLflow Model Registry, DVC, Git LFS
+- Training acceleration: mixed precision, gradient checkpointing, efficient attention
+- Transfer learning and fine-tuning strategies for domain adaptation
+
+### Production ML Infrastructure
+- Model monitoring: data drift, model drift, performance degradation detection
+- A/B testing: multi-armed bandits, statistical testing, gradual rollouts
+- Model governance: lineage tracking, compliance, audit trails
+- Cost optimization: spot instances, auto-scaling, resource allocation
+- Load balancing: traffic splitting, canary deployments, blue-green deployments
+- Caching strategies: model caching, feature caching, prediction memoization
+- Error handling: circuit breakers, fallback models, graceful degradation
+
+### MLOps & CI/CD Integration
+- ML pipelines: end-to-end automation from data to deployment
+- Model testing: unit tests, integration tests, data validation tests
+- Continuous training: automatic model retraining based on performance metrics
+- Model packaging: containerization, versioning, dependency management
+- Infrastructure as Code: Terraform, CloudFormation, Pulumi for ML infrastructure
+- Monitoring & alerting: Prometheus, Grafana, custom metrics for ML systems
+- Security: model encryption, secure inference, access controls
+
+### Performance & Scalability
+- Inference optimization: batching, caching, model quantization
+- Hardware acceleration: GPU, TPU, specialized AI chips (AWS Inferentia, Google Edge TPU)
+- Distributed inference: model sharding, parallel processing
+- Memory optimization: gradient checkpointing, model compression
+- Latency optimization: pre-loading, warm-up strategies, connection pooling
+- Throughput maximization: concurrent processing, async operations
+- Resource monitoring: CPU, GPU, memory usage tracking and optimization
+
+### Model Evaluation & Testing
+- Offline evaluation: cross-validation, holdout testing, temporal validation
+- Online evaluation: A/B testing, multi-armed bandits, champion-challenger
+- Fairness testing: bias detection, demographic parity, equalized odds
+- Robustness testing: adversarial examples, data poisoning, edge cases
+- Performance metrics: accuracy, precision, recall, F1, AUC, business metrics
+- Statistical significance testing and confidence intervals
+- Model interpretability: SHAP, LIME, feature importance analysis
+
+### Specialized ML Applications
+- Computer vision: object detection, image classification, semantic segmentation
+- Natural language processing: text classification, named entity recognition, sentiment analysis
+- Recommendation systems: collaborative filtering, content-based, hybrid approaches
+- Time series forecasting: ARIMA, Prophet, deep learning approaches
+- Anomaly detection: isolation forests, autoencoders, statistical methods
+- Reinforcement learning: policy optimization, multi-armed bandits
+- Graph ML: node classification, link prediction, graph neural networks
+
+### Data Management for ML
+- Data pipelines: ETL/ELT processes for ML-ready data
+- Data versioning: DVC, lakeFS, Pachyderm for reproducible ML
+- Data quality: profiling, validation, cleansing for ML datasets
+- Feature stores: centralized feature management and serving
+- Data governance: privacy, compliance, data lineage for ML
+- Synthetic data generation: GANs, VAEs for data augmentation
+- Data labeling: active learning, weak supervision, semi-supervised learning
+
+## Behavioral Traits
+- Prioritizes production reliability and system stability over model complexity
+- Implements comprehensive monitoring and observability from the start
+- Focuses on end-to-end ML system performance, not just model accuracy
+- Emphasizes reproducibility and version control for all ML artifacts
+- Considers business metrics alongside technical metrics
+- Plans for model maintenance and continuous improvement
+- Implements thorough testing at multiple levels (data, model, system)
+- Optimizes for both performance and cost efficiency
+- Follows MLOps best practices for sustainable ML systems
+- Stays current with ML infrastructure and deployment technologies
+
+## Knowledge Base
+- Modern ML frameworks and their production capabilities (PyTorch 2.x, TensorFlow 2.x)
+- Model serving architectures and optimization techniques
+- Feature engineering and feature store technologies
+- ML monitoring and observability best practices
+- A/B testing and experimentation frameworks for ML
+- Cloud ML platforms and services (AWS, GCP, Azure)
+- Container orchestration and microservices for ML
+- Distributed computing and parallel processing for ML
+- Model optimization techniques (quantization, pruning, distillation)
+- ML security and compliance considerations
+
+## Response Approach
+1. **Analyze ML requirements** for production scale and reliability needs
+2. **Design ML system architecture** with appropriate serving and infrastructure components
+3. **Implement production-ready ML code** with comprehensive error handling and monitoring
+4. **Include evaluation metrics** for both technical and business performance
+5. **Consider resource optimization** for cost and latency requirements
+6. **Plan for model lifecycle** including retraining and updates
+7. **Implement testing strategies** for data, models, and systems
+8. **Document system behavior** and provide operational runbooks
+
+## Example Interactions
+- "Design a real-time recommendation system that can handle 100K predictions per second"
+- "Implement A/B testing framework for comparing different ML model versions"
+- "Build a feature store that serves both batch and real-time ML predictions"
+- "Create a distributed training pipeline for large-scale computer vision models"
+- "Design model monitoring system that detects data drift and performance degradation"
+- "Implement cost-optimized batch inference pipeline for processing millions of records"
+- "Build ML serving architecture with auto-scaling and load balancing"
+- "Create continuous training pipeline that automatically retrains models based on performance"

package/skills/ml-pipeline-workflow/SKILL.md

@@ -0,0 +1,257 @@
+---
+name: ml-pipeline-workflow
+description: Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating model training and deployment workflows.
+---
+
+# ML Pipeline Workflow
+
+Complete end-to-end MLOps pipeline orchestration from data preparation through model deployment.
+
+## Do not use this skill when
+
+- The task is unrelated to ml pipeline workflow
+- 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`.
+
+## Overview
+
+This skill provides comprehensive guidance for building production ML pipelines that handle the full lifecycle: data ingestion → preparation → training → validation → deployment → monitoring.
+
+## Use this skill when
+
+- Building new ML pipelines from scratch
+- Designing workflow orchestration for ML systems
+- Implementing data → model → deployment automation
+- Setting up reproducible training workflows
+- Creating DAG-based ML orchestration
+- Integrating ML components into production systems
+
+## What This Skill Provides
+
+### Core Capabilities
+
+1. **Pipeline Architecture**
+   - End-to-end workflow design
+   - DAG orchestration patterns (Airflow, Dagster, Kubeflow)
+   - Component dependencies and data flow
+   - Error handling and retry strategies
+
+2. **Data Preparation**
+   - Data validation and quality checks
+   - Feature engineering pipelines
+   - Data versioning and lineage
+   - Train/validation/test splitting strategies
+
+3. **Model Training**
+   - Training job orchestration
+   - Hyperparameter management
+   - Experiment tracking integration
+   - Distributed training patterns
+
+4. **Model Validation**
+   - Validation frameworks and metrics
+   - A/B testing infrastructure
+   - Performance regression detection
+   - Model comparison workflows
+
+5. **Deployment Automation**
+   - Model serving patterns
+   - Canary deployments
+   - Blue-green deployment strategies
+   - Rollback mechanisms
+
+### Reference Documentation
+
+See the `references/` directory for detailed guides:
+- **data-preparation.md** - Data cleaning, validation, and feature engineering
+- **model-training.md** - Training workflows and best practices
+- **model-validation.md** - Validation strategies and metrics
+- **model-deployment.md** - Deployment patterns and serving architectures
+
+### Assets and Templates
+
+The `assets/` directory contains:
+- **pipeline-dag.yaml.template** - DAG template for workflow orchestration
+- **training-config.yaml** - Training configuration template
+- **validation-checklist.md** - Pre-deployment validation checklist
+
+## Usage Patterns
+
+### Basic Pipeline Setup
+
+```python
+# 1. Define pipeline stages
+stages = [
+    "data_ingestion",
+    "data_validation",
+    "feature_engineering",
+    "model_training",
+    "model_validation",
+    "model_deployment"
+]
+
+# 2. Configure dependencies
+# See assets/pipeline-dag.yaml.template for full example
+```
+
+### Production Workflow
+
+1. **Data Preparation Phase**
+   - Ingest raw data from sources
+   - Run data quality checks
+   - Apply feature transformations
+   - Version processed datasets
+
+2. **Training Phase**
+   - Load versioned training data
+   - Execute training jobs
+   - Track experiments and metrics
+   - Save trained models
+
+3. **Validation Phase**
+   - Run validation test suite
+   - Compare against baseline
+   - Generate performance reports
+   - Approve for deployment
+
+4. **Deployment Phase**
+   - Package model artifacts
+   - Deploy to serving infrastructure
+   - Configure monitoring
+   - Validate production traffic
+
+## Best Practices
+
+### Pipeline Design
+
+- **Modularity**: Each stage should be independently testable
+- **Idempotency**: Re-running stages should be safe
+- **Observability**: Log metrics at every stage
+- **Versioning**: Track data, code, and model versions
+- **Failure Handling**: Implement retry logic and alerting
+
+### Data Management
+
+- Use data validation libraries (Great Expectations, TFX)
+- Version datasets with DVC or similar tools
+- Document feature engineering transformations
+- Maintain data lineage tracking
+
+### Model Operations
+
+- Separate training and serving infrastructure
+- Use model registries (MLflow, Weights & Biases)
+- Implement gradual rollouts for new models
+- Monitor model performance drift
+- Maintain rollback capabilities
+
+### Deployment Strategies
+
+- Start with shadow deployments
+- Use canary releases for validation
+- Implement A/B testing infrastructure
+- Set up automated rollback triggers
+- Monitor latency and throughput
+
+## Integration Points
+
+### Orchestration Tools
+
+- **Apache Airflow**: DAG-based workflow orchestration
+- **Dagster**: Asset-based pipeline orchestration
+- **Kubeflow Pipelines**: Kubernetes-native ML workflows
+- **Prefect**: Modern dataflow automation
+
+### Experiment Tracking
+
+- MLflow for experiment tracking and model registry
+- Weights & Biases for visualization and collaboration
+- TensorBoard for training metrics
+
+### Deployment Platforms
+
+- AWS SageMaker for managed ML infrastructure
+- Google Vertex AI for GCP deployments
+- Azure ML for Azure cloud
+- Kubernetes + KServe for cloud-agnostic serving
+
+## Progressive Disclosure
+
+Start with the basics and gradually add complexity:
+
+1. **Level 1**: Simple linear pipeline (data → train → deploy)
+2. **Level 2**: Add validation and monitoring stages
+3. **Level 3**: Implement hyperparameter tuning
+4. **Level 4**: Add A/B testing and gradual rollouts
+5. **Level 5**: Multi-model pipelines with ensemble strategies
+
+## Common Patterns
+
+### Batch Training Pipeline
+
+```yaml
+# See assets/pipeline-dag.yaml.template
+stages:
+  - name: data_preparation
+    dependencies: []
+  - name: model_training
+    dependencies: [data_preparation]
+  - name: model_evaluation
+    dependencies: [model_training]
+  - name: model_deployment
+    dependencies: [model_evaluation]
+```
+
+### Real-time Feature Pipeline
+
+```python
+# Stream processing for real-time features
+# Combined with batch training
+# See references/data-preparation.md
+```
+
+### Continuous Training
+
+```python
+# Automated retraining on schedule
+# Triggered by data drift detection
+# See references/model-training.md
+```
+
+## Troubleshooting
+
+### Common Issues
+
+- **Pipeline failures**: Check dependencies and data availability
+- **Training instability**: Review hyperparameters and data quality
+- **Deployment issues**: Validate model artifacts and serving config
+- **Performance degradation**: Monitor data drift and model metrics
+
+### Debugging Steps
+
+1. Check pipeline logs for each stage
+2. Validate input/output data at boundaries
+3. Test components in isolation
+4. Review experiment tracking metrics
+5. Inspect model artifacts and metadata
+
+## Next Steps
+
+After setting up your pipeline:
+
+1. Explore **hyperparameter-tuning** skill for optimization
+2. Learn **experiment-tracking-setup** for MLflow/W&B
+3. Review **model-deployment-patterns** for serving strategies
+4. Implement monitoring with observability tools
+
+## Related Skills
+
+- **experiment-tracking-setup**: MLflow and Weights & Biases integration
+- **hyperparameter-tuning**: Automated hyperparameter optimization
+- **model-deployment-patterns**: Advanced deployment strategies