From dlthub-runtime
Verifies dlt workspace readiness for dltHub Runtime by checking pyproject.toml, .dlt/.workspace, dlt[hub] dependency with uv, runtime login, and profile files. Use before first deployment or on prereq errors.
npx claudepluginhub dlt-hub/dlthub-ai-workbench --plugin dlthub-runtimeThis skill uses the workspace's default tool permissions.
Lightweight check that the workspace is ready for runtime work. Run through each check and fix issues as found.
Deploys dlt pipelines to dltHub Runtime. Prepares Python scripts by removing dev_mode/limits, verifies dispositions, pins versions; runs dlt CLI deploy/launch/logs. For runtime deployment requests.
Validates dev environment by checking OS, runtime versions (Node, Python, Rust, Go, Ruby), installed tools, port availability, env vars, and disk space. Use for new projects, machine switches, or 'works on my machine' bugs.
Routes users to appropriate dlt toolkits and skills for data engineering by listing catalogs, matching intents via skill descriptions, guiding installs, and confirming MCP setup.
Share bugs, ideas, or general feedback.
Lightweight check that the workspace is ready for runtime work. Run through each check and fix issues as found.
Reference: https://dlthub.com/docs/hub/command-line-interface.md
Check pyproject.toml exists in the project root. If not:
uv init
Runtime uses pyproject.toml to install dependencies remotely.
.dlt/.workspace filels .dlt/.workspace
This file enables profiles and the runtime CLI. If missing:
touch .dlt/.workspace
dlt[hub] dependencyVerify dlt with the hub extra is installed:
uv pip show dlt
If not installed or missing the hub extra:
uv add "dlt[workspace,hub]"
If adding dlt to pyproject.toml, pin the exact installed version (==) — uv add may downgrade pre-release versions.
dlt runtime login
printf '1\n' | dlt runtime login)0), name, description (can be empty)config.toml under [runtime] workspace_iddlt runtime logout, remove workspace_id from config.toml, then dlt runtime login againls .dlt/*.toml
List existing config and secrets files. At minimum these should exist:
.dlt/config.toml.dlt/secrets.toml.dlt/.workspaceProfile-scoped files (dev.*, prod.*, access.*) may or may not exist yet — that's fine, (prepare-deployment) handles their creation.
Tell the user what's present and what the next step is: use (prepare-deployment) to set up production credentials and destinations.