deploy-workspace

Deploy and schedule dlt pipelines and notebooks on the dltHub Platform.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/aminojagh/LLMZC --skill deploy-workspace-aminojagh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-workspace
Source: https://github.com/aminojagh/LLMZC/tree/main/05_02_dlt_workshop/.claude/skills/deploy-workspace
Command: npx skills add https://github.com/aminojagh/LLMZC --skill deploy-workspace-aminojagh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving dlt pipelines from local development to a managed cloud runtime involves error-prone steps: removing dev-only settings, pinning dependencies, configuring triggers, and debugging remote failures. This Skill guides the full deployment workflow to dltHub Platform so pipelines and notebooks run reliably in production. ## Core Features & Use Cases - Production readiness checks: Removes dev_mode=True, externalizes dev limits, verifies write_disposition, and pins the dlt version in pyproject.toml before deployment. - Local simulation and cloud runs: Simulates jobs locally with dlthub local run (including --profile prod credential checks), then runs batch jobs with dlthub run and interactive jobs with dlthub serve. - Scheduling and triggers: Adds cron schedules, interval-based triggers, followup chains, freshness gates, and refresh cascades via the __deployment__.py manifest. - Use Case: You built a dlt pipeline locally against DuckDB and want it running daily on BigQuery in the cloud. The Skill walks you through production checks, a dry-run deploy, a local prod-profile simulation, cloud launch, log inspection, and cron scheduling. ## Quick Start Deploy my dlt pipeline to dltHub and schedule it to run daily at midnight.

Frequently Asked Questions about deploy-workspace

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

FAQPage Schema
How do I deploy a dlt pipeline to dltHub Platform?▼

Run dlthub deploy to sync your deployment manifest to the runtime, then dlthub run my_pipeline.py to execute it on the cloud. For first deployments, complete workspace setup and credential configuration first, and preview changes with dlthub deploy --dry-run.

How do I schedule a dlt pipeline with cron on dltHub?▼

Add a trigger to the @run.pipeline decorator, such as trigger=trigger.schedule("0 0 * * *") for daily midnight UTC runs, then run dlthub deploy. Triggers declared in code are the source of truth; there is no CLI command for adding schedules.

Can I test a dltHub job locally before deploying?▼

Yes, dlthub local run <job_name> resolves the job exactly like the runtime does but executes on your machine. Use --profile prod to catch missing production credentials or destination misconfiguration before anything reaches the platform.

Why does my dltHub remote job do nothing after deployment?▼

The deployed script is missing an if __name__ == "__main__": block, which the runtime requires to execute the job. Also verify the script does not rely on interactive or debug-only code inside that block.

What are the limitations of dltHub Platform jobs?▼

Jobs are killed after 120 minutes by default, though you can override this with execute={"timeout": "6h"} in the decorator. Notebooks must use dlt.attach() with explicit destination and dataset_name, and one workspace is allowed per GitHub account.