environment-secrets

To manage environment variables without hardcoding secrets, use a centralized skill to view, set non-sensitive values, and request sensitive data directly from users. This enforces safe usage by separating configuration from sensitive credentials across development and production.

The best way to securely collect secrets for production environments is to prompt users directly for sensitive values. This approach avoids hardcoding secrets and keeps them global while managing non-sensitive configuration scoped to development or production.

You cannot set sensitive environment variables directly. You must request secrets from users via a dedicated prompting mechanism. Non-sensitive values can be set directly, but the system safeguards against direct editing of runtime-managed variables to prevent accidental exposure.

You can view and delete environment variables across different environments using a centralized management interface. This approach supports scoping configurations to shared, development, or production environments while keeping secrets global.

You should avoid modifying runtime-managed environment variables to prevent system instability and security risks. The management skill enforces safeguards against direct editing of these runtime variables, ensuring sensitive data is only updated through secure prompting.

Environment secrets management works for both development and production scoping. It separates non-sensitive configuration by environment scope while keeping secrets global, ensuring consistent and safe usage across your entire deployment lifecycle.