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.