datarobot-oss/datarobot-agent-skills / skills/datarobot-model-deployment
datarobot-model-deployment
VerifiedTools and guidance for deploying DataRobot models, managing deployments, configuring prediction environments, and deployment operations. Use when deploying models, creating or updating deployments, or configuring prediction environments.
DataRobot Model Deployment Skill
This skill provides comprehensive guidance for deploying models, managing deployment configurations, and operating production deployments.
Quick Start
Most common use case: Deploy a trained model to production
- Get best model: Find the best model from a project (highest metric score)
- Create deployment:
create_deployment(model_id, deployment_name)to deploy model - Get endpoint:
get_deployment_endpoint(deployment_id)to retrieve prediction URL
Example: "Deploy the best model from project abc123 as 'Sales Prediction v1'"
When to use this skill
Use this skill when you need to:
- Deploy trained models to production
- Configure deployment settings and environments
- Manage multiple deployments
- Replace a deployment’s champion model with a new model version
- Configure prediction servers and environments
- Monitor deployment health and status
- Manage deployment access and permissions
Key capabilities
1. Deployment Creation
- Deploy models from projects or registered models
- Choose prediction environment (DataRobot Serverless, external)
- Configure deployment settings (challenger models, A/B testing)
- Set up deployment metadata and descriptions
2. Deployment Configuration
- Configure prediction servers and environments
- Set up batch prediction settings
- Configure real-time prediction endpoints
- Manage deployment credentials and access
3. Deployment Management
- Replace deployment champion model (model swap)
- Enable/disable deployments
- Manage challenger models for A/B testing
- Configure replacement policies
4. Deployment Operations
- Get deployment information and status
- Retrieve deployment endpoints
- Manage deployment settings
- Handle deployment errors and issues
Workflow examples
Example 1: Deploy a model to production
User request: "Deploy the best model from project abc123 to production with the name 'Sales Prediction v1'."
Agent workflow:
- Get the best model from the project (highest metric score)
- Create a new deployment with the model
- Configure deployment settings (name, description, environment)
- Set up prediction environment (DataRobot Serverless recommended)
- Retrieve deployment endpoint and credentials
- Verify deployment is active and ready for predictions
Example 2: Update deployment with new model
User request: "Replace the model in deployment xyz789 with the latest model from project abc123."
Agent workflow:
- Get the latest model from the project
- Retrieve current deployment information
- Validate the replacement model is eligible (
deployment.validate_replacement_model(...)) - Perform model replacement (
deployment.perform_model_replace(...)) - Verify replacement completed successfully
- Report deployment update status
Using DataRobot SDK
This skill guides you to use the DataRobot Python SDK directly. Install the SDK if needed:
pip install datarobot
Key SDK Operations
Use these DataRobot SDK methods for deployment management:
Deployments:
dr.Deployment.create_from_learning_model(model_id, label)- Create deploymentdr.Deployment.get(deployment_id)- Get deployment detailsdr.Deployment.list(project_id)- List deploymentsdeployment.delete()- Delete deployment
Model Replacement (champion swap):
deployment.validate_replacement_model(new_model_id=...)- Validate replacement eligibilitydeployment.perform_model_replace(new_model_id=..., reason=...)- Replace champion model (async)
Challenger Models (limited via SDK):
deployment.list_challengers()- List challenger models (if enabled/configured)deployment.get_challenger_models_settings()/deployment.update_challenger_models_settings(...)- Configure challenger models settings
Deployment Info:
deployment.get_features()- Get required features
See the Common Patterns section below for complete examples.
Best practices
- Naming conventions: Use clear, versioned names for deployments
- Environment selection: Choose appropriate prediction environment for your use case
- Challenger models: Use challenger models to test new models before full replacement
- Monitoring: Set up monitoring and alerts for production deployments
- Documentation: Document deployment purpose, model version, and configuration
- Access control: Configure appropriate access permissions for deployments
Common patterns
Pattern 1: Standard deployment
import datarobot as dr
# Initialize client
dr.Client()
# Get best model from project
models = dr.Model.list("abc123")
best_model = max(models, key=lambda m: m.metrics.get("AUC", 0))
# Create deployment
deployment = dr.Deployment.create_from_learning_model(
model_id=best_model.id,
label="Sales Prediction v1",
description="Production deployment for sales forecasting",
)
print(f"Deployment created: {deployment.id}")
Pattern 2: Deployment with challenger
import datarobot as dr
# Create deployment with primary model
deployment = dr.Deployment.create_from_learning_model(
model_id=primary_model.id, label="Sales Prediction v2"
)
# List challengers (if challenger models are configured/enabled)
challengers = deployment.list_challengers()
print(f"Challengers: {len(challengers)}")
Deployment environments
DataRobot Serverless
- Fully managed prediction environment
- Automatic scaling
- No infrastructure management
- Recommended for most use cases
External deployment
- Deploy to your own infrastructure
- More control over resources
- Requires infrastructure management
- Use for specific compliance or performance requirements
Deployment lifecycle
- Create: Deploy model to production environment
- Monitor: Track predictions, performance, and health
- Update: Replace with new model versions as needed
- Retire: Disable or archive old deployments
Error handling
Common errors and solutions:
- Model not found: Verify model ID and project access
- Deployment creation failures: Check prediction environment availability
- Endpoint access issues: Verify credentials and permissions
- Update failures: Ensure new model is compatible with deployment settings
SDK Setup
Install DataRobot SDK
pip install datarobot
Initialize Client
import datarobot as dr
dr.Client()
Resources
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |