prepare-deployment

Configure production credentials and Motherduck destinations in a dltHub workspace.

53|5|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/dlt-hub/dlthub-ai-workbench --skill prepare-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-deployment
Source: https://github.com/dlt-hub/dlthub-ai-workbench/tree/main/workbench/dlthub-runtime/skills/prepare-deployment
Command: npx skills add https://github.com/dlt-hub/dlthub-ai-workbench --skill prepare-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dlt, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of configuring your dltHub environment for production deployments by managing credentials and destination settings.

Core Features & Use Cases

  • Production Credential Setup: Safely split and manage development and production secrets.
  • Destination Configuration: Configure production-ready data destinations like Motherduck.
  • Use Case: Before deploying your data pipeline to dltHub Runtime, use this skill to ensure your production database credentials are correctly set up in a separate prod.secrets.toml file and that your pipeline points to the production destination.

Quick Start

Use the prepare-deployment skill to set up production secrets and configure the Motherduck destination.

Frequently Asked Questions about prepare-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split development and production secrets for dlt pipelines?

To configure a Motherduck destination for dlt production deployment, you use MCP tools to set up the cloud-based destination and ensure your pipeline points to it. This requires adherence to specific `.dlt/` directory structures for proper configuration.

What is the best way to manage credentials before deploying to dltHub Runtime?

To configure a Motherduck destination for dlt production deployment, you use MCP tools to set up the cloud-based destination and ensure your pipeline points to it. This requires adherence to specific `.dlt/` directory structures for proper configuration.

How do I configure a Motherduck destination for dlt production deployment?

To configure a Motherduck destination for dlt production deployment, you use MCP tools to set up the cloud-based destination and ensure your pipeline points to it. This requires adherence to specific `.dlt/` directory structures for proper configuration.

Do I need a specific directory structure to prepare a dltHub workspace for production?

To configure a Motherduck destination for dlt production deployment, you use MCP tools to set up the cloud-based destination and ensure your pipeline points to it. This requires adherence to specific `.dlt/` directory structures for proper configuration.

Can I use dlt to set up profile-scoped credentials for production environments?

To configure a Motherduck destination for dlt production deployment, you use MCP tools to set up the cloud-based destination and ensure your pipeline points to it. This requires adherence to specific `.dlt/` directory structures for proper configuration.

When should I separate development and production secrets in dlt?

To configure a Motherduck destination for dlt production deployment, you use MCP tools to set up the cloud-based destination and ensure your pipeline points to it. This requires adherence to specific `.dlt/` directory structures for proper configuration.