environment-secrets

You can securely request secrets from users by using a guided workflow that gathers API keys, tokens, and credentials without exposing them in your code. This ensures sensitive data remains out of source control during new service integrations.

The best way to view and delete environment variables in a shared environment is using a tool with environment scoping and predictable return formats. This ensures safe configuration changes across shared, development, and production contexts.

Yes, you can set environment variables for specific scopes like development or production. The skill applies environment scoping to its view, set, and delete operations, ensuring variables are only affected within their intended environment context.

You securely configure API keys and tokens by using a request workflow that gathers credentials directly from users. This approach keeps sensitive data out of your source code while enabling safe configuration across development and production environments.

No, this environment secrets skill does not require any external dependencies or components to function. It independently handles the viewing, setting, deleting, and requesting of environment variables and secrets across your configured environments.