setup-secrets

Manage dlt secrets in *.secrets.toml files for API keys, passwords, and tokens.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a secure and structured way to manage sensitive credentials (API keys, passwords, tokens) required for data pipelines, preventing them from being exposed in code or logs.

Core Features & Use Cases

  • Credential Management: Safely store and retrieve secrets using TOML files.
  • Secure Access: Integrates with dlt-workspace-mcp for secure secret handling or falls back to CLI commands.
  • Use Case: When setting up a new data source that requires an API key, this skill guides you through storing the key securely in .dlt/secrets.toml and shows how to access it in your Python code without exposing the value.

Quick Start

Use the setup-secrets skill to configure credentials for the stripe API.

Frequently Asked Questions about setup-secrets

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

FAQPage Schema
How do I securely store API keys and passwords for dlt pipelines?

You can securely store API keys and passwords for dlt pipelines by configuring them in `.secrets.toml` files, which keeps sensitive credentials out of your source code and execution logs.

How do I read secrets in Python using dlt without exposing the actual values?

You can read secrets in Python using dlt by leveraging `dlt.secrets` for credential resolution, which retrieves the required values from your TOML configuration without exposing the actual values in the code.

What is the best way to configure credentials for a new dlt data source?

The best way to configure credentials for a new dlt data source is to define the API keys, database passwords, or tokens in a structured `.secrets.toml` file, which dlt then automatically reads and resolves.

Do I need to understand TOML structure to manage dlt credentials?

Yes, you need to understand TOML structure to manage dlt credentials, because this Skill requires correctly formatting the `.secrets.toml` files to ensure dlt can properly resolve and access your secrets.

Can I inspect or update existing dlt secrets without exposing them in the terminal?

Yes, you can inspect or update existing dlt secrets securely by requesting a configuration check for your credentials, which validates the setup in your `.secrets.toml` file without printing the sensitive values.