environment-secrets

Securely manage environment variables and secrets by viewing, setting, and deleting values across scoped environments, while requesting sensitive credentials directly from users to avoid hardcoding. This workflow applies to shared, development, and production environments, with secrets kept global.

To avoid hardcoding API keys and tokens, use a secure workflow that requests secrets directly from users via a dedicated function. This ensures sensitive credentials are supplied at runtime rather than embedded in application configuration files.

Yes, you can scope environment variables separately for development and production environments. The Skill supports environment scoping across shared, development, and production tiers, while secrets are configured globally across all environments.

Delete unused environment variables using a dedicated function, and request missing secrets from users via a specific request function. This workflow returns a structured result, ensuring your application configuration remains clean and only holds necessary values.

No, managing environment secrets with this approach requires no external dependencies or configuration tools. The Skill operates independently, providing built-in functions to view, set, delete, and request environment variables without additional packages.

Secrets are handled globally to ensure sensitive credentials remain consistent and securely isolated from standard configuration values. Standard environment variables are scoped per environment—shared, development, or production—so non-sensitive settings can differ without affecting secret integrity.