How do I install the Setup Runtime skill?

Run npx skillmds@latest add dlt-hub/setup-runtime in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Setup Runtime safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Setup Runtime?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Setup Runtime free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Setup Runtime?

dlt-hub (@dlt-hub) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Setup Runtime by dlt-hub — Agent Skill

Name: Setup Runtime
Author: dlt-hub

File contents

Verify workspace for dltHub Platform

Lightweight check that the workspace is ready for runtime work. Run through each check and fix issues as found.

Reference:

Workspace intro (install dlt[hub], create a workspace): https://dlthub.com/docs/hub/getting-started/installation.md
Workspace setup (convert a Python project, credentials per profile): https://dlthub.com/docs/hub/pipeline-operations/workspace-setup.md

1. Verify Python project

Check pyproject.toml exists in the project root. If not:

uv init

dltHub Platform uses pyproject.toml to install dependencies remotely.

2. Check `.dlt/.workspace` file

ls .dlt/.workspace

This file enables profiles and the runtime CLI. If missing, use dlthub init (preferred):

dlthub init                    # creates .dlt/.workspace, prompts for workspace name
dlthub init --name <workspace> # skip prompt
dlthub init --dry-run          # preview only

Or manually as fallback: touch .dlt/.workspace

Heads up: the workspace description shown in the dltHub Platform UI comes from the first line of the docstring in __deployment__.py. You can set it now or later when creating the manifest in (prepare-deployment).

3. Check `dlt[hub]` dependency

Verify dlt with the hub extra is installed:

uv pip show dlt

If not installed or missing the hub extra:

uv add "dlt[hub]"

If adding dlt to pyproject.toml, pin the exact installed version (==) — uv add may downgrade pre-release versions.

4. Login to dltHub Platform

dlthub login

Opens a device-code OAuth flow (user visits URL + enters code in browser)
After login, connect to a workspace:

dlthub workspace connect                          # interactive prompt to select or create
dlthub workspace connect <name_or_id>             # skip prompt
dlthub workspace connect <name_or_id> --org-id <id>  # specify org

The selected workspace ID is stored in config.toml under [runtime] workspace_id
To switch workspaces (no re-login needed): dlthub workspace connect <name_or_id>
To log out: dlthub logout

5. Verify profile files exist

ls .dlt/*.toml

List existing config and secrets files. At minimum these should exist:

.dlt/config.toml
.dlt/secrets.toml
.dlt/.workspace

Profile-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.

---name: setup-runtimedescription: Verify dlthub workspace is ready for dltHub Platform. Use when user wants to deploy for the first time, or when another skill reports missing prerequisites like .workspace file or dlt[hub] dependency.---# Verify workspace for dltHub PlatformLightweight check that the workspace is ready for runtime work. Run through each check and fix issues as found.**Reference**:- Workspace intro (install `dlt[hub]`, create a workspace): https://dlthub.com/docs/hub/getting-started/installation.md- Workspace setup (convert a Python project, credentials per profile): https://dlthub.com/docs/hub/pipeline-operations/workspace-setup.md## 1. Verify Python projectCheck `pyproject.toml` exists in the project root. If not:```bashuv init```dltHub Platform uses `pyproject.toml` to install dependencies remotely.## 2. Check `.dlt/.workspace` file```bashls .dlt/.workspace```This file enables profiles and the runtime CLI. If missing, use `dlthub init` (preferred):```bashdlthub init # creates .dlt/.workspace, prompts for workspace namedlthub init --name <workspace> # skip promptdlthub init --dry-run # preview only```Or manually as fallback: `touch .dlt/.workspace`> **Heads up:** the workspace description shown in the dltHub Platform UI comes from the first line of the docstring in `__deployment__.py`. You can set it now or later when creating the manifest in (`prepare-deployment`).## 3. Check `dlt[hub]` dependencyVerify `dlt` with the `hub` extra is installed:```bashuv pip show dlt```If not installed or missing the `hub` extra:```bashuv add "dlt[hub]"```If adding `dlt` to `pyproject.toml`, pin the exact installed version (`==`) — `uv add` may downgrade pre-release versions.## 4. Login to dltHub Platform```bashdlthub login```- Opens a device-code OAuth flow (user visits URL + enters code in browser)- After login, connect to a workspace:```bashdlthub workspace connect # interactive prompt to select or createdlthub workspace connect <name_or_id> # skip promptdlthub workspace connect <name_or_id> --org-id <id> # specify org```- The selected workspace ID is stored in `config.toml` under `[runtime] workspace_id`- To **switch workspaces** (no re-login needed): `dlthub workspace connect <name_or_id>`- To **log out**: `dlthub logout`## 5. Verify profile files exist```bashls .dlt/*.toml```List existing config and secrets files. At minimum these should exist:- `.dlt/config.toml`- `.dlt/secrets.toml`- `.dlt/.workspace`Profile-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.

Frequently asked questions

Setup Runtime