setup-secrets

Configure dlthub credentials in .dlt/secrets.toml files using MCP tools or CLI commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up dlt pipeline credentials requires knowing the correct TOML layout, scoping rules, and file locations, and mishandling secrets risks exposing API keys and passwords in logs or code. ## Core Features & Use Cases - Secrets File Management: List, inspect redacted views, and merge TOML fragments into .dlt/secrets.toml or profile-scoped files via dlt-workspace-mcp tools or dlthub ai secrets CLI commands. - Safe Placeholder Workflow: Writes only meaningful placeholders (never real secret values) scoped under [sources.<name>] or [destination.<name>.credentials], so users fill in actual values by editing files directly. - Credential Research Guidance: Identifies required fields from ConfigFieldMissingException messages or dlt.secrets.value parameters and points users to where each credential is obtained. - Use Case: After hitting a ConfigFieldMissingException for a Stripe pipeline, use this Skill to create [sources.stripe] with an api_key placeholder in .dlt/secrets.toml, then verify the redacted merged view. ## Quick Start Set up the secrets for my Stripe dlt source by creating the proper entries in .dlt/secrets.toml with placeholders I can fill in.

Frequently Asked Questions about setup-secrets

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

FAQPage Schema
How do I set up dlt secrets in secrets.toml?▼

Use the secrets_update_fragment MCP tool or dlthub ai secrets update-fragment CLI command to merge a TOML fragment into .dlt/secrets.toml. Scope entries under [sources.<name>] or [destination.<name>.credentials] and write only placeholders, then edit the file directly to add real values.

How do I read dlt secrets in Python code?▼

Access secrets with dlt.secrets using the same TOML path, for example dlt.secrets["sources.github.api_key"]. You can also retrieve typed credentials like GcpServiceAccountCredentials via dlt.secrets.get with a default class.

What is the difference between profile-scoped and default secrets.toml files?▼

Profile-scoped files like .dlt/dev.secrets.toml take precedence and appear first in secrets_list output. Use them when present and fall back to .dlt/secrets.toml otherwise; the redacted view merges all workspace files.

Can I pass real API keys through the secrets update tool?▼

No. The workflow only writes placeholders such as "sk-*****-your-key" through secrets_update_fragment. Real values must be added by editing the secrets file directly so they never pass through tools or logs.

Why does my dlt pipeline raise ConfigFieldMissingException?▼

The exception means a required credential field is missing from your secrets configuration. Read the exception message for the exact field name and TOML path, then add that field under the correct [sources.<name>] or [destination.<name>.credentials] section.