loa-credentials

Managing API keys across environment variables and dotenv files involves coordinating status, set, and test workflows. This skill enforces environment priority (env > encrypted store > .env.local) to configure and audit provider keys securely.

The correct priority order for resolving environment credentials is environment variables first, then the encrypted store, and finally the .env.local file. This multi-storage policy determines which active credentials are used.

You can audit API credentials by running a centralized health check across environment variables, encrypted stores, and local dotenv files. This process ensures secure storage, traceability, and compliant usage of your provider keys.

To securely set API secrets without leaking sensitive values, the system prompts you to enter sensitive values directly during the set workflow. This prevents leakage and ensures secure configuration across your storage options.

Yes, you can delete provider keys from encrypted stores and environment variables using the delete workflow. This allows you to clean credentials and maintain compliant usage across your active configuration.