init-dlthub-workspace

Initializes and verifies dltHub workspaces with uv environment setup and toolkit routing.

1|Updated May 13, 2026
One-click install
npx skills add https://github.com/dlt-hub/dlthub-start --skill init-dlthub-workspace-dlt-hub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init-dlthub-workspace
Source: https://github.com/dlt-hub/dlthub-start/tree/main/src/create_dlthub_workspace/scaffolds/minimal_workspace/_agents/codex/.agents/skills/init-dlthub-workspace
Command: npx skills add https://github.com/dlt-hub/dlthub-start --skill init-dlthub-workspace-dlt-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Data engineering agents often start sessions in environments where uv, Python virtual environments, or dltHub are missing or misconfigured, causing failed commands and blocked pipelines. This Skill verifies the workspace state at session start and sets up a working dltHub environment in place, then routes user intent to the correct data engineering toolkit. ## Core Features & Use Cases - Environment verification and setup: Checks uv availability and runs uvx dlthub-init@latest (or the dlt[hub] fallback) to scaffold a workspace in place, then confirms with dlthub ai status. - Intent-to-toolkit routing: Maps user goals (REST API ingestion, SQL databases, files, transformations, data quality, deployment) to the correct toolkit install command and entry skill. - Safe secrets handling: Enforces rules that prevent reading secrets.toml files or printing credentials, directing all secret operations through the dlt-workspace-mcp server. - Use Case: A user asks an agent to build a pipeline from the Stripe API. The agent verifies the workspace, installs the rest-api-pipeline toolkit, and hands off to the find-source entry skill without manual setup. ## Quick Start Ask the agent to set up a dltHub workspace in this project and start building a pipeline from a REST API source.

Frequently Asked Questions about init-dlthub-workspace

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

FAQPage Schema
How do I set up a dltHub workspace in an existing project?▼

Run `uvx dlthub-init@latest` in the project directory to scaffold a dltHub workspace in place with AI support. If that fails, fall back to `uvx --from "dlt[hub]" dlthub init` followed by `uv run dlthub ai init`, then verify with `uv run dlthub ai status`.

How do I build a REST API pipeline with dltHub?▼

Install the rest-api-pipeline toolkit with `dlthub --non-interactive ai toolkit install rest-api-pipeline`, then open its find-source entry skill. For quick demos rather than production pipelines, use the one-shot toolkit instead.

What is the difference between dlthub-init and dlthub-start?▼

dlthub-init is non-interactive and agent-friendly, scaffolding a workspace in place for real projects. dlthub-start is an interactive onboarding playground that requires a human terminal for authentication and is not meant for production workflows.

Can the agent read my dlt secrets.toml file?▼

No. The skill forbids reading any secrets.toml file or printing secret values to the conversation. Credentials are managed through the dlt-workspace-mcp secrets tools or the `dlthub ai secrets` CLI, and Python code accesses values via `dlt.secrets["key"]`.

Why should dlthub commands run with --non-interactive?▼

The --non-interactive flag prevents prompts that would block automated agent execution. All dlthub commands should also run from the project root with `uv run` so the CLI locates the .dlt configuration directory correctly.