setup-secrets

Manage credentials as runtime environment variables via Tower MCP.

19|Updated Apr 1, 2026

Search Tags:#automation #security #config #secrets #credentials #environment-variables #tower-mcp

Ready to run

npx skills add https://github.com/tower/agentic-data-engineering --skill setup-secrets-tower

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-secrets
Source: https://github.com/tower/agentic-data-engineering/tree/main/.claude/skills/setup-secrets
Command: npx skills add https://github.com/tower/agentic-data-engineering --skill setup-secrets-tower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely manage credentials and secrets as environment variables during runtime, ensuring secure handling when users ask to set up, configure, or inspect credentials.

Core Features & Use Cases

Centralized secret governance via Tower MCP, enabling creation, updates, and secure injection of credentials without exposing values.
Safe workflow for using credentials in data pipelines and deployments, with clear guidance and placeholder mechanics.
Use Case: When a user needs to configure API keys or database credentials for a new pipeline, this skill guides the secure setup.

Quick Start

Create placeholder secrets for the required sources and destinations and guide the user to fill in real values in the Tower UI.

Frequently Asked Questions about setup-secrets

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

FAQPage Schema

How do I securely manage secrets and environment variables for a data pipeline?▼

You can configure API keys and database credentials by generating placeholder secrets for sources and destinations, then filling in the real values securely through the Tower UI.

How do I configure credentials for data pipelines without exposing sensitive values?▼

Configure credentials by generating placeholder secrets for required sources and destinations, then injecting the real values securely via the Tower UI to prevent exposure during pipeline execution.

What environment variable naming conventions are required for managing runtime credentials?▼

Managing runtime credentials requires standard env var naming conventions, specifically SOURCES__<SOURCE>__<FIELD> and DESTINATION__<DESTINATION>__CREDENTIALS, to ensure secure and correct secret injection.

Do I need Tower MCP integration to set up and inspect credentials for deployments?▼

Yes, Tower MCP integration is required to set up and inspect credentials for deployments, as it provides the centralized governance and secure injection mechanics for runtime environment variables.

Can I update existing API keys and database credentials without exposing the current secret values?▼

Yes, using Tower MCP centralized secret governance, you can create and update credentials through placeholder mechanics and secure injection workflows without directly exposing the underlying secret values.